Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-3419

NFR: UI end-to-end tests for Folijet (Morning Glory)

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Release:
      Morning Glory R2 2022
    • Epic Link:
    • Front End Estimate:
      XXL < 30 days
    • Back End Estimate:
      Out of scope
    • Front-End Confidence factor:
      High
    • Development Team:
      Folijet
    • Calculated Total Rank:
    • PO Rank:
      105

      Description

      Karate and E-to-E UI test tech debt should only take 15% of Folijet's capacity. Any beyond that, move to Nolana

      Current estimate; ca. 60 days for UI

      See list of available smoke use cases at FAT-552

      Current situation or problem: FOLIO does not have automated end-to-end tests and must rely on manual user tests. In Morning Glory, Folijet will focus on automating smoke test cases mainly for Inventory, plus a few for requests

      In scope:

      • Update for Morning Glory; any Data Import Smoke Tests left?
      • If not, write E-to-E tests for another app, or move on to Critical Path tests?

      Out of scope:

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

      Within the tests:

      • Will need to configure the environment
      • Will need appropriate MARC/EDIFACT files (1 record in the file)
      • 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
      • 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

      Use case(s)

      • See list of available smoke use cases at FAT-552

        TestRail: Results

          Attachments

            Issue Links

            continues

            New Feature - New feature requests UXPROD-3263 NFR: UI end-to-end tests for Data Import (Lotus)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            defines

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. UXPROD-47 Batch Importer (Bib/Acq)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Analysis Complete
            is defined by

            Tech Debt - FAT-812 Implement e-2-e automation of test case C598: Create new instance with add "New"

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-813 Implement e-2-e automation of test case C9200: Item status date updates

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-815 Implement e-2-e automation of test case C609: In Accordion Identifiers --> enter different type of identifiers

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-816 Implement e-2-e automation of test case C9215: In Accordion Title --> Test assigning a Preceding title

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-817 Implement e-2-e automation of test case C1294: Create a Holdings record as another user than the one that created the Instance

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-818 Implement e-2-e automation of test case C714: Mark an item as Missing

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-819 Implement e-2-e automation of test case C10930: Mark item withdrawn

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-820 Implement e-2-e automation of test case C11081: Verify item status filters retrieve items with that item status

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-821 Implement e-2-e automation of test case C3501: An item is being moved from one library location to another. Update the effective location for the item.

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-823 Implement e-2-e automation of test case C15850: Create a fast add record from Inventory. Monograph.

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-882 Implement e-2-e automation of test case C505: Settings (Inventory): Create, edit, delete material types

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-887 Implement e-2-e automation of test case C540: Make sure that request type filters are working properly

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-888 Implement e-2-e automation of test case C546: Create new request for "Page" type

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Tech Debt - FAT-889 Implement e-2-e automation of test case C556: Request: Edit requests. Make sure that edits are being saved.

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-890 Implement e-2-e automation of test case C747: Assign Tags to Request

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-891 Implement e-2-e automation of test case C2379: Test Request app sorting

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-1625 Implement e-2-e automation of test case C196769: Assign tags to an Instance record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - FAT-1626 Implement e-2-e automation of test case C343215: Filter instances by tags

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. FAT-1640 Review autotests results in folio Lotus

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

              Activity

                People

                Assignee:
                abreaux Ann-Marie Breaux
                Reporter:
                abreaux Ann-Marie Breaux
                Front End Estimator:
                Ivan Kryzhanovskyi Ivan Kryzhanovskyi
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases