Batch Importer (Bib/Acq) (UXPROD-47)

[UXPROD-4076] NFR: UI end-to-end tests tech debt for Folijet (Quesnelia R1 2024) Created: 20/Feb/23  Updated: 28/Dec/23

Status: In Progress
Project: UX Product
Components: None
Affects versions: None
Fix versions: Quesnelia (R1 2024)
Parent: Batch Importer (Bib/Acq)

Type: New Feature Priority: P2
Reporter: Ann-Marie Breaux (Inactive) Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: AQA, data-import, epam-folijet, standing-feature, ui-e-to-e-testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Continues
continues UXPROD-3839 NFR: UI end-to-end tests tech debt fo... Closed
is continued by UXPROD-4236 NFR: UI end-to-end tests tech debt fo... Open
Defines
defines UXPROD-47 Batch Importer (Bib/Acq) Analysis Complete
is defined by FAT-7316 Implement e-2-e automation of test ca... Blocked
is defined by FAT-2686 Implement e-2-e automation of test ca... Blocked
is defined by FAT-2687 Implement e-2-e automation of test ca... Blocked
is defined by FAT-7762 Implement e-2-e automation of test ca... In Refinement
Release: Quesnelia (R1 2024)
Epic Link: Batch Importer (Bib/Acq)
Front End Estimate: XXL < 30 days
Front End Estimator: Oleksandr Bashtynskyi
Front-End Confidence factor: 90%
Back End Estimate: Out of scope
Development Team: Folijet
PO Rank: 50
Rank: Cornell (Full Sum 2021): R5

 Description   

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

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