As the website keeps growing, new features are added and the code becomes more complex to manage, we could make use of e2e-testing (End-to-End testing) to make sure the application behaves the way that it should whenever a new feature/fix is merged.
What is the expected behavior?
This first issue should reflect a Proof of Concept/initial implementation of an e2e-testing library in the application. We (@jcooter @gvan12 and myself) consider that Cypress is the best alternative.
What is motivation or use case for adding/changing the behavior?
Ensure that the application behaves in the way we expect
Provide security to the dev team whenever merging new code
How should this be implemented in your opinion?
This first POC should include the basic setup of Cypress along with some basic test suites
Feature request
As the website keeps growing, new features are added and the code becomes more complex to manage, we could make use of e2e-testing (End-to-End testing) to make sure the application behaves the way that it should whenever a new feature/fix is merged.
What is the expected behavior?
This first issue should reflect a Proof of Concept/initial implementation of an e2e-testing library in the application. We (@jcooter @gvan12 and myself) consider that Cypress is the best alternative.
What is motivation or use case for adding/changing the behavior?
How should this be implemented in your opinion?
Are you willing to work on this yourself? yes