Skip to main content

O & M--Service Order History (AX03US02)

Service Order History - Complete Test Cases (AX03US02)

All 15 Acceptance Criteria with Complete Sections

Test Case 01: Four KPI Cards Display and Calculation

Test Case Metadata

  • Test Case ID: AX03US02_AC_001
  • Title: Verify Four KPI Cards Display with Correct Historical Calculations
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags

Tags: Historical-KPIs, Dashboard-Calculations, 12Month-Default, MOD-ServiceOrderHistory, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-Low, Business-Critical, Revenue-Impact-High

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Performance-Analysis
  • Compliance Required: Yes
  • SLA Related: Yes

Quality Metrics

  • Risk Level: Low
  • Complexity Level: Medium
  • Expected Execution Time: 4 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Medium
  • Failure Impact: Critical

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Historical-Data-Service, KPI-Calculation-Engine
  • Code Module Mapped: AX
  • Requirement Coverage: AC #1 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: Product
  • Report Categories: Historical-Analytics, KPI-Dashboard
  • Trend Tracking: Yes
  • Executive Visibility: Yes
  • Customer Impact Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Historical Data Service, Completed Service Orders Database
  • Performance Baseline: KPI calculations under 2 seconds
  • Data Requirements: Completed service orders spanning 12+ months

Prerequisites

  • Setup Requirements: Historical service orders database populated with completed orders
  • User Roles Permissions: O&M Manager with history view access
  • Test Data:
    • 186 completed service orders over last 12 months
    • Orders with total costs and labor hours recorded
    • Mix of Preventive and Corrective maintenance types
  • Prior Test Cases: Authentication and dashboard access successful

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to O&M —> service orders→ History

Service Order History dashboard loads showing four KPI cards

N/A

Verify dashboard structure

2

Verify "Total Completed SOs" KPI

Shows COUNT of completed orders in last 12 months

Expected: 186

Default 12-month timeframe

3

Verify "Average Cost Per SO" KPI

Shows AVG(TotalCost) formatted as currency

Expected: $1,275.32

Currency formatting validation

4

Verify "PM vs CM Ratio" KPI

Shows percentage ratio: PM% / CM% format

Expected: 72% / 28%

Ratio calculation and format

5

Verify "Total Labor Hours" KPI

Shows SUM(LaborHours) with average subtitle

Expected: 924 hours, Avg 4.97 hrs per SO

Labor hours aggregation

6

Check KPI time period indication

All KPIs show "Last 12 months" or similar timeframe indicator

Last 12 months default

Time period clarity

7

Verify KPI refresh on page load

Fresh calculation on each page access

Current data

Real-time calculation

Verification Points

  • Primary Verification: All four KPI cards display with mathematically correct values for 12-month period
  • Secondary Verifications: Currency formatting correct, Time period indicators clear
  • Negative Verification: Only completed orders included, No draft or cancelled orders counted



Test Case 02: Custom Date Range Filtering

Test Case Metadata

  • Test Case ID: AX03US02_AC_002
  • Title: Verify Dashboard Filtering by Custom Date Range
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags

Tags: Date-Range-Filter, Dashboard-Filter, KPI-Recalculation, MOD-ServiceOrderHistory, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-Medium, Business-Critical

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Performance-Analysis
  • Compliance Required: Yes
  • SLA Related: No

Quality Metrics

  • Risk Level: Medium
  • Complexity Level: High
  • Expected Execution Time: 5 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Medium
  • Failure Impact: Critical

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Filter-Service, Date-Range-Picker, KPI-Recalculation
  • Code Module Mapped: AX
  • Requirement Coverage: AC #2 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: Engineering
  • Report Categories: Filter-Functionality, Date-Operations
  • Trend Tracking: Yes
  • Executive Visibility: Yes
  • Customer Impact Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Date Range Service, Filter Framework
  • Performance Baseline: Filter application under 3 seconds
  • Data Requirements: Historical data spanning multiple quarters/years

Prerequisites

  • Setup Requirements: Historical data available across different time periods
  • User Roles Permissions: O&M Manager with filtering permissions
  • Test Data:
    • Q2 2025 data (April 1 - June 30, 2025)
    • Known KPI values for filtered period
    • Orders with completion dates spanning multiple periods
  • Prior Test Cases: Dashboard KPI display functional

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to Service Order History dashboard

Dashboard loads with default 12-month view

Baseline 12-month data

Default state verification

2

Click "Filters" button

Filter modal/dropdown opens with date range options

N/A

Filter interface accessibility

3

Select custom date range: Q2 2025

Date picker allows selection of April 1 - June 30, 2025

Q2 2025: Apr 1 - Jun 30

Date range selection

4

Apply date filter

All KPI cards recalculate for Q2 2025 period only

Q2-specific calculations

KPI recalculation

5

Verify "Total Completed SOs" updates

Count reflects only Q2 2025 completed orders

Q2 completed orders count

Date-filtered counting

6

Verify "PM vs CM Ratio" changes

Ratio shows Q2-specific percentages (e.g., 65% / 35%)

Q2 ratio calculation

Period-specific ratio

7

