Skip to main content
Version: Next

STD: Runfile Report (RUNRPT)

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

Overview​

This document specifies tests for the Runfile Report domain, which covers viewing and managing individual run file contents, including well-level data display, quality control analysis, result resolution, and export capabilities.

Domain Characteristics:

  • Primary function: UI display and user interaction (well table, widgets, filtering)
  • Secondary function: Backend processing (LIMS export, validation, re-analysis)
  • Configuration dependency: Client-specific widgets, export formats, multi-site settings

Test Method Rationale:

Per Test Plan SS3.3, UI Features domains use TM-UI as primary method with TM-MAN fallback. RUNRPT also has backend logic for LIMS export and validation, so TM-API is used for export file generation and validation logic. Print/export functions use TM-HYB for end-to-end verification.

Test Case Convention:

Steps describe logical actions, not UI mechanics. Use "Open runfile report" or "Select well A1", not "Click the row with data-well=A1". This ensures test intent survives UI redesigns.

Coverage Summary​

REQ IDTitleACsTestsAC CoverageMethodGaps
REQ-RUNRPT-001Display Run File Contents5TC-RUNRPT-001, TC-RUNRPT-002, TC-RUNRPT-046, TC-RUNRPT-0475/5 (100%)TM-UINone
REQ-RUNRPT-002Access Analytical Widgets3TC-RUNRPT-0033/3 (100%)TM-UINone
REQ-RUNRPT-003Re-analyze Run File3TC-RUNRPT-0043/3 (100%)TM-UINone
REQ-RUNRPT-004Print Run File Report7TC-RUNRPT-005, TC-RUNRPT-0067/7 (100%)TM-HYBNone
REQ-RUNRPT-005View Run Information2TC-RUNRPT-0072/2 (100%)TM-UINone
REQ-RUNRPT-006Edit Well Information6TC-RUNRPT-008, TC-RUNRPT-009, TC-RUNRPT-040, TC-RUNRPT-041, TC-RUNRPT-0426/6 (100%)TM-UINone
REQ-RUNRPT-007Manage Well Results6TC-RUNRPT-010, TC-RUNRPT-0116/6 (100%)TM-UINone
REQ-RUNRPT-008Export Run Results to LIMS14TC-RUNRPT-012, TC-RUNRPT-013, TC-RUNRPT-014, TC-RUNRPT-01514/14 (100%)TM-HYBNone
REQ-RUNRPT-009Sort Well Table4TC-RUNRPT-0164/4 (100%)TM-UINone
REQ-RUNRPT-010Filter Well Table6TC-RUNRPT-017, TC-RUNRPT-0186/6 (100%)TM-UINone
REQ-RUNRPT-011Display Amplification Curves6TC-RUNRPT-019, TC-RUNRPT-0206/6 (100%)TM-UINone
REQ-RUNRPT-012Provide Well Action Menu5TC-RUNRPT-0215/5 (100%)TM-UINone
REQ-RUNRPT-013Select Wells5TC-RUNRPT-0225/5 (100%)TM-UINone
REQ-RUNRPT-014Display Run File Notifications2TC-RUNRPT-023, TC-RUNRPT-043, TC-RUNRPT-044, TC-RUNRPT-045, TC-RUNRPT-048, TC-RUNRPT-0492/2 (100%)TM-UINone
REQ-RUNRPT-015Configure Composite Assay Outcomes3TC-RUNRPT-0243/3 (100%)TM-HYBNone
REQ-RUNRPT-016Display Accession History6TC-RUNRPT-025, TC-RUNRPT-0266/6 (100%)TM-UINone
REQ-RUNRPT-017Support Multi-Site Operation3TC-RUNRPT-0273/3 (100%)TM-UINone
REQ-RUNRPT-018Display Westgard QC Analysis4TC-RUNRPT-0284/4 (100%)TM-UINone
REQ-RUNRPT-019Display Assay Summary3TC-RUNRPT-0293/3 (100%)TM-UINone
REQ-RUNRPT-020Display Outcome Summary2TC-RUNRPT-0302/2 (100%)TM-UINone
REQ-RUNRPT-021Display Plate Map4TC-RUNRPT-0314/4 (100%)TM-UINone
REQ-RUNRPT-022Display Quantification Analysis6TC-RUNRPT-0326/6 (100%)TM-UINone
REQ-RUNRPT-023Bulk Edit Wells3TC-RUNRPT-0333/3 (100%)TM-UINone
REQ-RUNRPT-024Bulk Manage Results3TC-RUNRPT-0343/3 (100%)TM-UINone
REQ-RUNRPT-025Display System Flags3TC-RUNRPT-0353/3 (100%)TM-UINone
REQ-RUNRPT-026Warn Before Losing Unsaved Changes2TC-RUNRPT-0362/2 (100%)TM-UINone
REQ-RUNRPT-027Persist Widget State4TC-RUNRPT-0374/4 (100%)TM-UINone
REQ-RUNRPT-028Validate Well Data6TC-RUNRPT-038, TC-RUNRPT-0396/6 (100%)TM-HYBNone
REQ-RUNRPT-029Run Calibration Chart Tab4TC-RUNRPT-0504/4 (100%)TM-UINone (@V3_1_0)
REQ-RUNRPT-030Target Selector for Run Calibration Chart3TC-RUNRPT-0513/3 (100%)TM-UINone (@V3_1_0)
REQ-RUNRPT-031Fetch and Display Calibration Data5TC-RUNRPT-052, TC-RUNRPT-0535/5 (100%)TM-UI, TM-APINone (@V3_1_0)
REQ-RUNRPT-032Highlight Current Run on Chart2TC-RUNRPT-0542/2 (100%)TM-UINone (@V3_1_0)
REQ-RUNRPT-033Run Calibration Chart Display3TC-RUNRPT-0553/3 (100%)TM-UINone (@V3_1_0)
REQ-RUNRPT-034Chart Settings Panel6TC-RUNRPT-056, TC-RUNRPT-0576/6 (100%)TM-UINone (@V3_1_0)
REQ-RUNRPT-035Draggable DF Lines in Run View4TC-RUNRPT-0584/4 (100%)TM-UINone (@V3_1_0)
REQ-RUNRPT-036Pin/Unpin Calibration Chart Widget3TC-RUNRPT-0593/3 (100%)TM-UINone (@V3_1_0)
REQ-RUNRPT-037Help Data for Run Calibration Chart2TC-RUNRPT-0602/2 (100%)TM-UINone (@V3_1_0)

Totals: 37 REQs, 151 ACs, 60 Test Cases, 100% Coverage

Test Cases​

TC-RUNRPT-001: Well table data display​

Verifies: REQ-RUNRPT-001 (AC1, AC2, AC3)

Method: TM-UI

Priority: Critical

Preconditions:

  • User logged in with at least Junior User role
  • Runfile exists with wells containing data for all columns

Test Data:

  • Runfile with multiple mixes, various sample types, results with CT/Quant values

Steps:

  1. Navigate to the runfile report
  2. Observe the well table columns
  3. Verify target display order

Expected Results:

  • AC1: Well table displays mix, well position, sample name, sample type, sample role, results, outcome, and available actions
  • AC2: Targets displayed in configured order from Mix and Targets configuration
  • AC3: Run identification and notification status visible in report header

Automation Status: Automated

Jira: BT-1063, BT-2726

TC-RUNRPT-002: Status indication and control display​

Verifies: REQ-RUNRPT-001 (AC4, AC5)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile with wells in various states: error, warning, patient sample OK, control sample OK

Test Data:

  • Well A1: Error state
  • Well A2: Warning state
  • Well A3: Patient sample (no issues)
  • Well A4: Control sample (passed)

Steps:

  1. Open the runfile report
  2. Observe visual differentiation for each well state
  3. Verify control wells show appropriate outcome

Expected Results:

  • AC4: Error, warning, patient, and control wells have distinct visual indication
  • AC5: Control wells display "Control Passed" (or similar) when no errors exist

Automation Status: Automated

Jira: BT-1139

TC-RUNRPT-003: Analytical widget access​

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

Method: TM-UI

Priority: High

Preconditions:

  • User on runfile report
  • Client configuration includes all widgets

Steps:

  1. Identify available widget buttons
  2. Select each widget type in turn
  3. Verify widgets limited by client configuration (use a client with restricted widgets)

Expected Results:

  • AC1: Assay Summary, Outcome Summary, Westgard, Plate Map, and Quantification widgets are accessible
  • AC2: Selecting a widget opens the corresponding view
  • AC3: Only widgets enabled in client configuration are available

Automation Status: Automated

Jira: BT-1063

TC-RUNRPT-004: Re-analyze run file​

Verifies: REQ-RUNRPT-003 (AC1, AC2, AC3)

Method: TM-UI

Priority: Critical

Preconditions:

  • Runfile imported without auto re-analysis
  • Prior runfile exists with Westgard error for same control

Test Data:

  • Run A (newer): Control "PC" initially shows "Control Passed"
  • Run B (older): Same control has Westgard failure

Steps:

  1. Open Run A, skip auto reanalysis if prompted
  2. Verify PC outcome is "Control Passed"
  3. Trigger re-analysis
  4. Verify outcome recalculated to reflect Westgard history

Expected Results:

  • AC1: Full recalculation performed when re-analysis triggered
  • AC2: Westgard errors removed and reapplied based on current rules
  • AC3: Previously disabled mixes remain disabled unless explicitly included

Automation Status: Automated

Jira: BT-1105, BT-1928, BT-2722

TC-RUNRPT-005: Print options display​

Verifies: REQ-RUNRPT-004 (AC1, AC2, AC3, AC7)

Method: TM-HYB

Priority: High

Preconditions:

  • User on runfile report
  • Client has specific print options configured

Steps:

  1. Initiate print action
  2. Observe available print options
  3. Verify default selection state
  4. Test with client that has restricted options

Expected Results:

  • AC1: Print options are selectable (checkboxes or similar)
  • AC2: All options selected by default
  • AC3: Available options include Assay Summary, Westgard, Graphs, Comments, Wells, Accession History
  • AC7: Client-specific options only shown when enabled for that client

Automation Status: Automated (Browser)

Jira: BT-1108, BT-1109

TC-RUNRPT-006: Print output generation​

Verifies: REQ-RUNRPT-004 (AC4, AC5, AC6)

Method: TM-HYB

Priority: High

Preconditions:

  • User on runfile report with print options available

Steps:

  1. Select specific sections (e.g., Assay Summary, Wells)
  2. Confirm print
  3. Verify generated document includes selected sections
  4. Test with no sections selected - verify full well table included
  5. Test Wells option behavior for result visibility

Expected Results:

  • AC4: Printable document generated with selected content only
  • AC5: Full well table included when no specific sections selected
  • AC6: Wells option controls whether well results appear in printout

Automation Status: Automated (Browser)

Jira: BT-1110, BT-1111, BT-1112, BT-2474

TC-RUNRPT-007: View run information​

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

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with complete metadata

Steps:

  1. Open runfile report
  2. Access run information view
  3. Verify metadata and statistics displayed

Expected Results:

  • AC1: Run file metadata displayed (filename, date, operator, etc.)
  • AC2: Summary statistics displayed (well counts, pass/fail counts)

Automation Status: Automated

Jira: BT-2640

TC-RUNRPT-008: Edit well information interface​

Verifies: REQ-RUNRPT-006 (AC1, AC2, AC3, AC4)

Method: TM-UI

Priority: High

Preconditions:

  • User with edit permissions on runfile report

Steps:

  1. Initiate well editing without selecting a well
  2. Verify prompt for well selection
  3. Select well A1
  4. Verify edit interface displays A1 data
  5. Verify editable fields available

Expected Results:

  • AC1: Edit interface provided for well data
  • AC2: System prompts for well selection when editing initiated without selection
  • AC3: Selected well's data displayed for editing
  • AC4: Sample name, accession, sample type, sample role, and control label are editable

Automation Status: Automated (Browser)

Jira: BT-1114

TC-RUNRPT-009: Edit well validation​

Verifies: REQ-RUNRPT-006 (AC5, AC6)

Method: TM-UI

Priority: High

Preconditions:

  • User in well edit mode

Test Data:

  • Invalid accession: "ABC@#$"
  • Invalid control label wildcard: "PC*invalid"

Steps:

  1. Enter invalid characters in accession field
  2. Verify validation error
  3. Enter invalid wildcard in control label
  4. Verify validation error

Expected Results:

  • AC5: Accession field validates for allowed characters; invalid input rejected with error indication
  • AC6: Control label validates for wildcard characters; invalid wildcards rejected with error indication

Automation Status: Automated (Browser)

Jira: BT-1114

TC-RUNRPT-010: Manage well results interface​

Verifies: REQ-RUNRPT-007 (AC1, AC2, AC3)

Method: TM-UI

Priority: Critical

Preconditions:

  • Runfile with wells containing errors

Test Data:

  • Well A1: Error type = "Unrecognised"
  • Well A2: Error type = "Control Failed"

Steps:

  1. Open runfile report
  2. Access resolution interface
  3. Select error outcome for well A1
  4. Verify available resolutions match error type
  5. Repeat for well A2

