ci: add UI tests for improved release stability
New Pull Request Checklist
- [x] I am not disclosing a vulnerability.
- [x] I am creating this PR in reference to an issue.
Issue Description
This PR sets up a foundation for E2E testing along with two tests to have a starting point and verify whether CI jobs works correctly.
Related issue: #2007
Approach
TODOs before merging
- [x] Remove old electron tests and deps
- [x] Add commands for testing during development
- [x] Include a few tests
- [x] Setup one server, but handle single app and multi-app configs
- [x] Add changes to documentation (guides, repository pages, in-code descriptions)
- [x] A changelog entry is created automatically using the pull request title (do not manually add a changelog entry)
Thanks for opening this pull request!
- 🎉 We are excited about your hands-on contribution!
Wow, I'm super excited about this! This would be a major milestone for dashboard tests and release stability.
@mtrezza I think the core is ready, please take a look when you will have some time. I am not sure about developer guide for testing, is it clear enough?
This is amazing!
How could I run cypress using a locally running Parse Server deployment for debugging, instead of using docker?
@mtrezza Make sure it is started on the default port, has app ID set to hello and master key to world (default values in the Parse-Dashboard/parse-dashboard-config.json config).
Cypress is listening on port 4040, so I think there are some more steps necessary. Could you write a quick 1-2-3 instruction on how to run it with local Parse Server? I think we'd also need that in the contribution docs.
@visualfanatic just a friendly ping, it would be great if you could pick up this PR, it would be a long-awaited feature.