Verify maintenance history table updates

Table shows only orders completed in Q2 2025

Q2 orders in table

Table filtering consistency

8

Test different date ranges

Apply various custom ranges, verify KPIs update correctly

Different periods

Range flexibility

9

Clear date filter

Dashboard returns to default 12-month view

Original baseline data

Filter reset functionality

Verification Points

  • Primary Verification: Entire dashboard (KPIs and table) filters correctly by custom date range
  • Secondary Verifications: Multiple date ranges work, Filter reset functionality
  • Negative Verification: Orders outside selected range excluded from all calculations and displays



Test Case 03: PM vs CM Ratio Calculation Accuracy

Test Case Metadata

  • Test Case ID: AX03US02_AC_003
  • Title: Verify PM vs CM Ratio Calculation Based on Order Type
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags

Tags: PM-CM-Ratio, Calculation-Logic, Order-Type-Classification, MOD-ServiceOrderHistory, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Performance-Analysis
  • Compliance Required: Yes
  • SLA Related: Yes

Quality Metrics

  • Risk Level: High
  • Complexity Level: High
  • Expected Execution Time: 4 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Medium
  • Failure Impact: Critical

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Order-Classification-Service, Ratio-Calculation-Engine
  • Code Module Mapped: AX
  • Requirement Coverage: AC #3 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: Engineering
  • Report Categories: Business-Logic-Validation, KPI-Accuracy
  • Trend Tracking: Yes
  • Executive Visibility: Yes
  • Customer Impact Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Order Classification Service, Mathematical Calculation Engine
  • Performance Baseline: Ratio calculation under 1 second
  • Data Requirements: Orders with clearly defined Preventive and Corrective types

Prerequisites

  • Setup Requirements: Completed orders with accurate Type classification
  • User Roles Permissions: O&M Manager with analytics access
  • Test Data:
    • 134 Preventive maintenance orders (72%)
    • 52 Corrective maintenance orders (28%)
    • Total: 186 completed orders
  • Prior Test Cases: Order type classification validated

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History dashboard with known data

Dashboard displays PM vs CM Ratio KPI

134 PM, 52 CM orders

Baseline data verification

2

Verify PM percentage calculation

PM shows 72% (134/186 * 100)

Expected: 72%

Preventive percentage

3

Verify CM percentage calculation

CM shows 28% (52/186 * 100)

Expected: 28%

Corrective percentage

4

Verify ratio display format

Shows "72% / 28%" with PM first, CM second

Display: "72% / 28%"

Format validation

5

Test with filtered data

Apply Q2 filter, verify ratio recalculates for period

Q2 data: 65% / 35%

Filtered ratio accuracy

6

Verify order type classification

Preventive includes: Preventive, Scheduled, Planned types

Order type mapping

Classification rules

7

Verify corrective classification

Corrective includes: Corrective, Emergency, Reactive types

Order type mapping

Classification accuracy

8

Test edge cases

Verify calculation with zero CM or PM orders

Edge case scenarios

Mathematical robustness

Verification Points

  • Primary Verification: PM vs CM ratio calculates correctly based on order Type field
  • Secondary Verifications: Percentage format correct, Classification rules accurate
  • Negative Verification: Other order types (Inspection, etc.) not counted in PM/CM calculation



Test Case 04: Completed Orders Table Display

Test Case Metadata

  • Test Case ID: AX03US02_AC_004
  • Title: Verify Searchable and Filterable Table Shows Only Completed Orders
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags

Tags: Maintenance-History-Table, Completed-Orders-Only, Search-Filter-Functionality, MOD-ServiceOrderHistory, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-Enterprise, Risk-Medium, Business-High

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Data-Analysis
  • Compliance Required: No
  • SLA Related: No

Quality Metrics

  • Risk Level: Medium
  • Complexity Level: Medium
  • Expected Execution Time: 5 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Medium
  • Failure Impact: High

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Search-Service, Filter-Framework, Status-Filter
  • Code Module Mapped: AX
  • Requirement Coverage: AC #4 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: QA
  • Report Categories: Table-Operations, Search-Functionality
  • Trend Tracking: No
  • Executive Visibility: No
  • Customer Impact Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Search Service, Filter Service, Order Status Service
  • Performance Baseline: Search results under 500ms
  • Data Requirements: Mix of completed, in-progress, and draft orders

Prerequisites

  • Setup Requirements: Orders with various statuses available
  • User Roles Permissions: O&M Manager with table view access
  • Test Data:
    • Completed orders: SO-001, SO-002, SO-003
    • In Progress orders: SO-004, SO-005
    • Draft orders: SO-006
  • Prior Test Cases: Dashboard table display functional

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History dashboard

Maintenance History table displays

All test data

Table baseline

2

Verify only completed orders shown

Table shows only orders with Status = 'Completed'

Only SO-001, SO-002, SO-003 visible

Status filtering

3

Verify in-progress orders excluded

In Progress and Draft orders not visible in table

SO-004, SO-005, SO-006 not shown

Exclusion validation

4

Test search functionality

Enter "SO-002" in search bar, only SO-002 appears

Search: "SO-002"

Search capability

5