Expected Results:

  • AC1: Resolution interface provided for wells with errors
  • AC2: Resolution interface opens when error outcome selected
  • AC3: Available resolution actions displayed based on error type

Automation Status: Automated (Browser)

Jira: BT-1115

TC-RUNRPT-011: Apply resolution and role priority​

Verifies: REQ-RUNRPT-007 (AC4, AC5, AC6)

Method: TM-UI

Priority: High

Preconditions:

  • User with appropriate resolution permissions
  • Well with error requiring resolution

Steps:

  1. Select well with error
  2. Apply available resolution
  3. Verify error resolved
  4. Test with different user roles to verify role priority affects available resolutions
  5. Test observation-level resolution

Expected Results:

  • AC4: Resolutions can be applied to resolve errors
  • AC5: Role priority considered when determining available resolutions
  • AC6: Observation-level result resolution supported

Automation Status: Automated (Browser)

Jira: BT-2169

TC-RUNRPT-012: Basic LIMS export​

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

Method: TM-HYB

Priority: Critical

Preconditions:

  • Runfile with exportable wells
  • Export folder configured (LIMS_Reports)

Steps:

  1. Open runfile report
  2. Initiate LIMS export
  3. Select export format
  4. Select export location
  5. Confirm export
  6. Verify file created in configured folder

Expected Results:

  • AC1: Export file created for all wells
  • AC2: Export format selectable from configured formats
  • AC3: Export location selectable
  • AC4: Export stored in configured LIMS_Reports folder
  • AC5: Individual wells can be selected for export

Automation Status: Automated

Jira: Pending

TC-RUNRPT-013: LIMS export logic​

Verifies: REQ-RUNRPT-008 (AC6, AC7, AC8, AC9, AC10)

Method: TM-API

Priority: High

Preconditions:

  • Runfile with mixed well outcomes (exportable and non-exportable)

Test Data:

  • Well A1: Positive outcome (exportable)
  • Well A2: Error outcome (may not be exportable)
  • Well A3: Quantitative result
  • Well A4: Qualitative result

Steps:

  1. Generate export via API/job
  2. Verify CT and Quant values consider well outcome
  3. Verify exportable wells conditions applied
  4. Verify LIMS type exclusions honored
  5. Verify Quant/Qual wells not separated
  6. Verify no empty exports created

Expected Results:

  • AC6: Well outcome considered for CT and Quant values in export
  • AC7: Exportable wells conditions applied
  • AC8: LIMS type considered when checking excluded wells
  • AC9: Empty LIMS exports not created for Quantitative/Qualitative wells
  • AC10: Quant/Qual wells not separated in exports

Automation Status: Automated

Jira: Pending

TC-RUNRPT-014: Client-specific export formats​

Verifies: REQ-RUNRPT-008 (AC11, AC12, AC13, AC14, AC15, AC16)

Method: TM-HYB

Priority: Medium

Preconditions:

  • Client configurations for Quest, Viracor, Eurofins, Merck, Nottingham, Sherwood Forest

Steps:

  1. For each client type, configure appropriate export format
  2. Generate export
  3. Verify format matches client-specific requirements

Expected Results:

  • AC11: Quest export formats supported (ABI 7500 with Quest additions, Chantilly LIMS, Operator=Taqman8)
  • AC12: Viracor export formats supported (LIMS Export, Run Result Export, timestamp filename)
  • AC13: Eurofins export format supported (LIMS Export Definition)
  • AC14: Merck export formats supported (LIMS Export Format, Dynamic Header Rows)
  • AC15: Nottingham export format supported (Export definition, Viral Load column)
  • AC16: Sherwood Forest export format supported (Export definition)

Automation Status: Planned

Jira: Pending

Deviation: TM-HYB used due to client-specific configuration requirements. Some verification may require manual inspection of export file contents.

TC-RUNRPT-015: LIMS export error handling​

Verifies: REQ-RUNRPT-008 (Error Handling)

Method: TM-HYB

Priority: High

Preconditions:

  • Runfile with no exportable wells
  • Export location that is inaccessible

Steps:

  1. Attempt export with no exportable wells
  2. Verify error indication
  3. Attempt export to unavailable location
  4. Verify error indication

Expected Results:

  • No exportable wells: Export prevented with indication that no wells meet export criteria
  • Export location unavailable: Error displayed indicating destination not accessible

Automation Status: Planned

Jira: Pending

TC-RUNRPT-016: Well table sorting​

Verifies: REQ-RUNRPT-009 (AC1, AC2, AC3, AC4)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile with multiple wells across mixes

Steps:

  1. Open runfile report
  2. Observe default sort order
  3. Click Mix column header
  4. Verify sort by Mix ascending
  5. Click Mix column header again
  6. Verify sort toggles to descending
  7. Click Sample Name column
  8. Verify only one column sorted at a time

Expected Results:

  • AC1: Sorting supported for Mix, Well, Name, Sample Type, Sample Role columns
  • AC2: Default sort is by Well ascending (A1, A2, A3...)
  • AC3: Sort direction toggles when same column selected again
  • AC4: Only one column sorted at a time

Automation Status: Automated

Jira: BT-1066

TC-RUNRPT-017: Well table filtering categories​

Verifies: REQ-RUNRPT-010 (AC1, AC2, AC3)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile with diverse well data (multiple mixes, sample types, outcomes)

Steps:

  1. Open runfile report
  2. Observe available filter categories
  3. Select multiple values in Mix filter
  4. Verify wells filtered
  5. Add Sample Type filter
  6. Verify combined filter applied

Expected Results:

  • AC1: Filters available for Mixes, Names, Sample Types, Sample Roles, Targets, Classes, Outcomes, Actions
  • AC2: Multiple values can be selected within a filter
  • AC3: Multiple filters can be combined

Automation Status: Automated

Jira: BT-1070, BT-2723, BT-2724

TC-RUNRPT-018: Well table filter behavior​

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

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with some filter categories having no matching wells

Test Data:

  • Role Alias filter with wildcard: "PC*"

Steps:

  1. Test Role Alias filter with wildcard
  2. Verify wildcard filtering works
  3. Toggle filter visibility
  4. Verify filters can be shown/hidden
  5. Observe filter with no available options
  6. Verify visual indication for empty filter

Expected Results:

  • AC4: Wildcard characters supported in Role Alias filter
  • AC5: Filter visibility can be toggled
  • AC6: Visual indication when filter has no available options

Automation Status: Automated

Jira: BT-1079, BT-1082, BT-1085

TC-RUNRPT-019: Amplification curve display​

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

