Skip to main content
Version: Next

STD: Runfile List (RUNFILE-LIST)

Version: v1.0.0 Status: Draft SRS Source: docusaurus/docs/srs/runfile-list.md Domain: RUNFILE

Overview​

This document specifies tests for the Runfile List domain, which covers viewing, searching, filtering, sorting, and navigating processed run files.

Domain Characteristics:

  • Primary function: UI display and navigation (list view, row expansion, filtering)
  • Secondary function: Backend data retrieval, aggregation, and filtering
  • Multi-site support: Role-based site visibility and filtering
  • Configuration dependency: Archive mode, filter visibility, sort defaults

Test Method Rationale: Per Test Plan Section 3.3, UI Features domains use TM-UI as primary method with TM-MAN fallback. RUNFILE-LIST has significant backend filtering and sorting logic, so TM-API is used for list retrieval and filter validation while TM-UI handles user interaction flows.

Test Case Convention: Steps describe logical actions, not UI mechanics. Use "Navigate to Run Files page" or "Apply date filter", not "Click the Runs link" or "Select from dropdown with id=filter-date". This ensures test intent survives UI redesigns.

Coverage Summary​

REQ IDTitleACsTestsAC CoverageMethodGaps
REQ-RUNFILE-001Display Runfile List7TC-RUNFILE-001, TC-RUNFILE-002, TC-RUNFILE-003, TC-RUNFILE-0047/7 (100%)TM-UINone
REQ-RUNFILE-002Expand Runfile to View Mix Details6TC-RUNFILE-005, TC-RUNFILE-006, TC-RUNFILE-0076/6 (100%)TM-UINone
REQ-RUNFILE-003Search Runfiles4TC-RUNFILE-008, TC-RUNFILE-0094/4 (100%)TM-UINone
REQ-RUNFILE-004Filter Runfile List6TC-RUNFILE-010, TC-RUNFILE-011, TC-RUNFILE-0126/6 (100%)TM-UINone
REQ-RUNFILE-005Sort Runfile List5TC-RUNFILE-013, TC-RUNFILE-0145/5 (100%)TM-UINone
REQ-RUNFILE-006Navigate to Run Report2TC-RUNFILE-0152/2 (100%)TM-UINone
REQ-RUNFILE-007Configure Visible Columns2TC-RUNFILE-0162/2 (100%)TM-UINone
REQ-RUNFILE-008Display Run Status5TC-RUNFILE-017, TC-RUNFILE-0185/5 (100%)TM-UINone
REQ-RUNFILE-009Support Multi-Site Operation6TC-RUNFILE-019, TC-RUNFILE-020, TC-RUNFILE-0216/6 (100%)TM-HYBNone
REQ-RUNFILE-010Manage Run Tags6TC-RUNFILE-022, TC-RUNFILE-023, TC-RUNFILE-0246/6 (100%)TM-UINone
REQ-RUNFILE-011Organize Runfiles into Categorized Views3TC-RUNFILE-0253/3 (100%)TM-UINone
NFR-RUNFILE-001Performance3TC-RUNFILE-0263/3 (100%)TM-HYBNone

Totals: 12 REQs, 55 ACs, 26 Test Cases, 100% Coverage

Test Cases​

TC-RUNFILE-001: Runfile list displays with required metadata columns​

Verifies: REQ-RUNFILE-001 (AC1)

Method: TM-UI

Priority: High

Preconditions:

  • User logged in with at least Junior User role
  • At least one runfile has been imported and processed

Test Data:

  • Runfile with complete metadata (all columns populated)

Steps:

  1. Navigate to Run Files page
  2. Observe the runfile table columns

Expected Results:

  • AC1: Table displays columns: Date Uploaded, Date Modified, Run File Name, Mixes, Notifications, Westgard Status, Resolution Pending Status, Uploaded By, Run Creation Date, Plate Size

Automation Status: Automated

Jira: BT-601

TC-RUNFILE-002: Mix column displays mixes in Kit Configuration order​

Verifies: REQ-RUNFILE-001 (AC2)

Method: TM-UI

Priority: Medium

Preconditions:

  • Kit Configuration defines mix order: Mix-A, Mix-B, Mix-C
  • Runfile contains mixes in different order: Mix-C, Mix-A, Mix-B

