Skip to main content

Communication Workflows (UX03US04)

Communication Workflows - Updated Comprehensive Test Cases

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: Create New Workflow - Happy Path

Test Case ID: UX03US04_TC_001
Title: Successfully create a new communication workflow with all required fields
Priority: P1-Critical
Test Type: Functional
Module: Communication Workflows

Tags: MOD-Workflows, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Low, Business-Critical, Revenue-Impact-High

Business Context:

  • Customer_Segment: All
  • Revenue_Impact: High
  • Business_Priority: Must-Have
  • Customer_Journey: Daily-Usage
  • Compliance_Required: No
  • SLA_Related: Yes

Quality Metrics:

  • Risk_Level: Low
  • Complexity_Level: Medium
  • Expected_Execution_Time: 5 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Medium
  • Failure_Impact: Critical

Prerequisites:

  • User logged in as Utility Admin
  • Browser: Chrome 115+
  • Environment: Staging
  • Test data: Valid workflow configuration data
  • Required permissions: Workflow creation access

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Communication Workflows page

Workflows page loads with Active tab selected

N/A

Verify page header and navigation

2

Click "New Workflow" button

Create New Workflow modal opens with Details step active

N/A

Modal should show 3-step wizard

3

Enter Workflow Name

Field accepts input, no validation errors

"Customer Onboarding Sequence"

Min 3 characters required

4

Enter Description

Field accepts input, character count updates

"Automated welcome messages for new customers"

Min 5 characters required

5

Select Audience Type

Dropdown shows Consumer, Technician, Business User options

Select "Consumer"

Single selection required

6

Click "Next" button

Navigate to Trigger step, step 2 becomes active

N/A

Button enabled only when required fields filled

7

Select "Event-Based" trigger type

Event-Based option selected, Event Type dropdown appears

N/A

Radio button selection

8

Select Event Type

Dropdown shows system events

Select "NSC-Created"

System event selection

9

Click "Next" button

Navigate to Actions step, step 3 becomes active

N/A

Trigger configuration saved

10

Click "Add First Action"

Communication channel selection appears

N/A

Action configuration panel opens

11

Select Email channel

Email selected, message source options appear

N/A

Channel-specific options displayed

12

Click "Create New Message"

Message composition fields appear

N/A

Toggle between template/new message

13

Enter email subject

Subject field accepts input

"Welcome to UtilityConnect!"

Required field for email

14

Enter email content

Message body accepts rich text input

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

Support for variables/placeholders

15

Click "Add Action"

Action added to workflow, action summary displayed

N/A

Action configuration saved

16

Click "Create Workflow"

Workflow created successfully, redirect to workflows list

N/A

Success confirmation message

17

Verify workflow in Active tab

New workflow appears in Active workflows list with correct details

N/A

Status should be "Active"

Verification Points:

  • Primary_Verification: Workflow appears in Active tab with correct configuration
  • Secondary_Verifications: All entered data preserved, workflow metrics initialized (0 triggered, 0 completed)
  • Negative_Verification: Workflow does not appear in Draft or History tabs

Test Case 2: Create Workflow with Time-Based Trigger and Target List

Test Case ID: UX03US04_TC_002
Title: Create workflow with specific date/time trigger and target list selection
Priority: P1-Critical
Test Type: Functional
Module: Communication Workflows

Tags: MOD-Workflows, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-High

Prerequisites:

  • User logged in as Customer Service Manager
  • Target lists available in system
  • Future date/time available for selection

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

Start workflow creation

3

Enter workflow name

Field accepts input

"Reengagement Campaign"

Unique workflow name

4

Enter description

Field accepts input

"Re-engage users who haven't logged in for 30+ days"

Workflow purpose

5

Select "Consumer" audience type

Consumer option selected

N/A

Audience targeting

6

Click "Next" to configure trigger

Navigate to Trigger step

N/A

Proceed to trigger configuration

7

Select "Time-Based" trigger type

Time-Based option selected, sub-options appear

N/A

Trigger type selection

8

Select "Specific Date and Time"