Test asset name search

Search by asset name, matching orders appear

Search: "Main Control Valve"

Asset search

6

Test location search

Search by location, matching orders appear

Search: "Distribution Station"

Location search

7

Apply Type filter

Filter by "Corrective", only corrective orders shown

Filter: Type = Corrective

Type filtering

8

Apply multiple filters

Combine Type and Date filters, results match all criteria

Multiple active filters

Combined filtering

9

Clear all filters

Full completed orders list restored

Clear filters

Reset functionality

Verification Points

  • Primary Verification: Table displays only completed orders with search and filter functionality
  • Secondary Verifications: Multiple search fields work, Filters combine correctly
  • Negative Verification: Non-completed orders never appear in table regardless of search/filter



Test Case 05: Failure Mode Display Logic

Test Case Metadata

  • Test Case ID: AX03US02_AC_005
  • Title: Verify Failure Mode Display for Corrective Orders and N/A for Others
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags

Tags: Failure-Mode-Display, Conditional-Logic, Corrective-Orders, MOD-ServiceOrderHistory, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-Enterprise, Risk-Low, Business-Medium

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: Medium
  • Business Priority: Should-Have
  • Customer Journey: Failure-Analysis
  • Compliance Required: No
  • SLA Related: No

Quality Metrics

  • Risk Level: Low
  • Complexity Level: Medium
  • Expected Execution Time: 3 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Medium
  • Failure Impact: Medium

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Failure-Mode-Service, Order-Type-Classification
  • Code Module Mapped: AX
  • Requirement Coverage: AC #5 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: QA
  • Report Categories: Conditional-Display, Business-Logic
  • Trend Tracking: No
  • Executive Visibility: No
  • Customer Impact Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Failure Mode Service, Order Classification
  • Performance Baseline: Table render under 2 seconds
  • Data Requirements: Orders with various types and failure mode data

Prerequisites

  • Setup Requirements: Orders with different types and failure mode information
  • User Roles Permissions: O&M Manager with history view access
  • Test Data:
    • SO-002 (Type: Corrective, Failure Mode: "Seal Failure")
    • SO-001 (Type: Preventive, Failure Mode: should show "N/A")
    • SO-003 (Type: Inspection, Failure Mode: should show "N/A")
  • Prior Test Cases: Table display functional

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History dashboard table

Maintenance History table displays with Failure Mode column

All test orders

Column visibility

2

Locate SO-002 (Corrective type)

Failure Mode column shows "Seal Failure"

SO-002: Corrective, Seal Failure

Corrective order failure mode

3

Locate SO-001 (Preventive type)

Failure Mode column shows "N/A"

SO-001: Preventive

Non-corrective shows N/A

4

Locate SO-003 (Inspection type)

Failure Mode column shows "N/A"

SO-003: Inspection

Non-corrective shows N/A

5

Filter by Corrective type

All visible orders show actual failure modes (no N/A)

Filter: Type = Corrective

Corrective-only view

6

Filter by Preventive type

All visible orders show "N/A" in Failure Mode

Filter: Type = Preventive

Preventive-only view

7

Test edge case - Corrective without failure mode

Corrective order with no recorded failure mode shows "N/A"

Corrective order, no failure data

Edge case handling

Verification Points

  • Primary Verification: Failure Mode displays actual value for Corrective orders, "N/A" for all others
  • Secondary Verifications: Column always present, Edge cases handled appropriately
  • Negative Verification: Preventive/Inspection orders never show failure mode values



Test Case 06: Cost and Labor Hours Display

Test Case Metadata

  • Test Case ID: AX03US02_AC_006
  • Title: Verify Total Cost and Labor Hours Display for Each Completed Order
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags

Tags: Cost-Display, Labor-Hours, Financial-Data, Currency-Format, MOD-ServiceOrderHistory, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-Medium, Business-Critical

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Cost-Analysis
  • Compliance Required: Yes
  • SLA Related: No

Quality Metrics

  • Risk Level: Medium
  • Complexity Level: Low
  • Expected Execution Time: 2 minutes
  • Reproducibility Score: High
  • Data Sensitivity: High
  • Failure Impact: Critical

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Cost-Service, Labor-Tracking-Service
  • Code Module Mapped: AX
  • Requirement Coverage: AC #6 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: Product
  • Report Categories: Financial-Display, Cost-Analysis
  • Trend Tracking: Yes
  • Executive Visibility: Yes
  • Customer Impact Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Cost Calculation Service, Labor Hour Tracking
  • Performance Baseline: Table data load under 2 seconds
  • Data Requirements: Completed orders with cost and labor data

Prerequisites

  • Setup Requirements: Completed orders with recorded costs and labor hours
  • User Roles Permissions: O&M Manager with cost data access
  • Test Data:
    • SO-002: Total Cost $850.75, Labor Hours 6h
    • SO-001: Total Cost $1,250.50, Labor Hours 4.5h
    • SO-003: Total Cost $300.00, Labor Hours 2h
  • Prior Test Cases: Table display and data loading functional

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History dashboard table

Table displays with Total Cost column

All cost data visible

Cost column presence

2

