Droopler has a few known bugs and we want to catch them early. Automated tests can help us find these bugs faster and prevent new ones from appearing. However, we haven't decided which testing framework or approach to use yet (e.g., PHPUnit, Behat, Cypress, etc.). This issue aims to explore different options for automated testing in Droopler.
1. Research possible testing approaches and frameworks for Drupal-based distributions.
2. Decide on the most suitable automated testing approach (e.g., PHPUnit for backend testing, Behat or Cypress for functional/end-to-end tests).
3. Create a basic test suite for Droopler and run it against known bugs.
4. Gradually expand the test coverage to help reduce and prevent bugs.
1. Choose the testing framework (discussion and consensus).
2. Set up the testing environment and necessary configurations.
3. Write initial test scripts covering the most critical features.
4. Integrate tests into the existing CI/CD process (if available).
5. Document how to run and maintain these tests.
Active
5.0
Code
Automatically closed - issue fixed for 2 weeks with no activity.