Date and Time input fields appear

N/A

Time-based sub-option

9

Select Target List

Target list dropdown appears and shows available lists

Select "Inactive Users"

NEW: Target list in trigger step

10

Set date for campaign

Date picker opens, future date selectable

Tomorrow's date

Must be future date

11

Set time for campaign

Time picker allows time selection

"10:00:00"

24-hour format

12

Click "Next" to configure actions

Navigate to Actions step

N/A

Trigger with target list saved

13

Add email action

Select Email channel, create message

Subject: "We Miss You!"

First communication

14

Add SMS follow-up

Select SMS, set 2-day delay

"Check your email for offers"

Multi-channel sequence

15

Create workflow

Workflow created with time-based trigger and target list

N/A

Complete creation

16

Verify target list integration

Workflow shows target list in configuration

N/A

Target list properly saved

Verification Points:

  • Primary_Verification: Time-based workflow created with target list selection in trigger step
  • Secondary_Verifications: Target list properly integrated, specific date/time configured correctly
  • Negative_Verification: Target list not available in Details step (moved to Trigger step)

Test Case 3: Create Workflow with Specific Date and Time (Modified)

Test Case ID: UX03US04_TC_003
Title: Configure workflow with specific date and time trigger (Recurring events removed)
Priority: P2-High
Test Type: Functional
Module: Communication Workflows

Tags: MOD-Workflows, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High

Prerequisites:

  • User logged in as Billing Manager
  • Valid workflow details configured
  • Note: Recurring Event option removed from 2nd stepper

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Communication Workflows page

Page loads successfully

N/A

Base navigation

2

Click "New Workflow" button

Create workflow modal opens

N/A

Start creation process

3

Enter workflow details

Name and description accepted

"Payment Due Reminder"

Workflow identification

4

Select audience type

Consumer audience selected

N/A

Audience targeting

5

Click "Next" to configure trigger

Navigate to Trigger step

N/A

Proceed to triggers

6

Verify Time-Based options

Only "Specific Date and Time" option available

N/A

UPDATED: No Recurring Event option

7

Select "Time-Based" trigger

Time-Based trigger selected

N/A

Trigger type selection

8

Verify no recurring option

Recurring Event option not displayed

N/A

CONFIRMED: Recurring removed

9

Select specific date

Date picker allows future date selection

"2024-12-25"

Christmas campaign date

10

Select specific time

Time picker allows time selection

"09:00:00"

Morning execution time

11

Configure target list

Select target list for specific audience

"High Usage Consumers"

Targeted audience

12

Click "Next" for actions

Navigate to Actions configuration

N/A

Trigger configuration complete

13

Add SMS action

Configure SMS with character limit

"Your payment is due..."

SMS communication

14

Complete workflow creation

Workflow created with specific date/time only

N/A

No recurring functionality

Verification Points:

  • Primary_Verification: Only "Specific Date and Time" option available in Time-Based triggers
  • Secondary_Verifications: No recurring event configuration, specific date/time works correctly
  • Negative_Verification: Recurring Event option completely removed from interface

Test Case 4: Add Multiple Communication Channels with CC/BCC

Test Case ID: UX03US04_TC_004
Title: Configure workflow with multiple communication channels and enhanced email options
Priority: P1-Critical
Test Type: Functional
Module: Communication Actions

Tags: MOD-Actions, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-Medium, Business-Critical

Prerequisites:

  • User logged in as Customer Service Manager
  • Workflow Details and Trigger configured
  • Multiple channel templates available

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Actions step

Communication Actions page displays

N/A

Ready for action configuration

2

Click "Add First Action"

Channel selection appears

N/A

Action configuration starts

3

Select Email channel

Email configuration appears

N/A

First channel selection

4

Click "Create New Message"

Email composer with enhanced fields

N/A

NEW: Enhanced email options

5

Enter CC field

CC field accepts multiple email addresses

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

NEW: CC functionality

6

Enter BCC field

BCC field accepts email addresses

"audit@utility.com"

NEW: BCC functionality

7

Enter email subject

Subject field accepts input