Test Data:

  • Runfile with Mix-C, Mix-A, Mix-B imported from source file
  • Kit Configuration with order: Mix-A, Mix-B, Mix-C

Steps:

  1. Navigate to Run Files page
  2. Locate the test runfile
  3. Observe the Mixes column display order

Expected Results:

  • AC2: Mixes displayed as: Mix-A, Mix-B, Mix-C (Kit Configuration order, not import order)

Automation Status: Automated

Jira: BT-2809

TC-RUNFILE-003: Pagination controls and count display​

Verifies: REQ-RUNFILE-001 (AC3, AC4)

Method: TM-UI

Priority: High

Preconditions:

  • More runfiles exist than fit on a single page (e.g., 100 runfiles with page size 20)

Test Data:

  • 100 runfiles in system
  • Page size configured to 20

Steps:

  1. Navigate to Run Files page
  2. Observe pagination controls and count display
  3. Navigate to page 2
  4. Observe updated count display

Expected Results:

  • AC3: Pagination controls are present for navigating result set
  • AC4: Count display shows range and total (e.g., "Showing 1-20 of 100" on page 1)
  • AC4: Count display updates on navigation (e.g., "Showing 21-40 of 100" on page 2)

Automation Status: Automated

Jira: BT-668

TC-RUNFILE-004: Refresh preserves filter and sort state​

Verifies: REQ-RUNFILE-001 (AC5, AC6, AC7)

Method: TM-UI

Priority: High

Preconditions:

  • Multiple runfiles with varying upload dates and uploaders

Steps:

  1. Navigate to Run Files page
  2. Apply date filter (Uploaded Date = last 7 days)
  3. Apply sort (Date Modified, ascending)
  4. Note current filtered/sorted results
  5. Activate refresh control
  6. Observe list state after refresh

Expected Results:

  • AC5: List data reloads with fresh data from server
  • AC6: Date filter selection preserved after refresh
  • AC6: Sort order preserved after refresh
  • AC7 (Error - No runfiles): When no runfiles match filter, empty state message displayed
  • AC7 (Error - Retrieval fails): When data retrieval fails, error message with retry option displayed

Automation Status: Automated

Jira: BT-668

TC-RUNFILE-005: Expand row to view mix details​

Verifies: REQ-RUNFILE-002 (AC1, AC2, AC3)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile exists with at least one mix

Test Data:

  • Runfile with Mix-A: 5 targets, 96 wells, 48 samples, 2 notifications

Steps:

  1. Navigate to Run Files page
  2. Expand the test runfile row
  3. Observe expanded section content
  4. Collapse the row
  5. Observe collapsed state

Expected Results:

  • AC1: Expanded section displays columns: Mix, No of Targets, No of Wells, No of Samples, Notifications
  • AC1: Mix-A shows: 5 targets, 96 wells, 48 samples, 2 notifications
  • AC2: Multiple rows can be expanded simultaneously
  • AC3: Expanded row provides control to collapse

Automation Status: Automated

Jira: BT-601

TC-RUNFILE-006: Expand/collapse state constraints​

Verifies: REQ-RUNFILE-002 (AC4, AC5)

Method: TM-UI

Priority: Medium

Preconditions:

  • At least two runfiles available

Steps:

  1. Navigate to Run Files page
  2. Expand Row A
  3. Observe Row A expand control
  4. Observe Row B (collapsed) controls
  5. Collapse Row A
  6. Observe Row A controls

Expected Results:

  • AC4: Expanded Row A does not offer expand action (only collapse)
  • AC5: Collapsed Row B does not offer collapse action (only expand)
  • Controls toggle appropriately with state

Automation Status: Automated

Jira: BT-2809

TC-RUNFILE-007: Patient search context shows well-level details​

Verifies: REQ-RUNFILE-002 (AC6)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with patient identifier "PAT-001" in well A1, Mix-A, outcome "Positive"

Steps:

  1. Search for patient "PAT-001" using patient search
  2. Locate matching runfile in results
  3. Expand the runfile row
  4. Observe expanded section columns

Expected Results:

  • AC6: Expanded view shows columns: Well, Mix, Outcome (not standard mix details)
  • AC6: Well A1, Mix-A, Positive displayed for patient match

Automation Status: Automated

Jira: BT-144

TC-RUNFILE-008: Search by patient identifier (exact match)​