Method: TM-UI

Priority: High

Preconditions:

  • Runfile with wells containing amplification data

Steps:

  1. Open runfile report
  2. Select result data for a well
  3. Verify amplification curve displayed
  4. Verify curve corresponds to selected well
  5. Observe legend sort order

Expected Results:

  • AC1: Amplification curves displayed when result data selected
  • AC2: Curve displayed for selected well
  • AC3: Legend items in consistent sort order

Automation Status: Automated (Browser)

Jira: BT-1063

TC-RUNRPT-020: Amplification curve interaction​

Verifies: REQ-RUNRPT-011 (AC4, AC5, AC6)

Method: TM-UI

Priority: Medium

Preconditions:

  • Multiple wells with amplification data

Steps:

  1. Select multiple wells
  2. Verify curves overlaid for comparison
  3. Test zoom and pan controls
  4. Select single well only
  5. Verify alignment controls disabled for single curve

Expected Results:

  • AC4: Multiple curves can be overlaid for comparison
  • AC5: Zoom and pan controls available
  • AC6: Alignment controls disabled when only single curve displayed

Automation Status: Automated (Browser)

Jira: BT-1063

TC-RUNRPT-021: Well action menu​

Verifies: REQ-RUNRPT-012 (AC1, AC2, AC3, AC4, AC5)

Method: TM-UI

Priority: High

Preconditions:

  • User on runfile report with wells

Steps:

  1. Open action menu for well A1
  2. Verify available actions
  3. Use flag action to flag the well
  4. Use unflag action to unflag
  5. Add a comment
  6. View/edit the comment
  7. Use export to LIMS action

Expected Results:

  • AC1: Action menu available for each well
  • AC2: Actions include flag/unflag, comment, export to LIMS
  • AC3: Actions applied to selected well
  • AC4: Comments can be added, viewed, and edited
  • AC5: Flag state toggles between flagged and unflagged

Automation Status: Automated (Browser)

Jira: BT-1858

TC-RUNRPT-022: Well selection​

Verifies: REQ-RUNRPT-013 (AC1, AC2, AC3, AC4, AC5)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile with multiple wells

Steps:

  1. Click well row A1
  2. Verify A1 visually indicated as selected
  3. Use selection mechanism for multiple wells
  4. Verify multiple wells selected
  5. Initiate Edit Wells operation
  6. Verify selection used for edit
  7. Repeat for Manage Results and Export operations

Expected Results:

  • AC1: Well selected when row clicked
  • AC2: Selected wells visually indicated
  • AC3: Selection mechanism available for each well
  • AC4: Multiple wells can be selected simultaneously
  • AC5: Selection used for Edit Wells, Manage Results, and Export operations

Automation Status: Automated

Jira: BT-1114

TC-RUNRPT-023: Run file notifications​

Verifies: REQ-RUNRPT-014 (AC1, AC2)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with wells in various notification states

Steps:

  1. Open runfile report
  2. Observe notification indicators in header
  3. Select a notification
  4. Verify table filtered to related wells

Expected Results:

  • AC1: Notification indicators displayed in run header
  • AC2: Selecting notification filters table to related wells

Automation Status: Automated

Jira: Pending

TC-RUNRPT-024: Composite assay outcomes​

Verifies: REQ-RUNRPT-015 (AC1, AC2, AC3)

Method: TM-HYB

Priority: Medium

Preconditions:

  • Client with composite assay configuration
  • Runfile with composite assay results

Test Data:

  • Composite outcome matrix configured with 2 columns
  • Well with Target1=Positive, Target2=Negative

Steps:

  1. Configure composite outcome matrix (API/admin)
  2. Process runfile with composite assay
  3. Verify outcome determined based on combination
  4. Verify column count and titles match configuration
  5. Verify outcome text matches configured value

Expected Results:

  • AC1: Outcomes determined based on Negative/Positive result combinations
  • AC2: Column count and titles configurable
  • AC3: Outcome text configurable per combination

Automation Status: Planned

Jira: CST-155

TC-RUNRPT-025: Accession history display conditions​

Verifies: REQ-RUNRPT-016 (AC1, AC2, AC3, AC4)

Method: TM-UI

Priority: Medium

Preconditions:

  • Accession history enabled in client configuration
  • Well with repeat accession having prior results

Test Data:

  • Sample "12345" with prior results dated before current extraction date

Steps:

  1. Open runfile with repeat accession
  2. Verify history available for repeat accession wells
  3. Verify history shows only entries earlier than current extraction
  4. Verify history shows only same sample name entries

Expected Results:

  • AC1: Accession history displayed when enabled in client configuration
  • AC2: History displayed only for wells with repeat accessions
  • AC3: Only history entries earlier than current sample's extraction date shown
  • AC4: Only history entries for same sample name shown

Automation Status: Automated

Jira: BT-1140

TC-RUNRPT-026: Accession history content​

Verifies: REQ-RUNRPT-016 (AC5, AC6)

Method: TM-UI

Priority: Medium

Preconditions:

  • Same as TC-RUNRPT-025

Steps:

  1. View accession history for well
  2. Verify displayed fields
  3. Expand history display
  4. Collapse history display

Expected Results:

  • AC5: History displays date, runfile name, mix, and outcome
  • AC6: History can be expanded and collapsed

Automation Status: Automated

Jira: BT-1140

TC-RUNRPT-027: Multi-site operation​

Verifies: REQ-RUNRPT-017 (AC1, AC2, AC3)

Method: TM-UI

Priority: Medium

Preconditions:

  • Multi-site feature enabled
  • User with manager permissions
  • User with junior permissions

Steps:

  1. Log in as manager
  2. Open runfile report
  3. Verify site filtering available
  4. Verify site origin displayed
  5. Log in as junior user
  6. Verify site features hidden

Expected Results:

  • AC1: Site filtering provided for users with manager permissions
  • AC2: Run file site origin displayed for users with manager permissions
  • AC3: Site-related features hidden for users without manager permissions

Automation Status: Automated

Jira: Pending

TC-RUNRPT-028: Westgard QC widget​

Verifies: REQ-RUNRPT-018 (AC1, AC2, AC3, AC4)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile with Westgard data for multiple controls

Steps:

  1. Open Westgard widget
  2. Verify analysis results displayed for each control
  3. Verify control charts show rule violations
  4. Navigate between different controls
  5. Observe error and warning count separation

Expected Results:

  • AC1: Westgard analysis results displayed for each control
  • AC2: Control charts displayed with rule violations indicated
  • AC3: Navigation between different controls available
  • AC4: Error and warning counts separated in status indicator

Automation Status: Automated (Browser)