"Multi-Channel Customer Outreach"

Email subject

8

Enter email content

Rich text message body

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

Rich content with variables

9

Set timing

Select "Immediately"

N/A

No delay for first action

10

Click "Add Action"

Email action with CC/BCC added

N/A

NEW: CC/BCC preserved

11

Add SMS action

Select SMS channel

N/A

Second channel

12

Configure SMS content

SMS with character limit

"Welcome! Check your email for details."

SMS message

13

Set SMS delay

Configure delay after email

"2 days"

Sequential timing

14

Add WhatsApp action

Select WhatsApp channel

N/A

Third channel

15

Configure WhatsApp message

WhatsApp content with formatting

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

WhatsApp formatting

16

Set WhatsApp delay

Configure delay after SMS

"1 day"

Sequential workflow

17

Review action sequence

All actions with proper timing displayed

N/A

Multi-channel validation

18

Create workflow

Workflow created with enhanced email options

N/A

Complete creation

Verification Points:

  • Primary_Verification: CC/BCC fields function correctly in email actions
  • Secondary_Verifications: Multi-channel sequence works, timing delays configured properly
  • Negative_Verification: CC/BCC validation prevents invalid email addresses

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

Test Case ID: UX03US04_TC_005
Title: Verify communication channel type cannot be edited in existing workflows
Priority: P1-Critical
Test Type: Functional
Module: Workflow Management

Tags: MOD-Management, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-Critical

Prerequisites:

  • Existing workflow with configured actions
  • User has edit permissions
  • Workflow in Active state

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 Suite: Workflow History & Analytics

Test Case 6: View Workflow Execution History (Updated Format)

Test Case ID: UX03US04_TC_006
Title: View detailed execution history with updated status format
Priority: P1-Critical
Test Type: Functional
Module: Execution History

Tags: MOD-History, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Low, Business-High

Prerequisites:

  • Workflows executed with various outcomes
  • History data available
  • New status format implemented

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 workflow name display

NEW: No icon before workflow name

N/A

UPDATED: Icons removed

4

Locate completed execution

Workflow execution with updated status format

N/A

Find execution record

5

Verify status format

Status shows "x delivered y failed" format

"142 delivered 3 failed"

NEW: Status format

6

Expand execution details

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 in-progress status

Active execution shows current progress

"45 delivered 0 failed (In Progress)"

NEW: Progress format

10

Verify action button presence

NEW: Action button visible but non-functional

N/A

NEW: Placeholder button

11

Click action button

Button present but performs no action

N/A

NEW: Non-functional by design

12

Verify button tooltip/indication

Button indicates future functionality

"Coming Soon"

NEW: Future feature indicator

Verification Points:

  • Primary_Verification: Status format shows "x delivered y failed" instead of generic status
  • Secondary_Verifications: Icons removed from workflow names, action button present but non-functional
  • Negative_Verification: No old status format displayed, action button doesn't trigger actions

Test Case 7: Workflow Performance Metrics (Updated Calculations)

Test Case ID: UX03US04_TC_007
Title: Verify updated workflow performance metrics calculation and display
Priority: P1-Critical
Test Type: Functional
Module: Performance Analytics

Tags: MOD-Analytics, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-Critical

Prerequisites:

  • Workflows with execution history
  • Updated metrics definitions implemented
  • Various success/failure scenarios

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

Verify metrics in workflow edit

Detailed metrics in edit page

N/A

Extended metrics view

11

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: Old metrics calculation methods not used

Test Suite: Data Validation & Error Handling

Test Case 8: Character Limits Validation (Placeholder)

Test Case ID: UX03US04_TC_008
Title: Validate character limits for different communication channels
Priority: P2-High
Test Type: Functional
Module: Channel Validation

Tags: MOD-Validation, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium

Prerequisites:

  • Character limits defined per channel (TBD)
  • Action configuration interface available

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Select SMS channel

SMS configuration with character counter

N/A

SMS channel selection

2

Enter text approaching limit

Character counter shows remaining characters

TBD: SMS limit

PENDING: Limit definition