Verifies: REQ-RUNFILE-003 (AC1, AC3)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile A contains patient "PAT-001"
  • Runfile B contains patient "PAT-001-EXT"
  • Runfile C contains patient "OTHER-002"

Steps:

  1. Navigate to Run Files page
  2. Enter "PAT-001" in patient search field
  3. Submit search

Expected Results:

  • AC1: Search uses exact match for patient identifier
  • AC3: Only Runfile A displayed (exact match "PAT-001")
  • Runfile B not displayed (PAT-001-EXT is not exact match)
  • Runfile C not displayed (no match)

Automation Status: Automated

Jira: BT-144

TC-RUNFILE-009: Search by run file name (partial match)​

Verifies: REQ-RUNFILE-003 (AC2, AC3, AC4)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile "2024-01-15_Plate_A.csv" exists
  • Runfile "2024-01-15_Plate_B.csv" exists
  • Runfile "2024-01-20_Plate_A.csv" exists

Steps:

  1. Navigate to Run Files page
  2. Enter "Plate_A" in run name search field
  3. Submit search
  4. Clear search
  5. Verify all runfiles display when search empty

Expected Results:

  • AC2: Search uses partial match for run file name
  • AC3: Both "2024-01-15_Plate_A.csv" and "2024-01-20_Plate_A.csv" displayed
  • AC3: "2024-01-15_Plate_B.csv" not displayed (no match)
  • AC4: When search cleared, all runfiles matching other filters displayed

Automation Status: Automated

Jira: BT-668

TC-RUNFILE-010: Filter by date range​

Verifies: REQ-RUNFILE-004 (AC1)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile A: Uploaded 2024-01-10, Modified 2024-01-15
  • Runfile B: Uploaded 2024-01-12, Modified 2024-01-12
  • Runfile C: Uploaded 2024-01-20, Modified 2024-01-25

Steps:

  1. Navigate to Run Files page
  2. Apply Uploaded Date filter: 2024-01-10 to 2024-01-15
  3. Observe filtered results
  4. Clear filter
  5. Apply Modified Date filter: 2024-01-14 to 2024-01-16
  6. Observe filtered results

Expected Results:

  • AC1: Uploaded Date range 01-10 to 01-15 shows Runfile A, B (not C)
  • AC1: Modified Date range 01-14 to 01-16 shows Runfile A only

Automation Status: Automated

Jira: BT-602

TC-RUNFILE-011: Filter by discrete values with multi-select​

Verifies: REQ-RUNFILE-004 (AC2, AC3, AC4)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile A: Mix-A, Westgard Pass, No Resolution Pending, Uploaded by User1
  • Runfile B: Mix-B, Westgard Fail, Resolution Pending, Uploaded by User1
  • Runfile C: Mix-A, Westgard Pass, No Resolution Pending, Uploaded by User2

Steps:

  1. Navigate to Run Files page
  2. Apply Mix filter: select Mix-A
  3. Observe results (A, C visible)
  4. Add Mix filter: select Mix-B (now Mix-A AND Mix-B selected)
  5. Observe results (A, B, C visible)
  6. Apply Westgard Status filter: select Pass
  7. Observe results (A, C visible - combined with Mix filter)
  8. Apply Uploaded By filter: select User1
  9. Observe results (A only - all three filters combined)

Expected Results:

  • AC2: Mix filter supports multiple value selection
  • AC2: Westgard Status filter supports value selection
  • AC2: Resolution Pending Status filter available
  • AC2: Uploaded By filter supports value selection
  • AC3: Multiple values within single filter work as OR (Mix-A OR Mix-B)
  • AC4: Multiple different filters combine as AND (Mix AND Westgard AND Uploader)

Automation Status: Automated

Jira: BT-602

TC-RUNFILE-012: Filter visibility toggle preserves active filters​

Verifies: REQ-RUNFILE-004 (AC5, AC6)

Method: TM-UI

Priority: Medium

Preconditions:

  • Multiple runfiles available

Steps:

  1. Navigate to Run Files page
  2. Observe filter visibility default state
  3. Apply Mix filter: select Mix-A
  4. Note filtered result count
  5. Toggle filter visibility to hidden
  6. Observe result count (should remain same)
  7. Toggle filter visibility to shown
  8. Observe filter selection (should remain Mix-A)

