Introduce acceptance spec harness

[Systho]

I volunteer for introducing an acceptance spec "harness"

• a structured way of organizing spec/support in order to have specific subfolder for specific support stereotypes
• amending rails_helper in order to autoload some of the newly introduced helpers and configuration
• introduction of SitePrism : a small gem for cretaing page objects, making acceptance spec much more flexible and robust
• writing a first acceptance spec story in order to illustrate how to correctly write those in a narrative way, making those more time resistant by not relying on low level details.

If this makes sense to you, I can work on a PR but I will need a short story about an actual added value in the form of 5 to 20 steps, with only actions done described from the user perspective, the last step can be a verification step.

eg:

• I login as an admin
• I go to the admin panel
• I create a new rebel
• I edit the newly created rebel
• I update the newly created rebel
• I search the rebels according to the update
• The updated rebel is in the search results

[mhulet]

Hi @Systho, sorry for the radio silence these days, slow (and calm) start for the year. I'm now back to the Rebels Manager 🙌

So, this is super interesting. I have started the project without specs because I wanted us to go fast, but now we definitely need to increase the test coverage as much as working on new features.

I didn't want to dive into feature specs yet (if we are speaking about the same topic, to be honest I don't know -- my own experience with tests is yet limited), is this the same? But the scenario that you give as an example is absolutely relevant and can be a first one.

I would say:

• I login as a local coordinator (= a user linked to a local group)
• I create a new rebel
• I edit the newly created rebel (new name)
• I update the newly created rebel
• I search for the rebel name according to the update
• The updated rebel is in the search results

[Systho]

Yes I was speaking about feature spec, which are now renamed system spec since Rails acknowledged their existence :) Le jeu. 9 janv. 2020 à 12:42, Michael Hulet <notifications@github.com> a écrit :

…

Hi @Systho <https://github.com/Systho>, sorry for the radio silence these days, slow (and calm) start for the year. I'm now back to the Rebels Manager 🙌 So, this is super interesting. I have started the project without specs because I wanted us to go fast, but now we definitely need to increase the test coverage as much as working on new features. I didn't want to dive into feature specs yet (if we are speaking about the same topic, to be honest I don't know -- my own experience with tests is yet limited), is this the same? But the scenario that you give as an example is absolutely relevant and can be a first one. I would say: - I login as a local coordinator (= a user linked to a local group) - I create a new rebel - I edit the newly created rebel (new name) - I update the newly created rebel - I search for the rebel name according to the update - The updated rebel is in the search results — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#150?email_source=notifications&email_token=AAALSZTADFY56543OOP2EN3Q44ETTA5CNFSM4KCOQAMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIQAT3I#issuecomment-572525037>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAALSZQBR725UNGU6A5YBEDQ44ETTANCNFSM4KCOQAMA> .

-- Systho.

[mhulet]

Damn, there is always something new to learn. Could this computer world stop evolving someday, so that we can just sit down and relax? 😅