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

[UXPROD-3081] NFR: UI end-to-end tests for Data Import (Kiwi) Created: 25/May/21  Updated: 15/Feb/22  Resolved: 04/Oct/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Kiwi (R3 2021)
Parent: Batch Importer (Bib/Acq)

Type: New Feature Priority: P3
Reporter: Ann-Marie Breaux (Inactive) Assignee: Ann-Marie Breaux (Inactive)
Resolution: Done Votes: 0
Labels: data-import, epam-folijet, ui-e-to-e-testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Continues
is continued by UXPROD-3263 NFR: UI end-to-end tests for Data Imp... Closed
Defines
is defined by FAT-898 Spike: learn how to build UI e-2-e te... Closed
is defined by FAT-915 Spike: Decide on an approach for crea... Closed
is defined by FAT-957 Testing activity management Closed
is defined by FAT-1057 e-2-e test cases preparation phase 2 Closed
is defined by UIDATIMP-981 e-2-e test cases preparation Closed
is defined by FAT-743 Implement e-2-e automation of test ca... Closed
is defined by FAT-744 Implement e-2-e automation of test ca... Closed
is defined by FAT-745 Implement e-2-e automation of test ca... Closed
is defined by FAT-746 Implement e-2-e automation of test ca... Closed
is defined by FAT-747 Implement e-2-e automation of test ca... Closed
is defined by FAT-748 Implement e-2-e automation of test ca... Closed
is defined by FAT-749 Implement e-2-e automation of test ca... Closed
is defined by FAT-751 Implement e-2-e automation of test ca... Closed
is defined by FAT-752 Implement e-2-e automation of test ca... Closed
is defined by FAT-753 Implement e-2-e automation of test ca... Closed
is defined by FAT-754 Implement e-2-e automation of test ca... Closed
is defined by FAT-755 Implement e-2-e automation of test ca... Closed
is defined by FAT-573 Estimate e-2-e automation of test cas... Closed
is defined by FAT-574 Estimate e-2-e automation of test cas... Closed
is defined by FAT-575 Estimate e-2-e automation of test cas... Closed
is defined by FAT-576 Estimate e-2-e automation of test cas... Closed
is defined by FAT-577 Estimate e-2-e automation of test cas... Closed
is defined by FAT-578 Estimate e-2-e automation of test cas... Closed
is defined by FAT-579 Estimate e-2-e automation of test cas... Closed
is defined by FAT-580 Estimate e-2-e automation of test cas... Closed
is defined by FAT-581 Estimate e-2-e automation of test cas... Closed
is defined by FAT-582 Estimate e-2-e automation of test cas... Closed
is defined by FAT-583 Estimate e-2-e automation of test cas... Closed
is defined by FAT-584 Estimate e-2-e automation of test cas... Closed
is defined by FAT-585 Estimate e-2-e automation of test cas... Closed
is defined by FAT-586 Estimate e-2-e automation of test cas... Closed
is defined by FAT-587 Estimate e-2-e automation of test cas... Closed
is defined by FAT-588 Estimate e-2-e automation of test cas... Closed
is defined by FAT-589 Estimate e-2-e automation of test cas... Closed
is defined by FAT-590 Estimate e-2-e automation of test cas... Closed
is defined by FAT-1058 Test plan update and presentation Closed
Relates
relates to UXPROD-47 Batch Importer (Bib/Acq) Analysis Complete
Epic Link: Batch Importer (Bib/Acq)
Front End Estimate: Jumbo: > 45 days
Front End Estimator: Ivan Kryzhanovskyi
Front-End Confidence factor: Low
Development Team: Folijet
PO Rank: 85

 Description   

Current estimate; ca. 60 days for UI

Current situation or problem: Data Import does not have automated end-to-end tests

In scope:

  • Happy path scenarios
  • Most important negative path scenarios

Out of scope:

  • Individual unit tests (covered by RTL/Jest work)
  • Performance/stability tests for large files (covered by the Stability feature)

Use case(s)

  • See list of use cases at add link


 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 26/Jul/21 ]

Per Former user, we should update the TestRail test cases to make them more accurate before working on this.

  • Plan for a a couple meetings with Ann-Marie Breaux and Former user to review and update in TestRail.
    • Need to be clear on the scope for each test (e.g. creating all profiles needed for an import, then doing the import, then reviewing the log)
  • Size of files
    • Usually use a small file for the tests, since these are covering functionality, not performance/stability
    • Have separate tests for a large files for performance/stability and run less often; keep separate from functional tests
  • Environment for running them
    • Can be run against any environment; for small files, hosted reference envs probably best (folio-snapshot); for larger files, then either Rancher Perf Env (Shared Rancher) or maybe folio-snapshot-load, but it's not as powerful
  • Negative tests
    • Usually created at same time as positive tests, but focus first on happy path
    • In test outline, add the most frequent negative tests, and come back to those after the positive ones
  • Perhaps create new end-to-end cases that will merge some of the old cases in TestRail
  • Review the issues linked to this Jira and rename/revise
  • Probably do not need separate estimate and create Jiras for each test scenario; just one issue per scenario
  • Decide on schedule for how often these tests will be run
    • Make regression execution once per sprint
Comment by Ann-Marie Breaux (Inactive) [ 25/Aug/21 ]

Grooming: Former user met with Anton Emelianov to ensure the main workflows are outlined; one the Bigtest work is closer to done, then will meet with the Fjet UI devs to plan the priority/sequencing of the tests.

Comment by Ann-Marie Breaux (Inactive) [ 04/Oct/21 ]

Closed most of these issues and replaced with more accurate issues. Planning completed in Kiwi, but cannot begin writing tests until late in Lotus, due to BigTest replacements being higher priority than these E-to-E UI tests

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