Skip to main content

Communication Workflows (UX03US04)

Communication Workflows (UX03US04)

Total Test Cases:21
Total Acceptance Criteria:21
Total Coverage Percentage:

Test Scenario Summary

Functional Test Scenarios Covered:

  • Workflow Creation Flow - Complete 3-step wizard process (Details → Trigger → Actions)
  • Workflow Management - View, Edit, Delete, Filter workflows
  • Communication Actions - Multi-channel message configuration (Email, SMS, WhatsApp)
  • Trigger Configuration - Time-based triggers (Specific Date/Time only)
  • Workflow Execution - Automated workflow processing
  • Target List Integration - Target list selection in trigger configuration
  • CC/BCC Email Configuration - Enhanced email recipient management

Non-Functional Test Scenarios:

  • Performance Monitoring - History and analytics tracking
  • Integration Points - External system dependencies
  • Security & Access Control - Role-based permissions
  • Data Validation - Input validation and error handling
  • Cross-Platform Compatibility - Desktop browser testing only

FUNCTIONAL TEST CASES

Test Suite: Workflow Creation

Test Case 1: Complete Workflow Creation with 3-Step Wizard

Test Case ID: UX03US04_TC_001
Title: Verify complete workflow creation using 3-step wizard with multi-channel configuration and CC/BCC support
Created By: Prachi
Created Date: 2025-05-28
Version: V1.0.0

Classification:

  • Module/Feature: Workflow Creation Engine
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Manual
  • Enhanced Tags: MOD-Communication, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Low, Business-Critical, Revenue-Impact-High, HappyPath, Database, Services

Business Context:

  • Customer Segment: All
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Workflow-Creation
  • Compliance Required: Yes
  • SLA Related: Yes

Quality Metrics:

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

Coverage Tracking:

  • Feature Coverage: 95%
  • Integration Points: Workflow Engine, Template Service, Trigger Engine, NSC Event System, SendGrid, Twilio
  • Code Module Mapped: Communication
  • Requirement Coverage: REQ-WF-001, REQ-WF-002, REQ-WF-003, REQ-EMAIL-001, REQ-SMS-001, REQ-EVENT-001
  • Cross Platform Support: Web, Email, SMS, WhatsApp

Stakeholder Reporting:

  • Primary Stakeholder: Engineering
  • Report Categories: Quality-Dashboard, Feature-Coverage, Smoke-Results, Multi-Channel-Integration
  • Trend Tracking: Yes
  • Executive Visibility: Yes
  • Customer Impact Level: Critical

Requirements Traceability:

  • Acceptance Criteria Covered: #1 (3-step wizard process), #2 (Multi-channel configuration), #6 (CC/BCC email support), #8 (Event-based triggers)
  • Related Requirements: REQ-WF-001 (3-step wizard), REQ-WF-002 (Trigger config), REQ-WF-003 (Multi-channel), REQ-EMAIL-002 (CC/BCC), REQ-EVENT-001 (NSC events)
  • Related Bugs: N/A
  • Related Test Cases: UX03US04_TC_002, UX03US04_TC_003, UX03US04_TC_004

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Workflow Engine, SendGrid API, Twilio API, NSC Event System, Template Service
  • Performance Baseline: <1 second page load, <500ms workflow creation
  • Data Requirements: Valid workflow configuration data, Test templates, Target lists, NSC event data

Prerequisites:

Setup Requirements:

  • User logged in as Utility Admin
  • Template library populated with test templates
  • Target lists configured and accessible
  • Email/SMS providers configured (SendGrid, Twilio)
  • NSC event system active
  • Browser cache cleared
  • User Roles/Permissions: CSO manager , Utility admin
  • Prior Test Cases: Login functionality verified, Navigation verified, Basic system setup completed

Test Procedure:

Step

Action

Expected Result

Test Data

Comment

1

Navigate to Communication Workflows page

Workflows page loads with Active tab selected

N/A

Base navigation

2

Click "New Workflow" button

Step 1 (Details) opens with progress indicator showing 1/3

N/A

AC#1: 3-step wizard initialization

3

Enter Workflow Name

Field accepts input, no validation errors

"Customer Onboarding Sequence"

AC#1: Details step data entry

4

Enter Description

Field accepts input, character count updates

"Automated welcome messages for new customers"

AC#1: Details completion

5

Select Audience Type

Dropdown shows Consumer, Technician, Business User options

Select "Consumer"

AC#1: Audience selection

6

Click "Next" button

Navigate to Trigger step, step 2 becomes active

N/A

AC#1: Wizard step progression

7

Select "Event-Based" trigger type

Event-Based option selected, Event Type dropdown appears

N/A

AC#8: Event trigger selection

8

Select Event Type

Dropdown shows system events

Select "NSC-Created"

AC#8: System event configuration

9

Click "Next" button

Navigate to Actions step, step 3 becomes active

