Review of CCE Regression Testing

This page was created because of https://openlmis.atlassian.net/browse/OLMIS-5225.

What CCE manual tests cover:

Test Case	What it checks?	Should be tested manually?	Should be tested with Functional Test?	Additional notes

Test Case	What it checks?	Should be tested manually?	Should be tested with Functional Test?	Additional notes
OLMIS-4230: Viewing and dismissing RTM alerts	Whether a given inventory item has alerts and appropriate status; whether a report is displayed properly	No	Yes	Report should be tested manually.
OLMIS-3681: Filtering by functional status	Whether it is possible to filter inventories by Functional Status with appropriate options; checks if buttons work in a proper way; whether filtering shows appropriate equipment	No	Yes	Merge with OLMIS-3005
OLMIS-3679: Filtering by facility and program	Whether a proper list of devices is displayed after a filtered search	No	Yes (displayed list)	The part with checking dropdown placing should be removed.
OLMIS-3674: Spacing in The Edit Equipment Details	Checks spacing after adding equipment	No	No	We think that it isn't something which should have its own test case.
OLMIS-3658: User rights	Whether user with proper rights can add and edit inventory item; user without these rights doesn't have this possibility	No	Yes	Merge with OLMIS-3009
OMIS-3650: Adding a solar device with battery	Whether adding and editing inventory items works properly for a specific device	No	Yes
OLMIS-3048: Notification of nonfunctional CCE	Whether an email template after changing device's functional status is sent and is proper	Yes	No	There should be a Contract Test for this test case in the future. It can be done when there will be a pattern to test emails.
OLMIS-3052: The Manage Cold Chain Equipment Catalog screen	Checks uploading a file	Yes	No	API for uploading and exporting CCE catalog should be tested using contract test. We can leave this manual test case to check whether the UI component works properly.
OLMIS-3009: The inventory items list	Whether there are appropriate columns for the table with inventory items list	No	Yes	Merge with checking user rights.
OLMIS-3006: Editing devices	Whether it is possible to add and edit an inventory item	No	Yes
OLMIS-3005: The Equipment Functional Status model	Whether changing the functional status for an inventory item works properly	No	Yes
OLMIS-3000: Adding a new CCE device	Whether it is possible to add and edit an inventory item	No	Yes
OLMIS-4507: Facility CCE Status message when there is no CCE at facility	Whether after converting requisition there is a proper Facility CCE status component	Yes	No, this is a typical edge case	Many steps requiring other services (requisition, fulfillment) before checking the status

Things to cover with Functional Tests:

Verify that user with proper rights has access to CCE Inventory screen + verify that columns in the inventory items list are displayed in the right order and the columns have proper fields
Verify that user can see a list of inventory items for the chosen facility and program and are displayed in alphabetic order
Verify that appropriate user can add new equipment
Verify that appropriate user can add new (specific) Solar equipment
Verify that appropriate user can edit equipment
Verify that changing functional statuses for a given inventory item works (one test for each functional status)
Verify that filtering by functional status works properly
Verify that user without proper rights can't see CCE Management tab

Test cases to cover with Contract Tests:

Verify that CCE catalog items are archived - https://openlmis.atlassian.net/browse/OLMIS-2999
Verify that exporting/importing CCE catalog works properly - https://openlmis.atlassian.net/browse/OLMIS-3431
Verify that providing CCE Inventory as FHIR Device works properly - https://openlmis.atlassian.net/browse/OLMIS-4037 (Low priority)

Results of the discussion about current manual tests’ quality:

Current manual tests for CCE are effective as there is a small number of bugs (27) in comparison with other services.
Creating a new manual test case which needs about 15 execution steps takes 1-2 hours. However, we avoid creating a new, rather updating an existing one.
Executing a manual test case with 15 steps usually lasts about 1h.
Experience and a wide range of knowledge of system are crucial to make sure that manual tests make sense.
Our current manual test cases check both happy paths and edge cases.
There are a few manual tests which could be exchanged fully in favor of functional tests.
There is a danger of duplications as some manual tests need to use the same paths as functional tests to check edge cases (one idea to deal with this issue is to use Functional Tests for common steps up to the point of dispersion and then to test the edge case manually).