Expected Results:

  • AC5: Toggling filter visibility does not clear active filters
  • AC5: Filtered results remain consistent when filters hidden
  • AC6: Filter section defaults to shown on page load

Automation Status: Automated

Jira: BT-668

TC-RUNFILE-013: Default sort order​

Verifies: REQ-RUNFILE-005 (AC1, AC2)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile A: Uploaded 2024-01-10
  • Runfile B: Uploaded 2024-01-15
  • Runfile C: Uploaded 2024-01-05

Steps:

  1. Navigate to Run Files page (fresh navigation, no prior sort)
  2. Observe sort indicator and list order

Expected Results:

  • AC1: Sortable columns include: Date Uploaded, Date Modified, Uploaded By
  • AC2: Default sort is Date Uploaded, descending (newest first)
  • AC2: Order displayed: B, A, C (Jan 15, Jan 10, Jan 5)

Automation Status: Automated

Jira: BT-601

TC-RUNFILE-014: Sort toggle and single-column constraint​

Verifies: REQ-RUNFILE-005 (AC3, AC4, AC5)

Method: TM-UI

Priority: High

Preconditions:

  • Multiple runfiles with varying dates

Steps:

  1. Navigate to Run Files page
  2. Activate sort on Date Uploaded column
  3. Observe sort direction (should toggle to ascending)
  4. Activate sort on Date Uploaded again
  5. Observe sort direction (should toggle to descending)
  6. Activate sort on Date Modified column
  7. Observe which column shows sort indicator

Expected Results:

  • AC3: Repeated activation toggles between ascending and descending
  • AC4: Current sort column and direction indicated visually
  • AC5: Only one column sorted at a time (Date Uploaded indicator removed when Date Modified activated)

Automation Status: Automated

Jira: BT-601

TC-RUNFILE-015: Navigate to run report​

Verifies: REQ-RUNFILE-006 (AC1, AC2)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile "TestRun_001.csv" exists

Steps:

  1. Navigate to Run Files page
  2. Select runfile row "TestRun_001.csv" (not the expand control)
  3. Observe navigation result
  4. Observe navigation menu/breadcrumb

Expected Results:

  • AC1: Navigation opens run report for "TestRun_001.csv"
  • AC2: Navigation context shows "TestRun_001.csv" as current selection (e.g., in breadcrumb or nav menu)

Automation Status: Automated

Jira: BT-603

TC-RUNFILE-016: Configure visible columns​

Verifies: REQ-RUNFILE-007 (AC1, AC2)

Method: TM-UI

Priority: Medium

Preconditions:

  • User on Run Files page

Steps:

  1. Navigate to Run Files page
  2. Observe all columns visible (default state)
  3. Open column configuration mechanism
  4. Deselect "Plate Size" column
  5. Confirm selection
  6. Observe table columns

Expected Results:

  • AC1: Column visibility toggle mechanism available
  • AC2: All columns visible by default
  • AC1: Deselected column (Plate Size) hidden from table

Automation Status: Automated

Jira: BT-2702

TC-RUNFILE-017: Run status values based on well states​

Verifies: REQ-RUNFILE-008 (AC1, AC2, AC3, AC4)

Method: TM-UI

Priority: Critical

Preconditions:

  • Runfile A: All patient wells without errors
  • Runfile B: All patient wells exported
  • Runfile C: Some wells with errors, at least one exportable
  • Runfile D: All patient wells in error state

Steps:

  1. Navigate to Run Files page
  2. Locate each test runfile
  3. Observe Run Status column values

Expected Results:

  • AC1: Runfile A shows "All wells ready for export"
  • AC4: Runfile B shows "All wells exported"
  • AC2: Runfile C shows "Some wells ready for export with errors to resolve"
  • AC3: Runfile D shows "No export - errors to resolve"

Automation Status: Automated

Jira: BT-3684

Verifies: REQ-RUNFILE-008 (AC5)

Method: TM-UI

Priority: High

Preconditions:

  • Two runs with 1:2s Westgard errors for same patient/mix/control
  • Run #1: Latest date
  • Run #2: Earliest date

Steps:

  1. Import Run #2 (earliest date) with 1:2s error
  2. Import Run #1 (latest date) with 1:2s error
  3. Open Run #2 and skip auto reanalysis
  4. Observe PC outcome
  5. Activate reanalysis
  6. Observe PC outcome change

