[UXPROD-3962] NFR: UI end-to-end tests tech debt for Vega (Poppy R2 2023) Created: 11/Jan/23  Updated: 23/Jun/23  Resolved: 23/Jun/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)

Type: New Feature Priority: P2
Reporter: Stephanie Buck Assignee: Stephanie Buck
Resolution: Done Votes: 0
Labels: AQA-backlog, NFR
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-4122 NFR: UI end-to-end tests for Vega (Po... Closed
Defines
is defined by FAT-2545 Implement e-2-e automation of test ca... Closed
is defined by FAT-2628 Implement e-2-e automation of test ca... Closed
is defined by FAT-2646 Implement e-2-e automation of test ca... Closed
is defined by FAT-2648 Implement e-2-e automation of test ca... Closed
is defined by FAT-2649 Implement e-2-e automation of test ca... Closed
is defined by FAT-2732 Implement e-2-e automation of test ca... Closed
is defined by FAT-4398 Implement e-2-e automation of test ca... Closed
is defined by FAT-2593 Implement e-2-e automation of test ca... Closed
is defined by FAT-2604 Implement e-2-e automation of test ca... Closed
is defined by FAT-2605 Implement e-2-e automation of test ca... Closed
is defined by FAT-2607 Implement e-2-e automation of test ca... Closed
is defined by FAT-2630 Implement e-2-e automation of test ca... Closed
is defined by FAT-2631 Implement e-2-e automation of test ca... Closed
is defined by FAT-2647 Implement e-2-e automation of test ca... Closed
is defined by FAT-6324 Implement e-2-e automation of test ca... Closed
is defined by FAT-1390 Implement e-2-e automation of test ca... Closed
is defined by FAT-1393 Implement e-2-e automation of test ca... Closed
is defined by FAT-1396 Implement e-2-e automation of test ca... Closed
Front End Estimator: Oleksandr Bashtynskyi
Development Team: Vega
Rank: Cornell (Full Sum 2021): R5

 Description   

 

In scope:

  • Critical Path Tests should be automated in order regarding their priority (Critical, High, Medium, Low)
  • If any Critical Path Tests remain at the end of Orchid, it should be move to this Poppy feature

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 before test execution
  • 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

Generated at Fri Feb 09 00:36:11 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.