Verify SO-002 cost display

Total Cost shows "$850.75" with currency formatting

SO-002: $850.75

Currency format validation

3

Verify SO-002 labor hours

Cost column subtitle shows "6h labor"

SO-002: 6h labor

Labor hours display

4

Verify SO-001 cost and labor

Shows "$1,250.50" with "4.5h labor" subtitle

SO-001: $1,250.50, 4.5h

Decimal hours handling

5

Verify SO-003 cost and labor

Shows "$300.00" with "2h labor" subtitle

SO-003: $300.00, 2h

Format consistency

6

Test cost column sorting

Click Total Cost header, orders sort by cost amount

Descending cost order

Sorting functionality

7

Verify labor hours in sorting

Sorting uses cost amount, not labor hours

Cost-based sort priority

Sort priority validation

Verification Points

  • Primary Verification: Each completed order displays Total Cost (currency formatted) and Labor Hours
  • Secondary Verifications: Currency formatting consistent, Labor hours shown as subtitle/secondary info
  • Negative Verification: Orders without cost/labor data show appropriate placeholder or zero values



Test Case 07: Actions Menu Functionality

Test Case Metadata

  • Test Case ID: AX03US02_AC_007
  • Title: Verify Actions Menu Provides View Details and Print/Download Report
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags

Tags: Actions-Menu, View-Details, Print-Download-Report, MOD-ServiceOrderHistory, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-Enterprise, Risk-Medium, Business-Medium

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: Medium
  • Business Priority: Should-Have
  • Customer Journey: Report-Generation
  • Compliance Required: No
  • SLA Related: No

Quality Metrics

  • Risk Level: Medium
  • Complexity Level: Medium
  • Expected Execution Time: 4 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Medium
  • Failure Impact: Medium

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Actions-Framework, Report-Generation-Service, Detail-View-Service
  • Code Module Mapped: AX
  • Requirement Coverage: AC #7 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: QA
  • Report Categories: Actions-Testing, Report-Generation
  • Trend Tracking: No
  • Executive Visibility: No
  • Customer Impact Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Report Generation Service, Detail View Service
  • Performance Baseline: Report generation under 10 seconds
  • Data Requirements: Completed orders with full detail data

Prerequisites

  • Setup Requirements: Report generation service functional
  • User Roles Permissions: O&M Manager with report access
  • Test Data:
    • SO-002 with complete order details
    • Orders with various completion statuses
  • Prior Test Cases: Table actions column functional

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History table

Table displays with Actions column (three dots menu)

History table visible

Actions column presence

2

Click Actions menu for SO-002

Menu opens with available action options

SO-002 actions menu

Menu accessibility

3

Verify "View Details" option present

"View Details" option visible and clickable

SO-002 menu options

View Details availability

4

Click "View Details"

Read-only detailed view of completed service order opens

SO-002 detail view

Detail view functionality

5

Verify detail view content

Shows complete order information (ID, cost, labor, failure mode, etc.)

SO-002 complete details

Detail completeness

6

Return to History table

Navigate back to main history view

Return navigation

Navigation flow

7

Click Actions, verify "Print/Download Report"

"Print/Download Report" option visible and clickable

SO-002 report option

Report option availability

8

Click "Print/Download Report"

PDF or HTML report generates/downloads

SO-002 report file

Report generation

9

Verify report content

Report contains order summary with key details

Generated report content

Report completeness

Verification Points

  • Primary Verification: Actions menu provides functional View Details and Print/Download Report links
  • Secondary Verifications: Detail view shows complete information, Report contains appropriate content
  • Negative Verification: Actions menu only shows appropriate options for historical (completed) orders



Test Case 08: PM Schedule Link Logic

Test Case Metadata

  • Test Case ID: AX03US02_AC_008
  • Title: Verify View Linked PM Schedule Disabled When No Schedule Link Exists
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags

Tags: PM-Schedule-Link, Conditional-Actions, Schedule-Integration, MOD-ServiceOrderHistory, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-Medium, Business-Medium

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: Medium
  • Business Priority: Should-Have
  • Customer Journey: Schedule-Analysis
  • Compliance Required: No
  • SLA Related: No

Quality Metrics

  • Risk Level: Medium
  • Complexity Level: High
  • Expected Execution Time: 3 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Medium
  • Failure Impact: Medium

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Schedule
  • Integration Points: Schedule-Service, Link-Validation-Service
  • Code Module Mapped: AX
  • Requirement Coverage: AC #8 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: Engineering
  • Report Categories: Schedule-Integration, Conditional-Logic
  • Trend Tracking: No
  • Executive Visibility: No
  • Customer Impact Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Schedule Service, Link Validation Service
  • Performance Baseline: Menu load under 1 second
  • Data Requirements: Orders with and without schedule links

Prerequisites

  • Setup Requirements: Orders with various schedule link statuses
  • User Roles Permissions: O&M Manager with schedule access
  • Test Data:
    • SO-001 (Generated from PM schedule, has link)
    • SO-002 (Emergency repair, no schedule link)
    • SO-003 (Manual creation, no schedule link)
  • Prior Test Cases: Actions menu functional

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Click Actions menu for SO-001 (has schedule link)