N/A

AC#1: Final step navigation

10

Click "Add First Action"

Communication channel selection appears

N/A

AC#2: Channel selection

11

Select Email channel

Email selected, message source options appear

N/A

AC#2: Email channel configuration

12

Click "Create New Message"

Message composition fields appear with CC/BCC options

N/A

AC#6: Enhanced email composer

13

Enter CC field

CC field accepts multiple email addresses

"manager@utility.com, billing@utility.com"

AC#6: CC functionality

14

Enter BCC field

BCC field accepts email addresses

"audit@utility.com"

AC#6: BCC functionality

15

Enter email subject

Subject field accepts input

"Welcome to UtilityConnect!"

AC#2: Email content

16

Enter email content

Message body accepts rich text input

"Dear [Customer.FirstName], Welcome to our service..."

Variable support

17

Add SMS Action

Select SMS channel and configure message

"Welcome! Check your email for details."

AC#2: SMS channel

18

Add WhatsApp Action

Select WhatsApp channel and configure message

"Welcome! 🎉 Your service is active..."

AC#2: WhatsApp channel

19

Click "Create Workflow"

Workflow created successfully with success message

N/A

AC#1: Workflow completion

20

Verify workflow in Active tab

New workflow appears in Active workflows list with correct details

N/A

Workflow activation

Verification Points:

  • Primary Verification: Complete 3-step wizard creates multi-channel workflow with CC/BCC support successfully
  • Secondary Verifications: All entered data preserved, event triggers configured, all channels functional
  • Negative Verification: Cannot skip required steps, invalid email addresses in CC/BCC rejected

Test Case 2: Time-Based Scheduling with Target Lists and Sequential Actions

Test Case ID: UX03US04_TC_002
Title: Verify time-based triggers with target list integration and sequential message delays
Created By: Prachi
Created Date: 2025-05-28
Version: V1.0.0

Classification:

  • Module/Feature: Time-Based Scheduling Engine
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual
  • Enhanced Tags: MOD-Communication, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-High, Revenue-Impact-High, HappyPath, EdgeCase, Database, Services

Business Context:

  • Customer Segment: All
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Automated-Scheduling
  • Compliance Required: No
  • SLA Related: Yes

Quality Metrics:

  • Risk Level: Medium
  • Complexity Level: Complex
  • Expected Execution Time: 72 hours (long-running for timing verification)
  • Reproducibility Score: High
  • Data Sensitivity: Low
  • Failure Impact: High

Coverage Tracking:

  • Feature Coverage: 85%
  • Integration Points: Target List Service,API
  • Code Module Mapped: Communication
  • Requirement Coverage: REQ-SCHED-001, REQ-TARGET-001, REQ-SEQ-001, REQ-TIME-001
  • Cross Platform Support: Web, Email, SMS, WhatsApp

Stakeholder Reporting:

  • Primary Stakeholder: Engineering
  • Report Categories: Quality-Dashboard, Scheduling-Accuracy, Target-List-Integration, Sequential-Processing
  • Trend Tracking: Yes
  • Executive Visibility: No
  • Customer Impact Level: High

Requirements Traceability:

  • Acceptance Criteria Covered: #3 (Time-based triggers), #4 (Automated processing), #5 (Target lists in triggers), #20 (Sequential message delays)
  • Related Requirements: REQ-SCHED-001 (Time-based scheduling), REQ-TARGET-001 (Target list integration), REQ-SEQ-001 (Sequential actions), REQ-AUTO-001 (Automated processing)
  • Related Bugs: N/A
  • Related Test Cases: UX03US04_TC_001, UX03US04_TC_003, UX03US04_TC_015

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Scheduler Service, Target List Service, Action Engine, Database, Time Zone Service
  • Performance Baseline: ±5 minutes timing accuracy, <2 seconds scheduling response, <300ms target list load
  • Data Requirements: Target lists configured, Future date/time options, Multi-action workflow configurations

Prerequisites: Setup Requirements:

  • User logged in as Utility Admin
  • Target lists configured and populated ("Inactive Users" list available)
  • Scheduler service running and configured
  • Time zone configuration verified
  • Multi-channel communication enabled
  • Timing precision configured (±5 minutes tolerance)
  • User Roles/Permissions: CSO Manager, utility admin
  • Prior Test Cases: UX03US04_TC_001 passed, Target list service verified, Scheduler service tested

Test Procedure:

Step

Action

Expected Result

Test Data

comments

1

Navigate to Communication Workflows page

Page loads with Active tab selected

N/A

Base navigation

2

Click "New Workflow" button

Create New Workflow modal opens

N/A

Workflow creation start

3

Enter workflow name and details

Fields accept input successfully

"Reengagement Campaign"

Workflow identification

4

Select "Consumer" audience type

Consumer option selected

N/A

Audience targeting

5