Jira: Pending

TC-RUNRPT-029: Assay Summary widget​

Verifies: REQ-RUNRPT-019 (AC1, AC2, AC3)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with multiple targets and outcomes

Steps:

  1. Open Assay Summary widget
  2. Verify results grouped by target
  3. Verify counts for each outcome type
  4. Add well export note
  5. Verify note appears in run note section

Expected Results:

  • AC1: Results grouped by target
  • AC2: Counts displayed for each outcome type
  • AC3: Well export notes can be added to run note section

Automation Status: Automated

Jira: Pending

TC-RUNRPT-030: Outcome Summary widget​

Verifies: REQ-RUNRPT-020 (AC1, AC2)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with various outcomes

Steps:

  1. Open Outcome Summary widget
  2. Verify outcome distribution displayed
  3. Verify counts for each outcome type

Expected Results:

  • AC1: Distribution of outcomes displayed
  • AC2: Counts provided for each outcome type

Automation Status: Automated

Jira: Pending

TC-RUNRPT-031: Plate Map widget​

Verifies: REQ-RUNRPT-021 (AC1, AC2, AC3, AC4)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with wells in various states

Steps:

  1. Open Plate Map widget
  2. Verify plate layout displayed with well positions
  3. Verify well status indicated visually
  4. Verify error type information associated with wells
  5. Select well in plate map
  6. Verify selection synchronized with main table

Expected Results:

  • AC1: Plate layout displayed with well positions
  • AC2: Well status indicated through visual differentiation
  • AC3: Error type information associated with wells
  • AC4: Well selection synchronized between plate map and main table

Automation Status: Automated

Jira: Pending

TC-RUNRPT-032: Quantification widget​

Verifies: REQ-RUNRPT-022 (AC1, AC2, AC3, AC4, AC5, AC6)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with quantification data

Steps:

  1. Open Quantification widget
  2. Verify quantification results displayed
  3. Verify standard curve displayed
  4. Verify efficiency metrics displayed
  5. Verify intercept value displayed
  6. Verify gradient value displayed to 4 decimal places

Expected Results:

  • AC1: Quantification results displayed
  • AC2: Standard curve displayed
  • AC3: Efficiency metrics displayed
  • AC4: Intercept value displayed
  • AC5: Gradient value displayed with appropriate precision
  • AC6: Gradient values shown to 4 decimal places

Automation Status: Automated (Browser)

Jira: Pending

TC-RUNRPT-033: Bulk edit wells​

Verifies: REQ-RUNRPT-023 (AC1, AC2, AC3)

Method: TM-UI

Priority: High

Preconditions:

  • Multiple wells selected

Test Data:

  • Wells A1, A2, A3 selected
  • New sample type: "Standard"

Steps:

  1. Select multiple wells
  2. Initiate bulk edit
  3. Make changes to editable field
  4. Apply changes
  5. Verify changes applied to all selected wells
  6. Verify validation applies to all wells

Expected Results:

  • AC1: Changes applied to all selected wells in bulk operation
  • AC2: Same editable fields available as single well edit
  • AC3: Validation applied to all wells in bulk operation

Automation Status: Automated

Jira: Pending

TC-RUNRPT-034: Bulk manage results​

Verifies: REQ-RUNRPT-024 (AC1, AC2, AC3)

Method: TM-UI

Priority: High

Preconditions:

  • Multiple wells with errors selected

Steps:

  1. Select multiple wells with errors
  2. Initiate bulk result management
  3. Verify bulk management interface available
  4. Apply resolution
  5. Verify resolution applied to all selected wells

Expected Results:

  • AC1: Bulk result management capability provided
  • AC2: Resolution actions can be applied to multiple selected wells
  • AC3: All selected wells considered in bulk operation

Automation Status: Automated

Jira: Pending

TC-RUNRPT-035: System flags display​

Verifies: REQ-RUNRPT-025 (AC1, AC2, AC3)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with wells meeting flag criteria

Test Data:

  • Well with CLS/CT discrepancy
  • Well meeting AMB classification rule criteria

Steps:

  1. Open runfile with discrepancy well
  2. Verify CLS/CT discrepancy flag displayed
  3. Verify flag calculation applied automatically
  4. Verify classification flags based on AMB rules

Expected Results:

  • AC1: CLS/CT discrepancy flags displayed when criteria met
  • AC2: Flag calculation logic applied automatically
  • AC3: Classification flags applied based on AMB rules

Automation Status: Automated

Jira: Pending

TC-RUNRPT-036: Unsaved changes warning​

Verifies: REQ-RUNRPT-026 (AC1, AC2)

Method: TM-UI

Priority: High

Preconditions:

  • User has made unsaved changes on runfile report

Steps:

  1. Make changes to well data
  2. Attempt to navigate away (without saving)
  3. Verify warning displayed
  4. Cancel navigation
  5. Verify user remains on page
  6. Confirm navigation
  7. Verify navigation proceeds

Expected Results:

  • AC1: Warning triggered when unsaved changes exist and user attempts to navigate away
  • AC2: User can confirm or cancel the navigation

Automation Status: Automated

Jira: Pending

TC-RUNRPT-037: Widget state persistence​

Verifies: REQ-RUNRPT-027 (AC1, AC2, AC3, AC4)

Method: TM-UI

Priority: Medium

Preconditions:

  • User session with widget interaction

Steps:

  1. Open several widgets
  2. Close some widgets
  3. Resize/reposition open widgets
  4. Change tab layout
  5. Note default pinned widget configuration
  6. Close browser and re-open runfile report
  7. Verify widget states restored

Expected Results:

  • AC1: Widget open/closed state preserved
  • AC2: Widget positions and sizes preserved
  • AC3: Tab layout configuration preserved
  • AC4: Default pinned widget configuration respected

Automation Status: Automated

Jira: Pending

TC-RUNRPT-038: Accession and label validation​

Verifies: REQ-RUNRPT-028 (AC1, AC2, AC3, AC4)

Method: TM-HYB

Priority: High

Preconditions:

  • User in well edit mode

Test Data:

  • Invalid accession: "ABC@#$%"
  • Well label containing "null"

Steps:

  1. Enter invalid characters in accession field
  2. Verify validation error with indication of invalid characters
  3. Attempt accession validation during run import (API)
  4. Verify prohibited well label "null" rejected
  5. Verify error indication for label validation

Expected Results:

  • AC1: Accession field validates for allowed characters only
  • AC2: Accession characters validated during run import
  • AC3: Well label validates for prohibited values
  • AC4: Well label values containing "null" rejected

Automation Status: Automated (Browser)

Jira: Pending

TC-RUNRPT-039: Control label wildcard validation​