3

Verify counter accuracy

Counter reflects actual character count

N/A

PENDING: Exact validation

4

Attempt to exceed limit

System prevents or warns about excess

TBD: Limit + 1 chars

PENDING: Enforcement method

5

Test WhatsApp limits

WhatsApp-specific character restrictions

TBD: WhatsApp limit

PENDING: WhatsApp definition

6

Verify Email handling

Email channel character behavior

N/A

PENDING: Email restrictions

7

Test variable impact

Variables counted in character limits

"[Customer.FirstName]"

PENDING: Variable handling

Verification Points:

  • Primary_Verification: Character limits enforced per channel specifications
  • Note: This test case requires character limit definitions to be completed

Test Suite: Cross-Platform Compatibility (Desktop Only)

Test Case 9: Desktop Browser Compatibility

Test Case ID: UX03US04_TC_009
Title: Verify workflow functionality across desktop browsers only
Priority: P2-High
Test Type: Compatibility
Module: Cross-Browser

Tags: MOD-Compatibility, P2-High, Phase-Regression, Type-Compatibility, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium

Prerequisites:

  • Access to Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • NOTE: Mobile testing removed as requested

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Test in Chrome Desktop

Complete workflow creation successfully

Standard test data

Chrome compatibility

2

Verify Chrome UI elements

All buttons, forms, modals render correctly

N/A

Chrome UI consistency

3

Test in Firefox Desktop

Same functionality works in Firefox

Same test data

Firefox compatibility

4

Compare Firefox UI

UI consistent with Chrome version

N/A

Cross-browser consistency

5

Test in Safari Desktop

All features function in Safari

Same test data

Safari compatibility

6

Verify Safari-specific elements

Date/time pickers work correctly

N/A

Safari UI components

7

Test in Edge Desktop

Complete workflow operations in Edge

Same test data

Edge compatibility

8

Document browser differences

Note any browser-specific behaviors

N/A

REMOVED: Mobile testing

Verification Points:

  • Primary_Verification: Core functionality consistent across desktop browsers only
  • Secondary_Verifications: UI renders correctly, no JavaScript errors
  • Negative_Verification: No mobile compatibility testing required

Test Suite: API Testing

Test Case 10: Workflow CRUD API Operations

Test Case ID: UX03US04_TC_010
Title: Test complete CRUD operations for workflows via API
Priority: P1-Critical
Test Type: API
Module: Workflow API

Tags: MOD-API, P1-Critical, Phase-Regression, Type-API, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical

Prerequisites:

  • API endpoints accessible
  • Authentication configured
  • Test data prepared

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 11: Form Validation Error Messages

Test Case ID: UX03US04_TC_011
Title: Verify comprehensive form validation and error messaging throughout workflow creation
Priority: P2-High
Test Type: Functional
Module: Data Validation

Tags: MOD-Validation, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium

Prerequisites:

  • Workflow creation page accessible
  • Various invalid input scenarios prepared

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Leave workflow name empty

Error: "Workflow name is required"

"" (empty)

NEW: Required field validation

2

Leave email subject empty

Error: "Subject is required for email messages"

"" (empty)

NEW: Email subject validation

3

Leave email content empty

Error: "Message content cannot be empty"

"" (empty)

NEW: Message content validation

4

Enter duplicate workflow name

Error: "Workflow name already exists"

"Existing Workflow Name"

NEW: Uniqueness validation

5

Enter invalid email in CC field

Error: "Please enter valid email addresses"

"invalid-email"

NEW: CC field validation

6

Enter malformed BCC addresses

Error: "BCC field contains invalid email format"

"test@,invalid"

NEW: BCC field validation

7

Exceed SMS character limit

Warning: "Message exceeds 160 character limit"

161+ characters

NEW: SMS limit warning

8

Exceed WhatsApp limit

Warning: "Message exceeds 1024 character limit"

1025+ characters

NEW: WhatsApp limit warning

9

Try to save incomplete workflow

Error: "Please complete all required fields"

N/A

NEW: Completion validation

10