Click "Next" to configure trigger

Navigate to Trigger step

N/A

AC#3: Trigger configuration

6

Select "Time-Based" trigger type

Time-Based option selected, sub-options appear

N/A

AC#3: Time-based selection

7

Select "Specific Date and Time"

Date and Time input fields appear (no recurring option)

N/A

AC#3: Specific timing only

8

Select Target List in trigger step

Target list dropdown appears and shows available lists

Select "Inactive Users (1,250)"

AC#5: Target list in trigger

9

Set date for campaign

Date picker opens, future date selectable

Tomorrow's date

AC#3: Future date validation

10

Set time for campaign

Time picker allows time selection

"10:00:00"

AC#3: Time specification

11

Click "Next" to configure actions

Navigate to Actions step

N/A

Action configuration

12

Add first email action

Select Email channel, configure immediate delivery

Subject: "We Miss You!"

AC#20: Sequential start

13

Add SMS follow-up with delay

Select SMS, set 2-day delay after email

"After previous action + 2 days"

AC#20: Sequential delays

14

Add WhatsApp follow-up

Select WhatsApp, set 1-day delay after SMS

"After previous action + 1 day"

AC#20: Chained timing

15

Create and activate workflow

Workflow created and scheduled for automatic execution

N/A

AC#4: Automated processing

16

Wait for scheduled execution time

Workflow executes automatically at specified time

N/A

AC#4: Automation verification

17

Monitor sequential action execution

Email sends immediately, SMS after 2 days, WhatsApp after 3 days total

Actual timing verification

AC#20: Timing accuracy

18

Verify target list integration

Messages sent only to target list recipients

Target list recipients only

AC#5: Target list filtering

Verification Points:

  • Primary Verification: Time-based workflow executes automatically with target lists and precise sequential delays
  • Secondary Verifications: Target list properly integrated in trigger step, timing accuracy within ±5 minutes
  • Negative Verification: Past dates rejected, target list not available in Details step, invalid delays prevented



Test Case 3: Edit Workflow - Communication Channel Non-Editable

Test Case ID: UX03US04_TC_003
Title: Verify communication channel type cannot be edited in existing workflows
Created By: Prachi
Created Date: 2025-05-28
Version: 1.0

Classification:

  • Module/Feature: Workflow Management
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags:

MOD-Communication, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-Critical, Edit-Restrictions, Channel-Immutability,HappyPath

Business Context:

  • Customer Segment: All
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Daily-Usage
  • 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: 60%
  • Integration Points: Workflow Engine, Edit Service,
  • Code Module Mapped: Communication
  • Requirement Coverage: REQ-WF-004, REQ-VAL-001, REQ-EDIT-001
  • Cross Platform Support: Web

Stakeholder Reporting:

  • Primary Stakeholder: Engineering
  • Report Categories: Quality-Dashboard, Business-Rules-Coverage
  • Trend Tracking: Yes
  • Executive Visibility: No
  • Customer Impact Level: Critical

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Workflow Engine, Validation Service, Database
  • Performance Baseline: <1 second edit page load, <200ms validation response
  • Data Requirements: Existing workflow with email action configured

Prerequisites: Setup Requirements:

  • User logged in as CSO
  • Existing workflow with email action available
  • Edit permissions configured
  • Validation rules active

User Roles/Permissions: CSO manager, utility admin

Test Data:

  • Existing workflow with email channel
  • Updated subject: "Updated Welcome Message"
  • Updated CC: "newmanager@utility.com"
  • Updated BCC: "compliance@utility.com"

Prior Test Cases: UX03US04_TC_001 passed (workflow exists)

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Navigate to Active workflows

Active workflows displayed

N/A

Workflow list view

2

Click edit icon on workflow

Redirect to edit workflow page

N/A

NEW: Edit functionality

3

Navigate to Actions tab

Actions tab displays configured actions

N/A

Actions management

4

Locate existing email action

Email action displayed with configuration

N/A

Existing action identification

5

Attempt to change channel type

Channel type field is disabled/non-editable

N/A

NEW: Non-editable channel

6

Verify channel lock behavior

UI clearly indicates channel cannot be changed

N/A

NEW: Visual indication

7

Verify editable fields

Subject, content, CC/BCC can be modified

N/A

NEW: CC/BCC editable

8

Edit email subject

Subject field accepts changes

"Updated Welcome Message"

Content modification allowed

9

Edit CC field

CC field accepts address changes

"newmanager@utility.com"

NEW: CC editing

10

Edit BCC field

BCC field accepts modifications

"compliance@utility.com"

NEW: BCC editing

11

Try to add new channel type

Cannot convert email to SMS/WhatsApp

N/A

NEW: Channel type locked

12

Save changes

Modified content saved, channel type unchanged

N/A

Selective editing

13

Verify edit restrictions

Error message if channel change attempted

N/A