Verifies: REQ-RUNRPT-028 (AC5, AC6)

Method: TM-UI

Priority: Medium

Preconditions:

  • User editing control well

Test Data:

  • Invalid wildcard pattern in control label

Steps:

  1. Enter invalid wildcard in control label
  2. Verify validation error
  3. Verify error indication for invalid wildcard

Expected Results:

  • AC5: Control label wildcards validated
  • AC6: Invalid control label wildcard rejected with error indication

Automation Status: Automated (Browser)

Jira: Pending

TC-RUNRPT-040: Edit wells mode prompt​

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

Method: TM-UI

Priority: High

Preconditions:

  • User logged in with edit permissions
  • Runfile with seeded config and run data

Steps:

  1. Open runfile report
  2. Click Edit Wells button to enter edit mode
  3. Verify "Select a well" prompt displayed in edit widget
  4. Verify well table remains visible alongside edit widget

Expected Results:

  • AC1: Edit interface provided for well data
  • AC2: System prompts for well selection when editing initiated without selection

Automation Status: Automated (Browser)

Jira: BT-1349

TC-RUNRPT-041: Well selection in edit mode​

Verifies: REQ-RUNRPT-006 (AC3)

Method: TM-UI

Priority: High

Preconditions:

  • User in Edit Wells mode on runfile report

Steps:

  1. Enter Edit Wells mode
  2. Click a well row in the table
  3. Verify well row shows selected state
  4. Verify edit widget updates with selected well details

Expected Results:

  • AC3: Selected well's data displayed for editing

Automation Status: Automated (Browser)

Jira: BT-1349

TC-RUNRPT-042: Exit edit mode without changes​

Verifies: REQ-RUNRPT-006 (AC1)

Method: TM-UI

Priority: Medium

Preconditions:

  • User in Edit Wells mode with no unsaved changes

Steps:

  1. Enter Edit Wells mode
  2. Verify "Select a well" prompt
  3. Click Edit Wells button again to exit
  4. Verify run report returns to normal state without unsaved changes dialog

Expected Results:

  • AC1: Edit interface closes cleanly when no changes have been made

Automation Status: Automated (Browser)

Jira: BT-1349

TC-RUNRPT-043: Error notification count display​

Verifies: REQ-RUNRPT-014 (AC1)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile with seeded config and run data producing error wells

Steps:

  1. Upload config and run file via API
  2. Open runfile report
  3. Verify error notification icon (dark-red) is present with a count
  4. Verify associated control error icon (light-red) is present

Expected Results:

  • AC1: Notification indicators displayed in run header with correct error counts

Automation Status: Automated (Browser)

Jira: BT-4921

TC-RUNRPT-044: Warning notification count display​

Verifies: REQ-RUNRPT-014 (AC1)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with seeded config and run data producing warnings

Steps:

  1. Upload config and run file via API
  2. Open runfile report
  3. Verify warning icon (yellow) is present
  4. Verify exportable icon (green) is present
  5. Verify error icon (dark-red) is present to confirm differentiation

Expected Results:

  • AC1: Notification indicators for warnings displayed separately from error counts, confirming error type differentiation

Automation Status: Automated (Browser)

Jira: BT-4921

TC-RUNRPT-045: Error notification filter interaction​

Verifies: REQ-RUNRPT-014 (AC2)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile with seeded config and run data producing error wells

Steps:

  1. Upload config and run file via API
  2. Open runfile report
  3. Verify well table is present
  4. Click the error count indicator to filter wells
  5. Verify well table updates to show filtered results

Expected Results:

  • AC2: Selecting notification filters table to related wells

Automation Status: Automated (Browser)

Jira: BT-4921

TC-RUNRPT-046: Outcome column message display​

Verifies: REQ-RUNRPT-001 (AC1)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile with seeded config and run data producing wells with errors and outcomes

Steps:

  1. Upload config and run file via API
  2. Open runfile report
  3. Verify Outcome column header is present
  4. Verify outcome data attribute exists on well rows
  5. Verify outcome messages render in outcome column cells

Expected Results:

  • AC1: Well table displays outcome column with outcome messages for wells with errors

Automation Status: Automated (Browser)

Jira: BT-5510

TC-RUNRPT-047: Outcome error type icons​

Verifies: REQ-RUNRPT-001 (AC4)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with seeded config and run data producing wells with error outcomes

Steps:

  1. Upload config and run file via API
  2. Open runfile report
  3. Verify outcome column data elements are present
  4. Verify wells table contains wells with error type icon indicators

Expected Results:

  • AC4: Outcome messages display with associated error type icon indicators (error/warning/info)

Automation Status: Automated (Browser)

Jira: BT-5510

TC-RUNRPT-048: Unrecognised wells notification indicator​

Verifies: REQ-RUNRPT-014 (AC1)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with seeded config and run data producing label errors

Steps:

  1. Upload config and run file via API
  2. Open runfile report
  3. Verify unrecognised wells icon (gray question-circle) is present
  4. Verify count element is present alongside the icon

Expected Results:

  • AC1: Unrecognised wells notification indicator displays label error count in run header

Automation Status: Automated (Browser)

Jira: BT-2534

TC-RUNRPT-049: All notification categories visible​

Verifies: REQ-RUNRPT-014 (AC1)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile with seeded config and run data producing all notification types

Steps:

  1. Upload config and run file via API
  2. Open runfile report
  3. Verify all 6 notification icon types are present: unrecognised (gray), errors (dark-red), warnings (yellow), exportable (green), comments (light-gray), associated control errors (light-red)

Expected Results:

  • AC1: All notification category indicators are visible in the run report header

Automation Status: Automated (Browser)

Jira: BT-2534

TC-RUNRPT-050: Run Calibration Chart tab access @V3_1_0​

Verifies: REQ-RUNRPT-029 (AC1, AC2, AC3, AC4)

Method: TM-UI

Priority: High

Preconditions:

  • User logged in with at least Junior User role
  • Runfile exists with calibrated targets

Test Data:

  • Runfile associated with a mix that has calibrated targets

Steps:

  1. Navigate to the runfile report
  2. Observe the widget tab bar
  3. Verify "Run Calibration Chart" appears as the last tab (after Quantification)
  4. Click the "Run Calibration Chart" tab
  5. Verify the widget panel opens
  6. Open a different widget (e.g., Assay Summary), then click "Run Calibration Chart" again

Expected Results:

  • AC1: "Run Calibration Chart" is displayed as the last tab in the Run View tab bar
  • AC2: Clicking the tab opens the Run Calibration Chart widget panel
  • AC3: Opening the Run Calibration Chart tab closes any other open widget panel
  • AC4: The tab is always visible regardless of feature flag settings