Expected Results:

  • AC5: Before reanalysis, PC outcome shows "Control Passed"
  • AC5: After reanalysis, PC outcome shows "Previous westgard fail"
  • AC5: Westgard-related status reflected in Run Status column

Automation Status: Automated

Jira: BT-3247

TC-RUNFILE-019: Manager site filter and column visibility​

Verifies: REQ-RUNFILE-009 (AC1, AC2, AC6)

Method: TM-HYB

Priority: High

Preconditions:

  • Multi-site deployment with at least two sites configured
  • Manager user account
  • Junior user account

Steps:

  1. Log in as Manager
  2. Navigate to Run Files page
  3. Observe Site filter availability
  4. Observe Site column visibility
  5. Log out and log in as Junior user
  6. Navigate to Run Files page
  7. Observe Site filter and column visibility

Expected Results:

  • AC1: Manager sees Site filter control
  • AC2: Manager sees Site column in table
  • AC6: Junior user does not see Site filter
  • AC6: Junior user does not see Site column

Automation Status: Automated

Jira: BT-3035

TC-RUNFILE-020: Super-admin site selection and management​

Verifies: REQ-RUNFILE-009 (AC3, AC4)

Method: TM-HYB

Priority: High

Preconditions:

  • Multi-site deployment
  • Super-admin user account
  • At least two enabled sites

Steps:

  1. Log in as Super-Admin
  2. Observe site selection control in header
  3. Note current site name
  4. Activate site selection
  5. Select different site
  6. Observe site change
  7. Navigate to site management
  8. Disable a site
  9. Observe site list

Expected Results:

  • AC3: Site selection control displays current site name
  • AC3: Dropdown shows list of enabled sites
  • AC3: Selecting different site changes current context
  • AC4: Super-admin can enable/disable sites

Automation Status: Manual (requires admin configuration)

Jira: BT-3035

TC-RUNFILE-021: Disabled site login prevention​

Verifies: REQ-RUNFILE-009 (AC5)

Method: TM-HYB

Priority: Critical

Preconditions:

  • Multi-site deployment
  • Super-admin has disabled Site B
  • User account associated with Site B

Steps:

  1. As Super-Admin, disable Site B
  2. Log out
  3. Attempt to log in as user associated with Site B
  4. Observe login result

Expected Results:

  • AC5: Login attempt to disabled site is rejected
  • AC5: Appropriate error message displayed

Automation Status: Manual (requires site configuration changes)

Jira: BT-3035

TC-RUNFILE-022: Tag display in runfile list​

Verifies: REQ-RUNFILE-010 (AC1)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile A has tags: "Priority", "Review"
  • Runfile B has no tags

Steps:

  1. Navigate to Run Files page
  2. Observe Tags column for Runfile A
  3. Observe Tags column for Runfile B

Expected Results:

  • AC1: Runfile A shows "Priority, Review" in Tags column
  • AC1: Runfile B shows empty/no tags indicator

Automation Status: Automated

Jira: BT-4300

TC-RUNFILE-023: Attach and replace tags​

Verifies: REQ-RUNFILE-010 (AC2, AC3)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile A with existing tag "Old-Tag"
  • Tags "New-Tag-1", "New-Tag-2" configured in system

Steps:

  1. Navigate to Run Files page
  2. Select tag control for Runfile A
  3. Select "New-Tag-1" and "New-Tag-2"
  4. Confirm selection
  5. Observe Runfile A tags

Expected Results:

  • AC2: User can attach one or more tags to run
  • AC3: New tags replace existing tags (shows "New-Tag-1, New-Tag-2", not "Old-Tag, New-Tag-1, New-Tag-2")

Automation Status: Automated

Jira: BT-4300

TC-RUNFILE-024: Bulk tag operation scope confirmation​

Verifies: REQ-RUNFILE-010 (AC4, AC5, AC6)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile A and Runfile B exist, neither has tags
  • Tag "Bulk-Tag" configured
  • Archive Mode enabled in client configuration

Steps:

  1. Navigate to Run Files page
  2. Select both Runfile A and Runfile B
  3. Apply "Bulk-Tag" via Runfile A's tag control
  4. Observe scope confirmation dialog
  5. Select "Apply only one"
  6. Observe tags on A and B
  7. Repeat steps 2-4
  8. Select "Confirm"
  9. Observe tags on A and B
  10. Repeat steps 2-4
  11. Select "Cancel"
  12. Observe tags on A and B
  13. Observe archive visibility toggle availability