NEW: Error handling

Verification Points:

  • Primary Verification: Communication channel type cannot be edited in existing workflows
  • Secondary Verifications: Content and CC/BCC fields remain editable, proper error handling
  • Negative Verification: No option to change Email to SMS or other channel types



Test Case 4: View Workflow Execution History

Test Case ID: UX03US04_TC_004
Title: View detailed execution history with updated status format
Created By: Prachi
Created Date: 2025-05-28
Version: 1.0

Classification:

  • Module/Feature: Execution History
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags:

MOD-Communication, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Low, Business-High, Analytics-Dashboard, Execution-Tracking,HappyPath , API

Business Context:

  • Customer Segment: All
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Monitoring
  • Compliance Required: Yes
  • SLA Related: Yes

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: 70%
  • Integration Points: History Service, Database
  • Code Module Mapped: Communication
  • Requirement Coverage: REQ-HIST-001, REQ-ANAL-001, REQ-TRACK-001
  • Cross Platform Support: Web

Stakeholder Reporting:

  • Primary Stakeholder: Engineering
  • Report Categories: Quality-Dashboard, Analytics-Coverage
  • Trend Tracking: Yes
  • Executive Visibility: No
  • Customer Impact Level: High

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Analytics Engine, History Service, Database
  • Performance Baseline: <1 second history load, <500ms status update
  • Data Requirements: Executed workflows with history data

Prerequisites: Setup Requirements:

  • User logged in as Utility Admin
  • Workflows with execution history available
  • Analytics service running
  • History data populated

User Roles/Permissions: Utility Admin ,CSO manager

Test Data:

  • Workflows with completed executions
  • Sample status: "142 delivered 3 failed"
  • Mixed success scenarios available

Prior Test Cases: Workflow execution completed

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Navigate to Communication Workflows

Page loads successfully

N/A

Base navigation

2

Click "History" tab

History view opens

N/A

History tab access

3

Verify history table displayed

History table displayed successfully

N/A

Table rendering

4

Locate table fields

Table fields include workflow name, recipient type, recipient count, channel, run date, run time and status, action button

N/A

Find execution record

5

Verify status format

Status shows "x delivered y failed" format

"142 delivered 3 failed"

NEW: Status format

6

Click on action button

Detailed breakdown of delivery status

N/A

Expandable details

7

Verify individual message status

Each message shows delivery/failure status

Email: Delivered, SMS: Failed

Message-level tracking

8

Check failed execution

Failed workflow shows failure count

"0 delivered 5 failed"

Failure tracking

9

Verify completed status

Active execution shows completed status

"45 delivered 0 failed"

Success tracking

Verification Points:

  • Primary Verification: All fields display correct data with proper status format
  • Secondary Verifications: Action button expands details, individual message status visible
  • Negative Verification: No missing data or incorrect status calculations



Test Case 5: Workflow Performance Metrics

Test Case ID: UX03US04_TC_005
Title: Verify updated workflow performance metrics calculation and display
Created By: Prachi
Created Date: 2025-05-28
Version: 1.0

Classification:

  • Module/Feature: Performance Analytics
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags:

MOD-Communication, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-Critical, Performance-Metrics, Success-Rate-Calculation , performance

Business Context:

  • Customer Segment: All
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Analytics
  • Compliance Required: No
  • SLA Related: Yes

Quality Metrics:

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

Coverage Tracking:

  • Feature Coverage: 80%
  • Integration Points: Analytics Engine, Metrics Service, Database
  • Code Module Mapped: Communication
  • Requirement Coverage: REQ-PERF-001, REQ-CALC-001, REQ-METR-001
  • Cross Platform Support: Web

Stakeholder Reporting:

  • Primary Stakeholder: Engineering
  • Report Categories: Quality-Dashboard, Performance-Metrics, Analytics-Coverage
  • Trend Tracking: Yes
  • Executive Visibility: Yes
  • Customer Impact Level: Critical

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Analytics Engine, Calculation Service, Database
  • Performance Baseline: <500ms metrics calculation, <1 second display update
  • Data Requirements: Workflows with execution history and metrics data

Prerequisites: Setup Requirements:

  • User logged in as Utility Admin
  • Workflows with execution history
  • Analytics calculations up to date
  • Performance data available

User Roles/Permissions: Utility Admin role with analytics access

Test Data:

  • Workflow: "New Customer Welcome" (245 triggered, 240 completed)
  • Expected Success Rate: 98.0%
  • Mixed success workflow: (100 triggered, 85 completed, 85% success rate)

Prior Test Cases: Workflows executed with history available

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Navigate to Active workflows

Workflows displayed with metrics

N/A

Metrics visibility

2

Locate workflow with history

Target workflow card visible

"New Customer Welcome"

Target identification

3

Verify "Triggered" definition

NEW: Count of times workflow is used

Triggered: 245

