UIs: add Cypress e2e test integration
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
From @pwei1018 :
> When you upgrade your UI, please also consider cypress e2e test integration (compatible). You probably don’t need to build any tests right now. Queue management team’s test:
> https://github.com/bcgov/queue-management/tree/master/appointment-frontend/cypress
> and pipeline:
> https://github.com/bcgov/queue-management/blob/master/.github/workflows/master-deploy.yaml
We need to discuss the requirements for this (and scope and timing and anything else, like creating tests).
This probably applies to all UIs, including:
- Business Filings UI
- Business Create UI
- Business Edit UI
- Namerequest UI?
- Name Examination UI?
- Assets UI?
- Business Search UI?
- BC Registry UI?
- etc
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the queue-management Cypress examples and its .github/workflows/master-deploy.yaml pipeline, then inventory the listed UIs: Business Filings, Create, Edit, Namerequest, Name Examination, Assets, Business Search, and BC Registry. The issue first requires agreement on requirements, scope, timing, and whether tests are needed; done cannot be determined until those decisions are made.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, github-actions, javascript
- Domain
- ci-cd, frontend, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100