Production (regression) Smoke Tests

[CADbryon]

Investigate and compare smoke testing tools for our web application, focusing on their integration capabilities with our CI/CD pipeline and keep the cost at zero. The goal is to identify the most suitable tool for our needs.

1. Research and create a list of five popular open-source smoke testing tools, including but not limited to:

• [ ] Selenium
• [ ] Cypress
• [ ] Puppeteer
• [ ] TestCafe
• [x] Playwright
• [ ] Feel free to edit this list as required.

1.1 Research the Tracker teams current end to end testing solution. Compare that research to the tools in step 1 and moving forward.

• [x] Jest

2. For each tool, investigate and document:

• Cost
• Core features and capabilities (assuming they are all the same)
• Ease of use and learning curve
• Language support (e.g., JavaScript, Python, other?)
• Integration with our CI/CD tools

3. Create a very simply comparison matrix of the tools based on the criteria above. Recommend two tools.

4. Test two tools (mentioned above) by writing a basic smoke test for our web application's login page.

5. Integrate one of the tools into our pipeline.

• Keep your work visible. Ask the team for help.

[h701h]

Can we have multiple targets? Options:

1. tracker.canada.ca (different logins, different orgs, )
2. local (code spaces) (garbage data)
3. alpha
4. ?