Menu opens with "View Linked PM Schedule" option enabled

SO-001 with schedule link

Enabled link validation

2

Click "View Linked PM Schedule" for SO-001

Navigates to associated PM schedule view

SO-001 schedule navigation

Link functionality

3

Return to History, click Actions for SO-002 (no link)

Menu shows "View Linked PM Schedule" option disabled/grayed out

SO-002 emergency repair

Disabled state validation

4

Hover over disabled PM Schedule link

Tooltip shows reason for disabled state

Tooltip explanation

User feedback

5

Attempt to click disabled link

No action occurs, link remains non-functional

Disabled link behavior

Prevention validation

6

Test with SO-003 (manual creation)

"View Linked PM Schedule" option disabled

SO-003 manual order

Consistent disable logic

Verification Points

  • Primary Verification: View Linked PM Schedule disabled when no schedule link exists
  • Secondary Verifications: Enabled links work correctly, User feedback for disabled state
  • Negative Verification: Disabled links cannot be clicked, No false positives for link availability



Test Case 09: Export Data Functionality

Test Case Metadata

  • Test Case ID: AX03US02_AC_009
  • Title: Verify Export Data Downloads Currently Filtered Historical Orders
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags

Tags: Export-Data, CSV-XLSX-Export, Filtered-Data-Export, MOD-ServiceOrderHistory, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-Medium, Business-High

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Data-Export-Analysis
  • Compliance Required: Yes
  • SLA Related: No

Quality Metrics

  • Risk Level: Medium
  • Complexity Level: Medium
  • Expected Execution Time: 4 minutes
  • Reproducibility Score: High
  • Data Sensitivity: High
  • Failure Impact: High

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Export-Service, Filter-State-Service
  • Code Module Mapped: AX
  • Requirement Coverage: AC #9 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: Product
  • Report Categories: Export-Functionality, Data-Analysis
  • Trend Tracking: Yes
  • Executive Visibility: Yes
  • Customer Impact Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Export Service, File Generation Service
  • Performance Baseline: Export completion under 30 seconds
  • Data Requirements: Historical orders for export testing

Prerequisites

  • Setup Requirements: Export service functional, file download permissions
  • User Roles Permissions: O&M Manager with export permissions
  • Test Data:
    • Full dataset: 186 historical orders
    • Q2 2025 filtered dataset: subset of orders
    • Corrective type filtered dataset: corrective orders only
  • Prior Test Cases: Filtering and table display functional

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History dashboard

Full historical data displayed, Export Data button visible

All 186 orders

Export button availability

2

Click "Export Data" button without filters

CSV/XLSX file downloads with all 186 historical orders

Full dataset export

Complete data export

3

Apply Q2 2025 date filter

Table shows only Q2 2025 orders

Q2 2025 filtered data

Filter application

4

Click "Export Data" with date filter active

Export file contains only Q2 2025 orders (respects filter)

Q2 filtered export

Filtered export validation

5

Apply additional Type = Corrective filter

Table shows only Q2 corrective orders

Q2 corrective orders

Multiple filter application

6

Export with multiple filters active

Export contains only orders matching all active filters

Multi-filtered export

Complex filter export

7

Verify export file format

File is CSV or XLSX format as specified

Export file format

Format validation

8

Examine export file content

File contains all table columns with correct data

Export content validation

Data accuracy

9

Clear filters and re-export

New export contains full dataset again

Full dataset restore

Filter reset export

Verification Points

  • Primary Verification: Export Data downloads currently filtered list of historical orders
  • Secondary Verifications: All active filters respected, File format correct
  • Negative Verification: Export never includes more data than currently visible in filtered table



Test Case 10: Currency Formatting for Average Cost

Test Case Metadata

  • Test Case ID: AX03US02_AC_010
  • Title: Verify Average Cost Per SO KPI Formatted as Currency
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags

Tags: Currency-Formatting, Average-Cost-KPI, Financial-Display, MOD-ServiceOrderHistory, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-Low, Business-Medium

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: Medium
  • Business Priority: Should-Have
  • Customer Journey: Financial-Analysis
  • Compliance Required: No
  • SLA Related: No

Quality Metrics

  • Risk Level: Low
  • Complexity Level: Low
  • Expected Execution Time: 2 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Medium
  • Failure Impact: Medium

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Currency-Formatting-Service, KPI-Display-Service
  • Code Module Mapped: AX
  • Requirement Coverage: AC #10 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: Product
  • Report Categories: Financial-Display, Formatting-Validation
  • Trend Tracking: No
  • Executive Visibility: No
  • Customer Impact Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Currency Formatting Service
  • Performance Baseline: KPI display under 1 second
  • Data Requirements: Orders with cost data for average calculation

Prerequisites

  • Setup Requirements: Historical orders with total cost values
  • User Roles Permissions: O&M Manager with KPI access
  • Test Data:
    • Orders with various costs for average calculation
    • Expected average: $1,275.32
  • Prior Test Cases: KPI calculation functional

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History dashboard

Dashboard displays with Average Cost Per SO KPI

Historical cost data