UPDATED: Usage count

4

Verify "Completed" definition

NEW: Count of notifications successfully delivered

Completed: 240

UPDATED: Delivery count

5

Verify Success Rate calculation

NEW: (delivered notifications / total notifications) * 100

Success Rate: 98.0%

UPDATED: Formula

6

Calculate manual verification

Manual: (240/245) * 100 = 97.96% ≈ 98.0%

N/A

NEW: Calculation verification

7

Check workflow with failures

Workflow with failed notifications

Triggered: 100, Completed: 85

Mixed success scenario

8

Verify failure impact on success rate

Success rate reflects delivery success only

Success Rate: 85.0%

NEW: Delivery-based calculation

9

Check draft workflow metrics

Draft workflows show zero metrics

Triggered: 0, Completed: 0

Draft state handling

10

Check real-time metrics update

Metrics update after new executions

N/A

NEW: Real-time updates

Verification Points:

  • Primary Verification: Updated metrics definitions correctly implemented and calculated
  • Secondary Verifications: Success rate based on notification delivery, triggered count reflects usage
  • Negative Verification: Calculation should not be incorrect, draft workflows show zeros



Test Case 6: Workflow CRUD API Operations

Test Case ID: UX03US04_TC_006
Title: Test complete CRUD operations for workflows via API
Created By: Prachi
Created Date: 2025-05-28
Version: 1.0

Classification:

  • Module/Feature: Workflow API
  • Test Type: API
  • Test Level: Integration
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags:

MOD-Communication, P1-Critical, Phase-Regression, Type-API, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical, API-Integration, CRUD-Operations,API

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature Coverage: 90%
  • Integration Points: REST API, Database, Authentication Service
  • Code Module Mapped: API Controller Module, CRUD Service Module
  • Requirement Coverage: REQ-API-001, REQ-CRUD-001, REQ-AUTH-002
  • Cross Platform Support: API

Stakeholder Reporting:

  • Primary Stakeholder: Engineering
  • Report Categories: API-Quality-Dashboard, Integration-Coverage
  • Trend Tracking: Yes
  • Executive Visibility: No
  • Customer Impact Level: Critical

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: API Testing Tool (Postman/Newman)
  • Device/OS: Windows 10/11, macOS 12+, Linux
  • Screen Resolution: N/A
  • Dependencies: REST API, Database, Authentication Service
  • Performance Baseline: <500ms API response, <200ms database operations
  • Data Requirements: Valid API tokens, Test workflow JSON data

Prerequisites: Setup Requirements:

  • API endpoints accessible
  • Valid authentication tokens
  • Database in clean state
  • API testing tool configured

User Roles/Permissions: API access with workflow management permissions

Test Data:

  • Valid workflow JSON payload
  • API authentication token
  • Test workflow ID for operations
  • Modified workflow data for updates

Prior Test Cases: Authentication API verified

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

POST /api/workflows

Create workflow successfully

Valid workflow JSON

Create operation

2

Verify response structure

Proper JSON with workflow ID

N/A

Response validation

3

GET /api/workflows

Retrieve all workflows

N/A

Read operation

4

GET /api/workflows/{id}

Retrieve specific workflow

Created workflow ID

Specific read

5

PUT /api/workflows/{id}

Update workflow configuration

Modified workflow data

Update operation

6

Verify update persistence

Changes reflected in GET

N/A

Update verification

7

DELETE /api/workflows/{id}

Delete workflow

Workflow ID

Delete operation

8

Verify deletion

GET returns 404

N/A

Deletion verification

9

Test error scenarios

Invalid data returns errors

Invalid JSON

Error handling

10

Verify status codes

Correct HTTP codes returned

N/A

Status validation

Verification Points:

  • Primary Verification: All CRUD operations function correctly via API
  • Secondary Verifications: Proper error handling, correct status codes
  • Negative Verification: Invalid operations properly rejected



Test Case 7: Maximum Actions Limit Enforcement

Test Case ID: UX03US04_TC_007
Title: Verify workflow cannot exceed maximum of 10 actions per workflow
Created By: Prachi
Created Date: 2025-05-28
Version: 1.0

Classification:

  • Module/Feature: Workflow Limits
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags: MOD-Communication, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Boundary-Testing, Limit-Enforcement ,API

Business Context:

  • Customer Segment: All
  • Revenue Impact: Medium
  • Business Priority: Should-Have
  • Customer Journey: Configuration
  • Compliance Required: No
  • SLA Related: No

Quality Metrics:

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

Coverage Tracking:

  • Feature Coverage: 30%
  • Integration Points: Workflow Engine, Validation Service
  • Code Module Mapped: Validation Module, Limit Enforcement Module
  • Requirement Coverage: REQ-LIMIT-001, REQ-VAL-002
  • Cross Platform Support: Web