Expected Results:

  • AC4: Scope confirmation dialog appears when multiple runs selected
  • AC5 (Apply only one): Only initiating row gets tags
  • AC5 (Confirm): All selected runs get tags
  • AC5 (Cancel): No tags applied
  • AC6: Archive visibility toggle available when Archive Mode enabled

Automation Status: Automated

Jira: BT-4300

TC-RUNFILE-025: Categorized views filter by archive and export state​

Verifies: REQ-RUNFILE-011 (AC1, AC2, AC3)

Method: TM-UI

Priority: High

Preconditions:

  • Run A: Has archive tag, has exported wells
  • Run B: Has archive tag, no exported wells
  • Run C: No archive tag, fully exported
  • Run D: No archive tag, not exported

Steps:

  1. Navigate to Run Files page
  2. Select Active Runs view
  3. Observe visible runs
  4. Select Exported Runs view
  5. Observe visible runs
  6. Select Archived Runs view
  7. Observe visible runs

Expected Results:

  • AC1: Active Runs view shows only Run D (not archived, not fully exported)
  • AC2: Exported Runs view shows only Run C (not archived, fully exported)
  • AC3: Archived Runs view shows Run A and Run B (has archive tags)

Automation Status: Automated

Jira: BT-4488

TC-RUNFILE-026: Performance requirements​

Verifies: NFR-RUNFILE-001 (AC1, AC2, AC3)

Method: TM-HYB

Priority: Medium

Preconditions:

  • Test environment with representative data volume
  • Performance monitoring enabled

Steps:

  1. Navigate to Run Files page (fresh load)
  2. Measure initial load time
  3. Apply a filter
  4. Measure repopulation time
  5. Resize viewport
  6. Observe interface adaptation

Expected Results:

  • AC1: Initial screen population completes within acceptable response time (per NFR-001: 10 seconds)
  • AC2: Screen repopulation after filter completes within acceptable response time
  • AC3: Interface adapts responsively when viewport resized

Automation Status: Manual (requires performance instrumentation)

Jira: [Pending]

Deviation: TM-MAN used for AC1/AC2 timing measurement. Remediation: Add automated performance assertions in CI pipeline.

Gap Analysis​

No gaps identified. All 55 acceptance criteria have test coverage.

Coverage by AC Type​

AC CategoryCountCoveredNotes
Display/Rendering1818Verified via TM-UI
Interaction/Filtering2020Verified via TM-UI
Navigation44Verified via TM-UI
Multi-Site/Permissions66Verified via TM-HYB
Performance (NFR)33Verified via TM-HYB
Error Handling44Verified via TM-UI

Traceability to Existing Tests​

Test CaseJira TestAutomation
TC-RUNFILE-001, TC-RUNFILE-013, TC-RUNFILE-014BT-601Selenium
TC-RUNFILE-010, TC-RUNFILE-011BT-602Selenium
TC-RUNFILE-015BT-603Selenium
TC-RUNFILE-003, TC-RUNFILE-004, TC-RUNFILE-009, TC-RUNFILE-012BT-668Selenium
TC-RUNFILE-008BT-144Selenium
TC-RUNFILE-002, TC-RUNFILE-005, TC-RUNFILE-006BT-2809Selenium
TC-RUNFILE-016BT-2702Selenium
TC-RUNFILE-017BT-3684Selenium
TC-RUNFILE-018BT-3247Behat
TC-RUNFILE-019, TC-RUNFILE-020, TC-RUNFILE-021BT-3035Behat/Manual
TC-RUNFILE-022, TC-RUNFILE-023, TC-RUNFILE-024BT-4300Selenium
TC-RUNFILE-025BT-4488Selenium

Notes​

  • RUNFILE-LIST is a UI-heavy domain with significant filtering and sorting backend logic
  • Existing Gherkin tests in SRS provide base scenarios; this STD formalizes method and coverage
  • Multi-site tests (TC-RUNFILE-019 through TC-RUNFILE-021) require multi-site deployment configuration
  • Performance tests (TC-RUNFILE-026) require environment-specific thresholds; defer to NFR-001 for values
  • Mix ordering (TC-RUNFILE-002) depends on Kit Configuration state; ensure fixture consistency