KPI visibility

2

Verify currency symbol present

Average Cost shows dollar sign ($) prefix

Expected: $1,275.32

Currency symbol validation

3

Verify decimal precision

Cost displays with 2 decimal places

Format: $X,XXX.XX

Decimal precision

4

Verify thousands separator

Large amounts show comma separator

Format: $1,275.32

Thousands formatting

5

Test with different data ranges

Apply filters, verify currency formatting maintained

Filtered calculations

Format consistency

6

Test edge cases

Zero costs, very large amounts maintain formatting

Edge case amounts

Format robustness

Verification Points

  • Primary Verification: Average Cost Per SO KPI displays in proper currency format
  • Secondary Verifications: Format consistent across different amounts, Decimal precision correct
  • Negative Verification: No raw numbers displayed without currency formatting



Test Case 11: Multi-Field Search Functionality

Test Case Metadata

  • Test Case ID: AX03US02_AC_011
  • Title: Verify Search Bar Queries Across Multiple Fields
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags

Tags: Multi-Field-Search, Search-Functionality, Cross-Column-Search, MOD-ServiceOrderHistory, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-Enterprise, Risk-Low, Business-High

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: Medium
  • Business Priority: Should-Have
  • Customer Journey: Data-Search
  • Compliance Required: No
  • SLA Related: No

Quality Metrics

  • Risk Level: Low
  • Complexity Level: Medium
  • Expected Execution Time: 4 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Low
  • Failure Impact: Medium

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Search-Service, Multi-Column-Index
  • Code Module Mapped: AX
  • Requirement Coverage: AC #11 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: QA
  • Report Categories: Search-Functionality, User-Experience
  • Trend Tracking: No
  • Executive Visibility: No
  • Customer Impact Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Search Service, Database Indexing
  • Performance Baseline: Search results under 500ms
  • Data Requirements: Orders with varied content in searchable fields

Prerequisites

  • Setup Requirements: Search service functional, data indexed
  • User Roles Permissions: O&M Manager with search access
  • Test Data:
    • SO-002: Emergency Valve Repair, VLV-045 Main Control Valve
    • SO-001: Monthly Pump Maintenance, PUMP-001 Primary Intake
    • SO-003: Quarterly Tank Inspection, TNK-003 Storage Tank
  • Prior Test Cases: Search interface accessible

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History dashboard

Search bar visible and functional

N/A

Search interface availability

2

Search by SO ID

Enter "SO-002", only SO-002 appears in results

Search: "SO-002"

SO ID field search

3

Clear and search by SO Name

Enter "Emergency", SO-002 appears

Search: "Emergency"

SO Name field search

4

Clear and search by Asset ID

Enter "VLV-045", SO-002 appears

Search: "VLV-045"

Asset ID field search

5

Clear and search by Asset Name

Enter "Main Control", SO-002 appears

Search: "Main Control"

Asset Name field search

6

Search across multiple records

Enter "Pump", returns both PUMP-related and "Emergency" if description contains "pump"

Search: "Pump"

Cross-record search

7

Test partial matches

Enter "Tank", finds Tank Inspection and any descriptions with "tank"

Search: "Tank"

Partial matching

8

Test case insensitivity

Enter "EMERGENCY" (caps), still finds "Emergency Valve Repair"

Search: "EMERGENCY"

Case insensitive search

9

Test special characters

Search handles hyphens, numbers in asset IDs correctly

Search: "VLV-045"

Special character handling

Verification Points

  • Primary Verification: Search queries across SO ID, SO Name, Asset ID/Name, and Description fields
  • Secondary Verifications: Partial matches work, Case insensitive, Special characters handled
  • Negative Verification: Search doesn't return results from non-searchable fields



Test Case 12: Instant Filter and Search Updates

Test Case Metadata

  • Test Case ID: AX03US02_AC_012
  • Title: Verify KPI Cards and Table Update Instantly When Filters Applied
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Performance
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags

Tags: Real-Time-Updates, Instant-Filter-Response, Performance, MOD-ServiceOrderHistory, P1-Critical, Phase-Regression, Type-Performance, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-Medium, Business-Critical

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Interactive-Analysis
  • Compliance Required: No
  • SLA Related: Yes

Quality Metrics

  • Risk Level: Medium
  • Complexity Level: High
  • Expected Execution Time: 3 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Low
  • Failure Impact: Critical

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Real-Time-Update-Service, Filter-Response-Framework
  • Code Module Mapped: AX
  • Requirement Coverage: AC #12 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: Engineering
  • Report Categories: Performance-Testing, Real-Time-Updates
  • Trend Tracking: Yes
  • Executive Visibility: Yes
  • Customer Impact Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Real-Time Update Framework, Performance Monitoring
  • Performance Baseline: Updates within 1 second of filter application
  • Data Requirements: Sufficient data volume to test update performance

Prerequisites

  • Setup Requirements: Performance monitoring tools enabled
  • User Roles Permissions: O&M Manager with filtering access
  • Test Data: Large dataset for performance validation
  • Prior Test Cases: Filtering functionality validated

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History dashboard

Baseline KPIs and table displayed