Stakeholder Reporting:

  • Primary Stakeholder: QA
  • Report Categories: Quality-Dashboard, Boundary-Testing-Results
  • Trend Tracking: No
  • Executive Visibility: No
  • Customer Impact Level: Medium

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Workflow Engine, Validation Service
  • Performance Baseline: <100ms validation response
  • Data Requirements: Workflow in progress, Various action types available

Prerequisites: Setup Requirements:

  • User logged in as Utility Admin
  • Workflow creation in progress
  • All communication channels available
  • Validation rules active

User Roles/Permissions: Utility Admin role with workflow creation access

Test Data:

  • Various channel types: Email, SMS, WhatsApp, In-app
  • 10+ action configurations ready
  • Duplicate action scenarios

Prior Test Cases: Workflow creation process initiated

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Add 9 actions to workflow

All 9 actions added successfully

Various channel types

Approaching limit

2

Add 10th action

10th action added, maximum reached

Email action

NEW: Maximum limit reached

3

Attempt to add 11th action

Error: "Maximum of 10 actions allowed per workflow"

SMS action

NEW: Limit enforcement

4

Verify "Add Action" button state

Button disabled or shows limit message

N/A

NEW: UI limit indication

5

Try to duplicate existing action

Still counts toward 10-action limit

Duplicate email

NEW: Duplication counting

6

Remove one action

"Add Action" button becomes available again

N/A

NEW: Dynamic limit management

7

Add action after removal

Can add action when under limit

WhatsApp action

NEW: Limit management

Verification Points:

  • Primary Verification: Maximum 10 actions per workflow strictly enforced
  • Secondary Verifications: Clear error messaging, UI updates dynamically
  • Negative Verification: Cannot exceed limit under any circumstances



Test Case 8: View Button Functionality

Test Case ID: UX03US04_TC_008
Title: Verify distinct behavior of View button on workflow cards
Created By: Prachi
Created Date: 2025-05-28
Version: 1.0

Classification:

  • Module/Feature: Workflow Management
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags: MOD-Communication, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Low, Business-Critical, Navigation-Testing, Read-Only-Access , HappyFlow

Business Context:

  • Customer Segment: All
  • Revenue Impact: Medium
  • Business Priority: Must-Have
  • Customer Journey: Daily-Usage
  • Compliance Required: No
  • SLA Related: No

Quality Metrics:

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

Coverage Tracking:

  • Feature Coverage: 40%
  • Integration Points: UI Navigation, Workflow Engine
  • Code Module Mapped: Navigation Module, View Controller
  • Requirement Coverage: REQ-NAV-001, REQ-VIEW-001
  • Cross Platform Support: Web

Stakeholder Reporting:

  • Primary Stakeholder: Engineering
  • Report Categories: Quality-Dashboard, UI-Navigation-Coverage
  • Trend Tracking: No
  • Executive Visibility: No
  • Customer Impact Level: Medium

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: UI Framework, Workflow Engine
  • Performance Baseline: <500ms page navigation
  • Data Requirements: Existing workflows with View and Edit buttons

Prerequisites: Setup Requirements:

  • User logged in as Utility Admin
  • Existing workflows available
  • UI navigation functional
  • View permissions configured

User Roles/Permissions: Utility Admin role with view access

Test Data:

  • Existing workflow with both View and Edit buttons
  • Workflow configuration data for verification

Prior Test Cases: Workflow exists and is accessible

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Locate workflow with view buttons

View buttons visible on workflow card

N/A

NEW: Button identification

2

Click "View" button

NEW: Navigate to Details page (read-only)

N/A

NEW: View functionality

3

Verify Details page content

Workflow details displayed in read-only format

N/A

NEW: Read-only verification

4

Verify no edit capabilities

No Save/Edit buttons available in Details view

N/A

NEW: Read-only enforcement

5

Navigate back to workflows list

Return to main workflows page

N/A

NEW: Navigation back


Verification Points:

  • Primary Verification: View button → Details page (read-only), Edit button → Actions page (editable)
  • Secondary Verifications: Distinct navigation paths, appropriate permissions enforcement
  • Negative Verification: View mode doesn't allow editing, Edit mode properly functional



Test Case 9: Workflow Status Toggle with Dependency Check

Test Case ID: UX03US04_TC_009
Title: Verify workflow status toggle shows usage dependencies and impact before allowing deactivation
Created By: Prachi
Created Date: 2025-05-28
Version: 1.0

Classification:

  • Module/Feature: Workflow Management
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Security
  • Automation Status: Manual

Enhanced Tags: MOD-Communication, P1-Critical, Phase-Security, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Dependency-Checking, Status-Management , API

Business Context:

  • Customer Segment: All
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Daily-Usage
  • Compliance Required: Yes
  • SLA Related: Yes

Quality Metrics:

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