Test special characters in name

Accept special characters appropriately

"Test-Workflow_2024"

NEW: Special character handling

Verification Points:

  • Primary_Verification: All form fields have appropriate validation with clear error messages
  • Secondary_Verifications: Error messages are user-friendly and actionable
  • Negative_Verification: Invalid data properly rejected with helpful guidance




Test Case 12: Maximum Actions Limit Enforcement

Test Case ID: UX03US04_TC_012
Title: Verify workflow cannot exceed maximum of 10 actions per workflow
Priority: P2-High
Test Type: Functional
Module: Workflow Limits

Tags: MOD-Limits, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium

Prerequisites:

  • Workflow creation in Actions step
  • Ability to add multiple actions

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 13: View vs Edit Button Functionality

Test Case ID: UX03US04_TC_013
Title: Verify distinct behavior of View and Edit buttons on workflow cards
Priority: P1-Critical
Test Type: Functional
Module: Workflow Management

Tags: MOD-Management, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Low, Business-Critical

Prerequisites:

  • Existing workflows with both View and Edit buttons
  • User has appropriate permissions

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Locate workflow with both buttons

View and Edit 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

6

Click "Edit" button on same workflow

NEW: Navigate to Actions page (editable)

N/A

NEW: Edit functionality

7

Verify Actions page access

Actions tab active with edit capabilities

N/A

NEW: Edit mode verification

8

Verify edit functionality available

Save Changes button present and functional

N/A

NEW: Edit capabilities

9

Test tab navigation in edit mode

Can navigate between Details, Trigger, Actions, Preview

N/A

NEW: Edit mode navigation

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 14: Workflow Deletion with Dependency Check

Test Case ID: UX03US04_TC_014
Title: Verify workflow deletion shows usage dependencies before allowing deletion
Priority: P1-Critical
Test Type: Functional
Module: Workflow Management

Tags: MOD-Management, P1-Critical, Phase-Security, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical

Prerequisites:

  • Workflow used in multiple places/templates
  • Delete functionality available

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Attempt to delete active workflow

NEW: System shows dependency check dialog

Active workflow with usage

NEW: Dependency checking

2

Review dependency information

NEW: Shows "Used in X places" with details

N/A

NEW: Usage tracking

3

View specific usage locations

NEW: List of templates/processes using workflow

N/A

NEW: Detailed dependencies

4

Confirm deletion despite dependencies

NEW: Require explicit confirmation

N/A

NEW: Confirmation required

5

Test deletion of unused workflow

NEW: Direct deletion without dependency warning

Unused workflow

NEW: Clean deletion

6

Verify deletion impact

NEW: Dependent processes show broken references

N/A

NEW: Impact verification

7

Test cancellation of deletion

NEW: Cancel preserves workflow and dependencies

N/A

NEW: Cancellation handling

Verification Points:

  • Primary_Verification: Deletion process shows all usage dependencies before allowing deletion
  • Secondary_Verifications: Clear impact warning, explicit confirmation required
  • Negative_Verification: Cannot accidentally delete workflows with dependencies




Test Case 15: Alert System for Workflow Failures

Test Case ID: UX03US04_TC_015
Title: Verify alert system triggers for workflow and delivery failures
Priority: P1-Critical
Test Type: Functional
Module: Alert System

Tags: MOD-Alerts, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical

Prerequisites:

  • Workflow with configured triggers
  • Alert system configured
  • Test scenarios for trigger failures and delivery failures

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Simulate event-based trigger failure

NEW: Alert sent to workflow creator

Failed NSC-Created event

NEW: Trigger failure alert

2

Verify alert content and delivery

NEW: Alert contains failure reason and workflow details

N/A

NEW: Alert content verification

3

Create workflow with 100 recipients

Workflow configured for delivery testing

100 test recipients

NEW: Large recipient test

4

Simulate 15% delivery failure

NEW: Alert triggered when >10% messages fail

15 failed deliveries

NEW: Delivery failure threshold

5

Verify delivery failure alert

NEW: Alert shows failure percentage and details

N/A