Full dataset

Initial state

2

Apply date filter

KPIs and table update within 1 second of filter application

Date range filter

Update speed validation

3

Measure update time

Use browser dev tools to measure response time

Performance timing

Response time measurement

4

Apply additional Type filter

Second filter updates instantly without page refresh

Type filter addition

Progressive filtering

5

Remove one filter

Updates instantly when filter removed

Filter removal

Reverse operation speed

6

Apply search term

Table filters instantly as user types

Live search

Real-time search response

7

Clear all filters

Dashboard returns to default state instantly

Filter reset

Complete reset speed

8

Test with large dataset

Performance maintained with maximum data volume

Full dataset

Scalability validation

Verification Points

  • Primary Verification: All KPI cards and table update within 1 second of filter application
  • Secondary Verifications: No page refresh required, Multiple filter changes maintain speed
  • Negative Verification: No delay, freezing, or loading states during filter updates



Test Case 13: Pagination Controls Navigation

Test Case Metadata

  • Test Case ID: AX03US02_AC_013
  • Title: Verify Pagination Controls Navigate Through Historical Records Correctly
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags

Tags: Pagination-Controls, Navigation, Large-Dataset-Handling, MOD-ServiceOrderHistory, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-Enterprise, Risk-Low, Business-Medium

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: Medium
  • Business Priority: Should-Have
  • Customer Journey: Data-Navigation
  • Compliance Required: No
  • SLA Related: No

Quality Metrics

  • Risk Level: Low
  • Complexity Level: Medium
  • Expected Execution Time: 3 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Low
  • Failure Impact: Medium

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Pagination-Framework, Data-Loading-Service
  • Code Module Mapped: AX
  • Requirement Coverage: AC #13 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: QA
  • Report Categories: Navigation-Testing, User-Interface
  • Trend Tracking: No
  • Executive Visibility: No
  • Customer Impact Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Pagination Service, Data Loading Framework
  • Performance Baseline: Page navigation under 2 seconds
  • Data Requirements: Sufficient historical records to require pagination (100+ orders)

Prerequisites

  • Setup Requirements: Large dataset requiring pagination
  • User Roles Permissions: O&M Manager with table access
  • Test Data: 186+ historical orders requiring multiple pages
  • Prior Test Cases: Table display functional

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History table

Table displays with pagination controls at bottom

186+ orders dataset

Pagination visibility

2

Verify page 1 display

Shows first set of records (e.g., 1-50 of 186)

Page 1 records

Initial page state

3

Click "Next" button

Navigates to page 2, shows next set of records

Page 2 records

Forward navigation

4

Verify page indicator

Page indicator shows "2" as current page

Page 2 active

Current page indication

5

Click page number "3" directly

Jumps directly to page 3

Page 3 records

Direct page navigation

6

Click "Previous" button

Returns to page 2

Page 2 records

Backward navigation

7

Navigate to last page

Click last page number, shows final records

Last page records

End boundary

8

Test "Previous" on first page

Previous button disabled on page 1

Page 1 state

Start boundary

9

Test "Next" on last page

Next button disabled on last page

Last page state

End boundary

10

Apply filter and test pagination

Pagination adjusts for filtered results

Filtered pagination

Filtered navigation

Verification Points

  • Primary Verification: Pagination controls correctly navigate through all historical records
  • Secondary Verifications: Page indicators accurate, Boundary conditions handled properly
  • Negative Verification: Cannot navigate beyond available pages, Disabled states work correctly



Test Case 14: Total Labor Hours KPI Display

Test Case Metadata

  • Test Case ID: AX03US02_AC_014
  • Title: Verify Total Labor Hours KPI Shows Sum and Average Per SO
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags

Tags: Labor-Hours-KPI, Sum-Average-Calculation, KPI-Display, MOD-ServiceOrderHistory, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-Medium, Business-Critical

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Labor-Analysis
  • Compliance Required: Yes
  • SLA Related: Yes

Quality Metrics

  • Risk Level: Medium
  • Complexity Level: Medium
  • Expected Execution Time: 3 minutes
  • Reproducibility Score: High
  • Data Sensitivity: Medium
  • Failure Impact: Critical

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Labor-Hours-Service, Mathematical-Calculation
  • Code Module Mapped: AX
  • Requirement Coverage: AC #14 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: Product
  • Report Categories: Labor-Analytics, KPI-Validation
  • Trend Tracking: Yes
  • Executive Visibility: Yes
  • Customer Impact Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Labor Hours Calculation Service
  • Performance Baseline: KPI calculation under 1 second
  • Data Requirements: Historical orders with recorded labor hours

Prerequisites

  • Setup Requirements: Historical orders with labor hour data
  • User Roles Permissions: O&M Manager with labor analytics access
  • Test Data:
    • Total labor hours across all orders: 924 hours
    • Total completed orders: 186
    • Expected average: 4.97 hours per SO
  • Prior Test Cases: KPI calculations functional

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History dashboard

Total Labor Hours KPI card visible

Historical data

KPI visibility

2

Verify total hours display

Main KPI shows "924" (total hours)

Expected: 924 hours

Sum calculation