Coverage Tracking:

  • Feature Coverage: 50%
  • Integration Points: Workflow Engine, Dependency Service, Status Manager
  • Code Module Mapped: Status Toggle Module, Dependency Check Module
  • Requirement Coverage: REQ-STAT-001, REQ-DEP-001, REQ-SAFE-001
  • Cross Platform Support: Web

Stakeholder Reporting:

  • Primary Stakeholder: Engineering
  • Report Categories: Quality-Dashboard, Security-Coverage, Dependency-Analysis
  • Trend Tracking: Yes
  • Executive Visibility: Yes
  • Customer Impact Level: Critical

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Workflow Engine, Dependency Service, Template Service
  • Performance Baseline: <1 second dependency check, <500ms status update
  • Data Requirements: Active workflows with dependencies, Unused workflows

Prerequisites: Setup Requirements:

  • User logged in as Utility Admin
  • Active workflows with dependencies
  • Unused workflows for comparison
  • Dependency tracking active

User Roles/Permissions: Utility Admin role with workflow management access

Test Data:

  • Active workflow with dependencies: "Used in 3 templates, affects 150 customers"
  • Unused workflow for clean toggle testing
  • Expected warning: "This will stop all scheduled executions"

Prior Test Cases: Workflows with usage dependencies exist

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Locate active workflow with toggle button

Toggle button shows "Active" status

Active workflow with usage

NEW: Toggle button identification

2

Click toggle to deactivate workflow

System shows dependency check dialog

N/A

NEW: Dependency checking on toggle

3

Review dependency information

Shows "Used in X places" with impact details

"Used in 3 templates, affects 150 customers"

NEW: Usage impact tracking

4

View specific usage locations

List of templates/processes using workflow

Template names and customer counts

NEW: Detailed dependencies

5

Confirm deactivation despite dependencies

Require explicit confirmation with warning

"This will stop all scheduled executions"

NEW: Impact confirmation required

6

Verify workflow status change

Workflow status changes to "Inactive"

Status: Active → Inactive

NEW: Status toggle verification

7

Test reactivation of workflow

Toggle back to "Active" status

N/A

NEW: Reactivation capability

8

Test toggle of unused workflow

Direct toggle without dependency warning

Unused workflow

NEW: Clean toggle for unused

9

Verify dependent process impact

Dependent processes show workflow as inactive

Scheduled executions stopped


Verification Points:

  • Primary Verification: Toggle process shows all usage dependencies and impact before allowing status change
  • Secondary Verifications: Clear impact warning, explicit confirmation required, status changes properly reflected
  • Negative Verification: Cannot accidentally deactivate workflows with dependencies without proper warning



Test Case 10: Variable Data Accuracy Validation

Test Case ID: UX03US04_TC_010
Title: Verify all placeholder variables are replaced with accurate customer data across all channels
Created By: Prachi
Created Date: 2025-05-28
Version: 1.0

Classification:

  • Module/Feature: Variable Processing Engine
  • Test Type: Functional
  • Test Level: Integration
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags: MOD-Communication, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-CRM-CustomerData, Variable-Replacement-Engine,Database

Business Context:

  • Customer Segment: All
  • Revenue Impact: High
  • Business Priority: Must-Have
  • Customer Journey: Daily-Usage
  • Compliance Required: Yes
  • SLA Related: Yes

Quality Metrics:

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

Coverage Tracking:

  • Feature Coverage: 85%
  • Integration Points: Variable Engine, Customer Database, Billing System
  • Code Module Mapped: Variable Processing Module, Data Integration Module
  • Requirement Coverage: REQ-VAR-001, REQ-DATA-001, REQ-PERS-001
  • Cross Platform Support: Web, Email, SMS, WhatsApp

Stakeholder Reporting:

  • Primary Stakeholder: Engineering
  • Report Categories: Quality-Dashboard, Data-Integration-Coverage, Personalization-Metrics
  • Trend Tracking: Yes
  • Executive Visibility: No
  • Customer Impact Level: Critical

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Variable Engine, Customer Database, Billing System
  • Performance Baseline: <200ms variable replacement, <500ms data lookup
  • Data Requirements: Test customer data with all variable types

Prerequisites: Setup Requirements:

  • User logged in as Utility Admin
  • Customer database populated with test data
  • Billing system integration active
  • Variable engine configured
  • All communication channels available

User Roles/Permissions: Utility Admin role with data access permissions

Test Data: test_customer: first_name: "John" last_name: "Smith" email: "john.smith@utilitytest.com" phone: "+1-555-123-4567" account_number: "ACC-789456" bill_amount: "$125.50" due_date: "2024-12-15" service_address: "123 Main St, Anytown, ST 12345" Special character test: "José O'Brien"

Prior Test Cases: Customer data integration verified

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Create workflow with customer variables

Variable picker shows all available placeholders

[Customer.FirstName], [Customer.LastName], [Customer.Email]

