Item sort order - Checklist
Checklist
Area | Requirement | Check # | Scenario | Test case (green-pass / red-fail) | Passed? |
|---|---|---|---|---|---|
UI - create | Add a numeric sort order field to the item record | 1.1 | Create 1st item from UI and check "order" field (must be “1”) | Yes | |
| For newly created items via UI, increment the sort order field | 1.2 | Create 2nd item from UI and check "order" field (must be “2”) | see 1.1 | Yes |
|
| 1.3 | Create 3rd item with the same "order" value as 1st item has | Blocked by UI implementation |
|
|
| 1.4 | Create 4rd item with "order" value not in the sequence - ex.: 909 | Blocked by UI implementation |
|
|
|
| Validation of “order” field during CREATE | Blocked by UI implementation |
|
|
| 1.5 | There are 2 Holdings records. All holdings have the different number of items. | Yes | |
UI - Fast add |
| 1.6 | Create Instance, Holdings, Item via “Fast add” feature and check Item’s “order” field (must be “1”) | Yes | |
UI - Duplicate |
| 1.7 | Duplicate existing Item: | No (retest in scope of UXPROD-1625) | |
UI - Edit |
| 1.8 | There are 5 items with 1, 2, 3, 4, 5 sequence. | Blocked by UI implementation |
|
|
| 1.9 | There are 5 items with 1, 2, 3, 4, 5 sequence. | Blocked by UI implementation |
|
|
|
| Validation of “order” field during Edit | Blocked by UI implementation |
|
|
| 1.10 | Clear “order” field during Edit | Not clear if we will have validation. TBD @Maksym Ishchenko (Out of scope?) |
|
|
| 1.11 | Edit any Item field (barcode, status, tag) but don’t change “order” field “order” field shouldn’t be updated) | Yes | |
UI - Delete |
| 1.12 | Delete 1st item in the sequence and check other items "order" values (“order” field has not been changed in existing items) | Yes | |
UI - Move Item/Holdings |
| 1.13 | Move 1 item within different holdings of same instance ("order" value of moved item should be updated to the last in sequence) | Yes | |
|
| 1.14 | Move multiple items within different holdings of same instance ("order" value of moved items should be updated to the last in sequence in series) | see 1.13 | Yes |
|
| 1.15 | Move 1 item within holdings of different instances ("order" value of moved item should be updated to the last in sequence) | Yes | |
|
| 1.16 | Move Multiple items within holdings of different instances ("order" value of moved items should be updated to the last in sequence in series) | see 1.15 | Yes |
|
| 1.17 | Move 1 holding with multiple items within different instances | Yes | |
|
| 1.18 | Move multiple holdings with items within different instances | see 1.17 | Yes |
UI - Data import |
| 1.19 | Import multiple items. | https://foliotest.testrail.io/index.php?/cases/view/831984 |
|
|
| 1.20 | Import one item per record. | Yes | |
|
| 1.21 | Update Item (“order” field shouldn’t be changed/updated) | Yes | |
UI - Orders |
| 1.22 | Verify that Item(s) created via "Orders" app will have "order" field (multiple created Items should have sequence in “order” fields, ex.: 1, 2, 3, 4, 5, etc.) | Yes | |
UI - Bulk edit |
| 1.23 | Update Items (“order” field shouldn’t be changed/updated) | No (see MODBULKED-40) | |
API |Create |
| 2.1 | Create Check validation, must accept "numbers" only: | Yes | |
|
| 2.2 | Create 1st item without "order" field and check generated "order" field (“1”) | Yes | |
|
| 2.3 | Create 2nd item without "order" field (must be last in the list - “2”) | see 2.2 | Yes |
|
| 2.4 | Create 3rd item with the same "order" value as 1st item has (there are duplicates now with “1” value) | Yes | |
|
| 2.5 | Create 4th item with "order" value not in the sequence (ex.: 909) | see 2.4 | Yes |
|
| 2.6 | Create Item with specified "order" value = the last in sequence | see 2.4 | Yes |
|
| 2.7 | There are 2 Holdings records. All holdings have different number of items. | Yes | |
API | EDIT | Allow for libraries to change the sort order (numeric value) via API | 3.1 | Edit. Check validation, must accept "numbers" only: | Yes | |
| No validation needed for deduplication | 3.2 | There are 5 items with 1, 2, 3, 4, 5 sequence. | Yes | |
|
| 3.3 | There are 5 items with 1, 1, 2, 3, 4 sequence. | see 3.2 | Yes |
|
| 3.4 | Edit (remove). Send request with empty "order" field (“order” field value must be updated to the last in the sequence) | Yes | |
API | Batch create (mod-inventory) |
| 4.1 | Create Multiple Items without "order" field (created Items must have sequence like 1, 2, 3, 4, 5) | Yes | |
|
| 4.2 | Create multiple Items with filled "order" value (should retain specified values) | Yes | |
API | Batch edit (mod-inventory-storage) |
| 4.3 | Edit Multiple Items. No "order" in request (“order” field values must be re-generated, starting from the last in the sequence). | Yes | |
|
| 4.4 | Edit multiple Items with filled "order" value (should retain specified values) | Yes | |
Existing (migrated) records | For existing items: Populate numeric sort “order field with current” sort (based on Barcode) | 5.1 | Check that “order” field exists in migrated records. | How to verify that items are sorted by new “order” actually? | Yes |
RTAC table of Locate (only API check) | Add sort order to the RTAC response
| 6.1 | Add items with "itemDisplayOrder" fields filled and check mod-rtac response | Yes | |
|
| 6.2 | Add items with "itemDisplayOrder" fields filled and check edge-rtac BATCH response /rtac | Yes | |
|
| 6.3 | Add items with "itemDisplayOrder" fields filled and check single instance edge-rtac response /rtac/{instanceId} | Yes | |
Load test | RTAC |
| 7.1 | 15000 Items in 1 Holdings and check “itemDisplayOrder” | How to generate such numbers? - Used existing record: | No |
Load test | mod-inventory |
| 7.2 | 15000 Items in 1 Holdings and check “itemDisplayOrder” | Yes | |
ECS |
| 8.1 | There are 2 Holdings records (each in different member tenants). | Yes | |
|
| 8.2 | Update ownership of Holdings and verify the order of items (“order” values shouldn’t change) | Yes | |
|
| 8.3 | Update ownership of 1 Item and verify the order of moved item (“order” value should be regenerated) | https://foliotest.testrail.io/index.php?/cases/view/808510 There is Issue on UI, but works via API | Yes |
|
| 8.4 | Update ownership of multiple Items and verify the order of moved items (“order” value should be regenerated) |