3

Verify average hours subtitle

Subtitle shows "Avg 4.97 hrs per SO"

Expected: 4.97 avg

Average calculation

4

Verify calculation accuracy

Manual verification: 924 total ÷ 186 orders = 4.97

Mathematical verification

Calculation accuracy

5

Apply date filter

Both total and average recalculate for filtered period

Filtered timeframe

Dynamic recalculation

6

Verify filtered calculations

Filtered total hours and new average per SO display correctly

Filtered calculations

Filter impact validation

7

Test with zero labor hours

Orders without labor data handled appropriately

Edge case handling

Zero value handling

Verification Points

  • Primary Verification: Total Labor Hours KPI displays sum of all hours and calculated average per SO
  • Secondary Verifications: Both values update with filtering, Calculations mathematically accurate
  • Negative Verification: Orders without labor data don't break calculation, Zero division handled



Test Case 15: Read-Only Historical Data

Test Case Metadata

  • Test Case ID: AX03US02_AC_015
  • Title: Verify Historical Data Presented as Read-Only
  • Created By: Prachi
  • Created Date: 2025-08-26
  • Version: 1.0

Classification

  • Module/Feature: Service Order History (AX03US02)
  • Test Type: Security
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Security
  • Automation Status: Manual

Enhanced Tags

Tags: Read-Only-Data, Data-Integrity, Historical-Security, MOD-ServiceOrderHistory, P1-Critical, Phase-Security, Type-Security, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical

Business Context

  • Customer Segment: Enterprise
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Data-Integrity
  • Compliance Required: Yes
  • SLA Related: Yes

Quality Metrics

  • Risk Level: High
  • Complexity Level: Low
  • Expected Execution Time: 3 minutes
  • Reproducibility Score: High
  • Data Sensitivity: High
  • Failure Impact: Critical

Coverage Tracking

  • Feature Coverage: 100%
  • Integration Points: Data-Security-Framework, Read-Only-Enforcement
  • Code Module Mapped: AX
  • Requirement Coverage: AC #15 Complete
  • Cross Platform Support: Web

Stakeholder Reporting

  • Primary Stakeholder: Engineering
  • Report Categories: Data-Security, Historical-Integrity
  • Trend Tracking: No
  • Executive Visibility: Yes
  • Customer Impact Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Security Framework, Data Protection Service
  • Performance Baseline: N/A (Security focused)
  • Data Requirements: Historical completed orders

Prerequisites

  • Setup Requirements: Historical data with completed status
  • User Roles Permissions: O&M Manager with history access (read-only)
  • Test Data: Completed historical service orders
  • Prior Test Cases: Historical data display functional

Test Procedure

Step

Action

Expected Result

Test Data

Comments

1

Navigate to History dashboard

Historical data displays without edit options

Historical orders

Read-only interface

2

Verify no edit buttons in table

No edit icons, buttons, or links in table rows

Table interface

Edit prevention

3

Right-click on table data

Context menu (if any) doesn't provide edit options

Table data

Context menu restrictions

4

Access detailed order view

Detail view shows data in read-only format

Order detail view

Detail view read-only

5

Verify no form inputs in details

No text fields, dropdowns, or checkboxes for editing

Detail view interface

Input prevention

6

Test keyboard shortcuts

Common edit shortcuts (Ctrl+E, F2, etc.) have no effect

Keyboard interaction

Shortcut prevention

7

Verify Actions menu limitations

Actions menu only shows view/report options, no edit/delete

Actions menu options

Action limitations

8

Test URL manipulation

Direct URL attempts to edit historical records fail

URL security

URL protection

Verification Points

  • Primary Verification: All historical data presented as read-only with no edit capabilities
  • Secondary Verifications: No edit interface elements present, Security enforced at all levels
  • Negative Verification: No method exists to modify historical completed order data



Complete Test Suite Summary

Acceptance Criteria Coverage: 15/15 ✅

P1-Critical Test Cases (8):

  • AC_001: Four KPI Cards Display
  • AC_002: Custom Date Range Filtering
  • AC_003: PM vs CM Ratio Calculation
  • AC_004: Completed Orders Table
  • AC_006: Cost and Labor Hours Display
  • AC_009: Export Data Functionality
  • AC_012: Instant Updates
  • AC_014: Total Labor Hours KPI
  • AC_015: Read-Only Data

P2-High Test Cases (7):

  • AC_005: Failure Mode Display Logic
  • AC_007: Actions Menu Functionality
  • AC_008: PM Schedule Link Logic
  • AC_010: Currency Formatting
  • AC_011: Multi-Field Search
  • AC_013: Pagination Controls

Test Execution Metrics:

  • Total Estimated Time: 52 minutes
  • Automated Tests: 11
  • Manual Tests: 4
  • Integration Points: 25+ services tested
  • Performance Benchmarks: All defined with specific limits

Quality Gates:

  • Release Blockers: Any P1-Critical failure, Security vulnerabilities, Performance baseline violations
  • Data Integrity: Historical data immutability enforced
  • Performance Standards: All operations within defined time limits# Service Order History - Complete Test Cases (AX03US02)


Back to top