parse-community / parse-community/parse-dashboard
Add UI tests to CI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
The lack of UI tests in the CI process makes it difficult to identify bugs before release. That leads to severe bugs likely to make it into release, e.g.:
- https://github.com/parse-community/parse-dashboard/issues/1991
- https://github.com/parse-community/parse-dashboard/issues/1994
- https://github.com/parse-community/parse-dashboard/issues/2006
- https://github.com/parse-community/parse-dashboard/issues/2194
The current manual testing before merging a PR is not reliable nor scalable.
Feature / Enhancement Description
Add UI tests to CI, starting with just a few basic tests as guidance on how to write these tests, that can be extended over time.
Example Use Case
n/a
Alternatives / Workarounds
Manual testing which is not reliable or scalable.
3rd Party References
n/a
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, test suite, or CI entry point. Start by locating the dashboard's UI-test setup and CI configuration, then add a small basic test set and verify those tests run successfully in CI; done means the initial tests provide guidance and execute before merges.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, frontend, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100