Basic customer variables

2

Add billing variables to email template

Billing placeholders available

[Bill.Amount], [Bill.DueDate]

Financial data variables

3

Include service variables in message

Service placeholders functional

[Service.Address], [Account.Number]

Service-related data

4

Configure multi-channel workflow

All channels support variable replacement

Email, SMS, WhatsApp

Cross-channel consistency

5

Execute workflow for test customer

All variables replaced with actual data

Customer: John Smith

Data replacement verification

6

Verify email content accuracy

Email shows "Dear John Smith, Your bill of $125.50..."

N/A

Email variable accuracy

7

Check SMS message content

SMS contains actual data: "ACC-789456 bill due 2024-12-15"

N/A

SMS variable accuracy

8

Validate WhatsApp message

WhatsApp shows complete address and amount

N/A

WhatsApp variable accuracy

9

Test with special characters

Variables handle names with apostrophes, accents

Customer: "José O'Brien"

Special character handling

10

Verify variable case sensitivity

[customer.firstname] vs [Customer.FirstName] handling

Mixed case variables

Case handling verification


Verification Points:

  • Primary Verification: All placeholder variables correctly replaced with actual customer data
  • Secondary Verifications: No placeholder syntax visible in final messages, special characters handled correctly
  • Negative Verification: No system errors or null values displayed to customers



Test Case 11: Missing Data Graceful Handling

Test Case ID: UX03US04_TC_011
Title: Verify system handles missing or null variable data with graceful fallback behavior
Created By: Prachi
Created Date: 2025-05-28
Version: 1.0

Classification:

  • Module/Feature: Data Validation & Error Handling
  • Test Type: Functional
  • Test Level: Integration
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags: MOD-Communication, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-High, Revenue-Impact-Medium, Integration-ErrorHandling, Data-Fallback-Mechanism

Business Context:

  • Customer Segment: All
  • Revenue Impact: Medium
  • Business Priority: Must-Have
  • Customer Journey: Daily-Usage
  • Compliance Required: Yes
  • SLA Related: No

Quality Metrics:

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

Coverage Tracking:

  • Feature Coverage: 70%
  • Integration Points: Variable Engine, Error Handler, Customer Database
  • Code Module Mapped: Error Handling Module, Fallback Mechanism Module
  • Requirement Coverage: REQ-ERR-001, REQ-FALL-001, REQ-CONT-001
  • Cross Platform Support: Web, Email, SMS, WhatsApp

Stakeholder Reporting:

  • Primary Stakeholder: Engineering
  • Report Categories: Quality-Dashboard, Error-Handling-Coverage, Data-Quality-Metrics
  • Trend Tracking: Yes
  • Executive Visibility: No
  • Customer Impact Level: High

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen Resolution: Desktop-1920x1080
  • Dependencies: Variable Engine, Error Handler, Customer Database
  • Performance Baseline: <300ms fallback processing, <1 second execution continuation
  • Data Requirements: Customer records with missing data fields

Prerequisites: Setup Requirements:

  • User logged in as Utility Admin
  • Customer database with missing data scenarios
  • Error handling configured
  • Fallback mechanisms active
  • Workflow execution enabled

User Roles/Permissions: Utility Admin role with workflow execution access

Test Data:

  • Customer with missing first_name: NULL
  • Customer with missing bill_amount: NULL
  • Customer with missing account_number: NULL
  • Customer with missing middle_name: NULL
  • Multiple missing fields scenario

Prior Test Cases: Variable processing system verified

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Create customer with missing first name

Customer record with null first_name

first_name: NULL

Missing required field

2

Execute workflow with [Customer.FirstName]

Default text: "Dear Customer" or skip personalization

N/A

Graceful fallback

3

Test missing billing amount

Shows "Amount pending" or equivalent

bill_amount: NULL

Financial data missing

4

Handle missing account number

Generic reference or skip field

account_number: NULL

Critical field missing

5

Test optional field missing

Field gracefully omitted from message

middle_name: NULL

Optional data handling

6

Verify workflow continues execution

Workflow completes despite missing data

N/A

Execution continuity

7

Test multiple missing fields

System handles compound null values

Multiple NULLs

Complex missing data

8

Verify customer experience

No error messages visible to end customer

N/A


Verification Points:

  • Primary Verification: Workflows execute successfully despite missing variable data
  • Secondary Verifications: Appropriate fallback text used, admin notifications sent
  • Negative Verification: No error messages or null values displayed to customers



Test Case 12: Email Deliverability and Inbox Placement

Test Case ID: UX03US04_TC_012
Title: Verify emails are delivered to inbox (not spam) with proper authentication headers
Created By: Prachi
Created Date: 2025-05-28
Version: 1.0

Classification:

  • Module/Feature: Email Delivery Service
  • Test Type: Integration
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Integration
  • Automation Status: Manual

Back to top