Automation Status: Pending

Jira: BT-2456

TC-RUNRPT-051: Target selector and warning display @V3_1_0​

Verifies: REQ-RUNRPT-030 (AC1, AC2, AC3)

Method: TM-UI

Priority: High

Preconditions:

  • User logged in with at least Junior User role
  • Runfile exists with calibrated targets

Test Data:

  • Runfile with multiple calibrated targets

Steps:

  1. Open the Run Calibration Chart widget
  2. Verify the target dropdown is present and lists calibration targets for the current run
  3. Before selecting a target, verify a warning message is displayed
  4. Select a target from the dropdown
  5. Verify the warning message is dismissed and the chart loads

Expected Results:

  • AC1: Target dropdown displays all calibration targets available for the current run
  • AC2: Target options are populated from the run calibrations targets API endpoint
  • AC3: A warning message is displayed when no target is selected

Automation Status: Pending

Jira: BT-2456

TC-RUNRPT-052: Calibration data fetch and display @V3_1_0​

Verifies: REQ-RUNRPT-031 (AC1, AC2, AC3)

Method: TM-API

Priority: High

Preconditions:

  • Runfile exists with calibrated targets
  • Active calibration exists for the target

Test Data:

  • Runfile with mix/target that has an active calibration and historical calibrated runs

Steps:

  1. Open the Run Calibration Chart widget
  2. Select a target from the dropdown
  3. Verify calibration data is fetched via the run-calibration-data API
  4. Change the selected target to a different one
  5. Verify data is re-fetched for the new target

Expected Results:

  • AC1: Calibration data is fetched via the run-calibration-data API when a target is selected
  • AC2: Response includes calibrated runs, current run data, target details, and active calibration status
  • AC3: Data is automatically re-fetched when the selected target changes

Automation Status: Pending

Jira: BT-2456

TC-RUNRPT-053: Calibration data feedback states @V3_1_0​

Verifies: REQ-RUNRPT-031 (AC4, AC5)

Method: TM-UI

Priority: Medium

Preconditions:

  • Runfile exists with at least one calibrated target and one target without calibration data

Test Data:

  • Target with calibration data (loading state observable)
  • Target with no calibration data

Steps:

  1. Open the Run Calibration Chart widget
  2. Select a target with calibration data and observe the loading state
  3. Select a target without any calibration data
  4. Verify the informational message is displayed

Expected Results:

  • AC4: A loading indicator is displayed while calibration data is being fetched
  • AC5: An informational message is displayed when no calibration data exists for the selected target

Automation Status: Pending

Jira: BT-2456

TC-RUNRPT-054: Current run highlighting on calibration chart @V3_1_0​

Verifies: REQ-RUNRPT-032 (AC1, AC2)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile exists with calibrated targets
  • Active calibration exists with observations from multiple runs including the current run

Test Data:

  • Runfile with calibrated target where the current run is part of the calibration dataset

Steps:

  1. Open the Run Calibration Chart widget
  2. Select a target with calibration data
  3. Verify the chart renders with the current run's observations visually highlighted
  4. Verify other calibrated runs' observations are displayed differently

Expected Results:

  • AC1: Current run observations are pre-highlighted when the chart is rendered
  • AC2: Current run observations are visually distinguished from other calibrated runs

Automation Status: Pending

Jira: BT-2456

TC-RUNRPT-055: Calibration chart 2D/3D display @V3_1_0​

Verifies: REQ-RUNRPT-033 (AC1, AC2, AC3)

Method: TM-UI

Priority: High

Preconditions:

  • Runfile exists with calibrated targets
  • Active calibration exists with observations and defined min/max DF boundaries

Test Data:

  • Runfile with calibrated target having observations and positivity range set

Steps:

  1. Open the Run Calibration Chart widget and select a target
  2. Verify the default chart renders as a 2D scatter plot
  3. Verify min/max DF positivity range lines are displayed on the 2D chart
  4. Toggle the chart to 3D mode
  5. Verify the chart switches to a 3D scatter plot visualization
  6. Toggle back to 2D mode and verify the chart returns to 2D

Expected Results:

  • AC1: A 2D scatter plot is rendered by default showing calibration observations
  • AC2: A toggle switches between 2D and 3D scatter plot visualization
  • AC3: Positivity range lines (min/max DF) are displayed on the 2D chart

Automation Status: Pending

Jira: BT-2456

TC-RUNRPT-056: Chart settings axis configuration @V3_1_0​

Verifies: REQ-RUNRPT-034 (AC1, AC2, AC3)

Method: TM-UI

Priority: Medium

Preconditions:

  • Run Calibration Chart is displayed with calibration data loaded

Test Data:

  • Runfile with calibrated target rendering observations on chart

Steps:

  1. Open the chart settings panel
  2. Verify X-axis and Y-axis representation selectors are present
  3. Change the X-axis to a different representation (e.g., PcrAi CT)
  4. Verify the selected option is unavailable in the Y-axis selector
  5. Switch the chart to 3D mode
  6. Verify a Z-axis representation selector appears
  7. Verify axis uniqueness constraint applies across all three axes

Expected Results:

  • AC1: X-axis and Y-axis representation selectors are available with appropriate options
  • AC2: A Z-axis representation selector is displayed when 3D mode is active
  • AC3: Each representation option can only be assigned to one axis at a time

Automation Status: Pending

Jira: BT-2456

TC-RUNRPT-057: Chart settings interactive controls @V3_1_0​

Verifies: REQ-RUNRPT-034 (AC4, AC5, AC6)

Method: TM-UI

Priority: Medium

Preconditions:

  • Run Calibration Chart is displayed with calibration data from multiple runs

Test Data:

  • Calibration data involving multiple calibrated runs

Steps:

  1. Open the chart settings panel
  2. Use the run highlighter to highlight a specific run
  3. Verify the highlighted run is visually emphasized on the chart
  4. Toggle the CLS discrepancy control
  5. Verify the chart legend is displayed identifying runs and classification data

Expected Results:

  • AC4: Run highlighter highlights specific runs on the chart
  • AC5: CLS discrepancy toggle is available and functional
  • AC6: Chart legend is displayed for run and classification identification

Automation Status: Pending

Jira: BT-2456

TC-RUNRPT-058: Draggable DF lines in run view @V3_1_0​

Verifies: REQ-RUNRPT-035 (AC1, AC2, AC3, AC4)

Method: TM-UI

Priority: High

Preconditions:

  • Run Calibration Chart is displayed in 2D mode with calibration data and positivity range set

