|
In scope:
- Any remaining Data Import Critical Path Tests (Jira P2s) not finished on the previous feature
UXPROD-3839
Closed
- Data Import Critical Path Tests (Jira P3s)
- If any Data Import Critical Path Tests remain at the end of Quesnelia, move to a new Ramsons feature
- After Data Import Smoke and Critical Path tests are finished, check for other teams' remaining Smoke and Critical Path tests before moving on to further Folijet E2E tests
Out of scope:
- Individual unit tests (covered by RTL/Jest work)
- Performance/stability tests for large files (covered by the Stability feature)
- Smoke and Critical Path tests for new functionality (should be linked to the feature for the functionality, in the release that the feature is completed in)
Within the tests:
- Will need to configure the environment
- Will need appropriate MARC/EDIFACT files (1 record in the file when possible)
- Will need the appropriate profiles
- Test covers the workflow from profile creation through finishing the UI log
- Reset environment after tests
After the tests are written
- Confirm that they are running and passing on a regular basis
- Fix any problems identified during the automated runs
- Retire the manual TestRail case(s) that the automated test replaces
- See PO if any questions
- See description here for updating TestRail
- If possible, add recording of the automated test to the Jira, to show it working
|