Test coverage of website features

[ctmbl]

Tests could be separated in different categories:

• automatically/manually
• at each PR/release
• backend/frontend/both

So what features of the website should be tested:

Non-logged:

• read an article
• redirect to home page
• sign up
• impossibility of deleting/creating articles
• ...

Logged:

• log in
• read an article
• create an article
• impossibility of deleting others articles
• ...

@atxr you may propose other features to test
@amtoine you may give an opinion on how to address these tests, how solid should they be (because a common risk is to make tests so stronger that you can't change anything

[amtoine]

mm 🤔

tbh, i do not even have an idea how to implement such tests 😅

a question for now: what do you mean by "logged" and "non-logged"? 😕

[atxr]

I think it's tests as a logged user or not

[amtoine]

got it 👍
wanted to be sure 😋

[atxr]

These one looks very important indeed!
I would add also test that must fail, for example create an article/delete when not logged in

[ctmbl]

That's right!

[amtoine]

could you add that to the list above @ctmbl? 😋

[amtoine]

in the end, pretty much all the tests would be duplicated in "logged" and "non-logged" 👌