NEW: Failure alert verification

6

Test alert for different failure types

NEW: Different alerts for trigger vs delivery failures

Various failure scenarios

NEW: Alert differentiation

7

Verify alert recipient targeting

NEW: Alerts sent to workflow creator only

N/A

NEW: Alert targeting

8

Test alert frequency limits

NEW: Prevent alert spam for repeated failures

N/A

NEW: Alert throttling

Verification Points:

  • Primary_Verification: Alert system triggers appropriately for workflow and delivery failures
  • Secondary_Verifications: Alerts contain actionable information, proper recipient targeting
  • Negative_Verification: Alerts don't trigger for normal operations or minor failures



PERFORMANCE BENCHMARKS

Performance Acceptance Criteria:

  • Page Load Times: < 3 seconds for workflow pages
  • API Response Times: < 500ms for critical operations, < 1000ms for complex operations
  • Search Performance: < 300ms for workflow search results
  • Form Submission: < 2 seconds for workflow creation/updates
  • Concurrent Users: Support 100+ concurrent users without degradation
  • Database Performance: Complex queries < 1000ms
  • Memory Usage: < 500MB per user session

EXECUTION MATRIX

Browser Coverage (Desktop Only):

Browser/Device

Version

Priority

Test Cases

Chrome Desktop

115+

P1

All test cases

Firefox Desktop

110+

P1

Core functionality (TC_001-007)

Safari Desktop

16+

P2

Core functionality

Edge Desktop

Latest

P2

Core functionality


TEST SUITE DEFINITIONS

Smoke Test Suite (Pre-deployment):

  • TC_001: Create New Workflow - Happy Path
  • TC_005: Edit Workflow - Communication Channel Non-Editable
  • TC_006: View Workflow Execution History (Updated Format)
  • TC_007: Workflow Performance Metrics (Updated Calculations)
  • TC_013: View vs Edit Button Functionality

Regression Test Suite (Release cycles):

  • TC_001 through TC_012 (Core functionality)
  • TC_013, TC_014, TC_015 (Management and alerts)
  • TC_009 (Cross-browser desktop)
  • TC_010 (API operations)

Full Test Suite (Major releases):

  • All test cases TC_001 through TC_015
  • Cross-browser compatibility
  • Performance testing
  • Security validation
  • Integration testing

KEY UPDATES IMPLEMENTED

1. Target List Integration

  • Moved target list selection from Details step to Trigger step
  • Updated test cases TC_002 to reflect new location

2. Recurring Events Removal

  • Modified TC_003 to only test "Specific Date and Time"
  • Removed all recurring event functionality testing

3. History Tab Updates

  • Removed icons before workflow names (TC_006)
  • Updated status format to "x delivered y failed" (TC_006)
  • Added non-functional action button testing (TC_006)

4. Metrics Definitions Updated

  • Triggered = count of workflow usage (TC_007)
  • Completed = count of successful notifications delivered (TC_007)
  • Success rate = (delivered notifications / total notifications) * 100 (TC_007)

5. CC/BCC Email Enhancement

  • Added CC/BCC testing in workflow creation (TC_004)
  • Added CC/BCC editing in workflow modification (TC_005)

6. Communication Channel Non-Editable

  • New test case TC_005 for channel type editing restrictions
  • Verification that content remains editable while channel type is locked

7. Mobile Testing Removal

  • Removed all mobile device testing scenarios
  • Focused exclusively on desktop browser compatibility

8. Character Limits Placeholder

  • Created TC_008 with placeholders for character limit definitions
  • Ready for implementation once limits are discussed and finalized

PENDING ITEMS FOR DISCUSSION

  1. Character Limits: Specific limits for SMS, WhatsApp, Email channels
  2. API Endpoints: Specific endpoint URLs and authentication methods
  3. Performance Thresholds: Confirmation of performance standards vs. <1 second requirement
  4. Integration Points: Specific external systems and their integration requirements

This comprehensive test suite now aligns with all your specified requirements and includes the updated functionality while maintaining the quality standards for a B2B utility SaaS product.