Test Data:

  • Runfile with calibrated target having min/max DF boundaries

Steps:

  1. Verify two vertical draggable lines (min DF and max DF) are displayed on the 2D chart
  2. Drag one of the DF lines to a new position
  3. Verify save/discard controls appear
  4. Click "Persist" and verify the updated DF values are saved
  5. Drag a DF line again, then click "Discard" and verify the line reverts
  6. Switch to 3D mode
  7. Verify a message indicates DF line adjustment requires 2D mode and lines are not draggable

Expected Results:

  • AC1: Two vertical draggable lines representing min DF and max DF are displayed on the 2D chart
  • AC2: Save/discard controls appear when DF values are changed by dragging
  • AC3: Users can persist or discard positivity range changes
  • AC4: In 3D mode, a message indicates DF adjustment requires 2D mode and dragging is disabled

Automation Status: Pending

Jira: BT-2456

TC-RUNRPT-059: Pin/unpin calibration chart widget @V3_1_0​

Verifies: REQ-RUNRPT-036 (AC1, AC2, AC3)

Method: TM-UI

Priority: Medium

Preconditions:

  • Run Calibration Chart widget is open

Test Data:

  • Any runfile with calibrated targets

Steps:

  1. Open the Run Calibration Chart widget
  2. Verify the pin/unpin toggle control is present
  3. Click pin to pin the widget
  4. Verify the widget displays inline with run view content
  5. Click unpin to unpin the widget
  6. Verify the widget displays as an overlay above run view content

Expected Results:

  • AC1: A pin/unpin toggle control is available on the widget panel
  • AC2: When pinned, the widget panel displays inline with run view content
  • AC3: When unpinned, the widget panel displays as an overlay above run view content

Automation Status: Pending

Jira: BT-2456

TC-RUNRPT-060: Help data for run calibration chart @V3_1_0​

Verifies: REQ-RUNRPT-037 (AC1, AC2)

Method: TM-UI

Priority: Low

Preconditions:

  • Run Calibration Chart widget is open

Test Data:

  • System with help_data feature flag togglable

Steps:

  1. Enable the help feature flag
  2. Open the Run Calibration Chart widget
  3. Activate help mode
  4. Verify contextual help data is displayed within the calibration chart widget
  5. Disable the help feature flag
  6. Open the Run Calibration Chart widget again
  7. Verify help data is not available

Expected Results:

  • AC1: Contextual help data is displayed when help mode is active
  • AC2: Help data availability is gated on the help feature flag

Automation Status: Pending

Jira: BT-2456

Gap Analysis​

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

Coverage by AC Type​

AC CategoryCountCoveredNotes
Display/Rendering3535Verified via TM-UI
Interaction/Filtering2828Verified via TM-UI
Export/Print2121Verified via TM-HYB
Validation1212Verified via TM-UI/TM-HYB
Configuration1010Verified via TM-HYB
Multi-site/Permissions66Verified via TM-UI
State Persistence77Verified via TM-UI
Calibration Chart (v3.1.0)3232Verified via TM-UI, TM-API

Traceability to Existing Tests​

Test CaseJira TestAutomation
TC-RUNRPT-001, TC-RUNRPT-002BT-1063, BT-2726, BT-1139Selenium
TC-RUNRPT-003BT-1063Selenium
TC-RUNRPT-004BT-1105, BT-1928, BT-2722Selenium
TC-RUNRPT-005, TC-RUNRPT-006BT-1108, BT-1109, BT-1110, BT-1111, BT-1112, BT-2474Browser (Behat/Mink)
TC-RUNRPT-007BT-2640Selenium
TC-RUNRPT-008, TC-RUNRPT-009BT-1114Browser (Behat/Mink)
TC-RUNRPT-010, TC-RUNRPT-011BT-1115, BT-2169Browser (Behat/Mink)
TC-RUNRPT-016BT-1066Selenium
TC-RUNRPT-017, TC-RUNRPT-018BT-1070, BT-2723, BT-2724, BT-1079, BT-1082, BT-1085Selenium
TC-RUNRPT-019, TC-RUNRPT-020BT-1063Browser (Behat/Mink)
TC-RUNRPT-021BT-1858Browser (Behat/Mink)
TC-RUNRPT-022BT-1114Selenium
TC-RUNRPT-025, TC-RUNRPT-026BT-1140Selenium
TC-RUNRPT-040, TC-RUNRPT-041, TC-RUNRPT-042BT-1349Browser (Behat/Mink)
TC-RUNRPT-043, TC-RUNRPT-044, TC-RUNRPT-045BT-4921Browser (Behat/Mink)
TC-RUNRPT-046, TC-RUNRPT-047BT-5510Browser (Behat/Mink)
TC-RUNRPT-048, TC-RUNRPT-049BT-2534Browser (Behat/Mink)
TC-RUNRPT-028PendingBrowser (Behat/Mink)
TC-RUNRPT-032PendingBrowser (Behat/Mink)
TC-RUNRPT-038, TC-RUNRPT-039PendingBrowser (Behat/Mink)
TC-RUNRPT-050PendingBrowser (Behat/Mink) @V3_1_0
TC-RUNRPT-051PendingBrowser (Behat/Mink) @V3_1_0
TC-RUNRPT-052, TC-RUNRPT-053PendingAPI (Behat) + Browser @V3_1_0
TC-RUNRPT-054PendingBrowser (Behat/Mink) @V3_1_0
TC-RUNRPT-055PendingBrowser (Behat/Mink) @V3_1_0
TC-RUNRPT-056, TC-RUNRPT-057PendingBrowser (Behat/Mink) @V3_1_0
TC-RUNRPT-058PendingBrowser (Behat/Mink) @V3_1_0
TC-RUNRPT-059PendingBrowser (Behat/Mink) @V3_1_0
TC-RUNRPT-060PendingBrowser (Behat/Mink) @V3_1_0

Notes​

  • RUNRPT is the largest UI domain with 37 requirements and 151 acceptance criteria
  • Many widgets (Westgard, Assay Summary, Outcome Summary, Plate Map, Quantification) have pending Jira references
  • LIMS export tests (TC-RUNRPT-012 through TC-RUNRPT-015) require backend job verification
  • Client-specific export formats should be tested per-client during deployment validation
  • Multi-site tests require multi-site feature to be enabled in system configuration
  • Widget state persistence tests require session management verification across browser sessions
  • Run Calibration Chart tests (TC-RUNRPT-050 through TC-RUNRPT-060) are tagged @V3_1_0 and require active calibration data (see Calibration SRS for lifecycle prerequisites). These test the Run View chart widget, not the Config Mode calibration page (tested in std-calibration.md)