Skip to main content

Communication Workflows (UX03US04)

Communication Workflows - Updated Comprehensive Test Cases

Test Scenario Summary

Functional testTest 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 andtriggers Event-based(Specific triggersDate/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 testTest scenariosScenarios:

      • 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 - BrowserDesktop and devicebrowser 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

    NavigateLeave toworkflow Communicationname Workflows pageempty

    WorkflowsError: page"Workflow loadsname withis Active tab selectedrequired"

    N/A"" (empty)

    VerifyNEW: pageRequired headerfield and navigationvalidation

    2

    ClickLeave "Newemail Workflow"subject buttonempty

    CreateError: New"Subject Workflowis modalrequired opensfor withemail Details step activemessages"

    N/A"" (empty)

    ModalNEW: shouldEmail showsubject 3-step wizardvalidation

    3

    EnterLeave Workflowemail Namecontent empty

    FieldError: accepts"Message input,content nocannot validationbe errorsempty"

    "Customer" Onboarding Sequence"(empty)

    MinNEW: 3Message characterscontent requiredvalidation

    4

    Enter Descriptionduplicate workflow name

    FieldError: accepts"Workflow input,name characteralready count updatesexists"

    "AutomatedExisting welcomeWorkflow messages for new customers"Name"

    MinNEW: 5Uniqueness characters requiredvalidation

    5

    SelectEnter Audienceinvalid Typeemail in CC field

    DropdownError: shows"Please Consumer,enter Technician,valid Businessemail User optionsaddresses"

    Select "Consumer"invalid-email"

    SingleNEW: selectionCC requiredfield validation

    6

    SelectEnter Targetmalformed ListBCC (optional)addresses

    DropdownError: shows"BCC availablefield listscontains invalid email format"

    Select "New Customers"test@,invalid"

    OptionalNEW: BCC field validation

    7

    ClickExceed "Next"SMS buttoncharacter limit

    NavigateWarning: to"Message Triggerexceeds step,160 stepcharacter 2 becomes activelimit"

    N/A161+ characters

    ButtonNEW: enabledSMS onlylimit when required fields filledwarning

    8

    SelectExceed "Event-Based"WhatsApp trigger typelimit

    Event-BasedWarning: option"Message selected,exceeds Event1024 Typecharacter dropdown appearslimit"

    N/A1025+ characters

    RadioNEW: buttonWhatsApp selectionlimit warning

    9

    SelectTry Eventto Typesave incomplete workflow

    DropdownError: shows"Please systemcomplete eventsall required fields"

    Select "NSC-Created"N/A

    SystemNEW: eventCompletion selectionvalidation

    10

    ClickTest "Next"special buttoncharacters in name

    NavigateAccept tospecial Actionscharacters step, step 3 becomes active

    N/A

    Trigger configuration saved

    11

    Click "Add First Action"

    Communication channel selection appears

    N/A

    Action configuration panel opens

    12

    Select Email channel

    Email selected, message source options appear

    N/A

    Channel-specific options displayed

    13

    Click "Create New Message"

    Message composition fields appear

    N/A

    Toggle between template/new message

    14

    Enter email subject

    Subject field accepts inputappropriately

    "Welcome to UtilityConnect!"Test-Workflow_2024"

    RequiredNEW: fieldSpecial forcharacter email

    15

    Enter email content

    Message body accepts rich text input

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

    Support for variables/placeholders

    16

    Click "Add Action"

    Action added to workflow, action summary displayed

    N/A

    Action configuration saved

    17

    Click "Create Workflow"

    Workflow created successfully, redirect to workflows list

    N/A

    Success confirmation message

    18

    Verify workflow in Active tab

    New workflow appears in Active workflows list with correct details

    N/A

    Status should be "Active"handling

    Verification Points:

    • Primary_Verification:Primary_Verification: WorkflowAll appearsform infields Activehave tabappropriate validation with correctclear configurationerror messages
    • Secondary_Verifications:Secondary_Verifications: AllError enteredmessages are user-friendly and actionable
    • Negative_Verification: Invalid data preserved,properly workflowrejected metricswith initializedhelpful (0 triggered, 0 completed)
    • Negative_Verification: Workflow does not appear in Draft or History tabsguidance




    Test Case 2:12: CreateMaximum WorkflowActions withLimit Time-Based TriggerEnforcement

    Test Case ID: UX03US04_TC_002UX03US04_TC_012
    Title: CreateVerify workflow withcannot specificexceed date/timemaximum triggerof configuration10 actions per workflow
    Priority: P1-CriticalP2-High
    Test Type: Functional
    Module: CommunicationWorkflow WorkflowsLimits
     

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

    Business Context:

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

    Prerequisites:

    • UserWorkflow loggedcreation in asActions Customer Service Managerstep
    • ValidAbility workflowto detailsadd configuredmultiple in previous steps
    • Future date/time available for selectionactions

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    NavigateAdd 9 actions to the Workflows sectionworkflow

    WorkflowsAll page9 loadsactions withadded Active tab selectedsuccessfully

    N/AVarious channel types

    VerifyApproaching page header and navigationlimit

    2

    ClickAdd "New10th Workflow" buttonaction

    Create10th Newaction Workflowadded, modalmaximum opens with Details step activereached

    N/AEmail action

    ModalNEW: shouldMaximum showlimit 3-step wizardreached

    3

    NameAttempt theto workflowadd 11th action

    FieldError: accepts"Maximum input,of no10 validationactions errorsallowed per workflow"

    "ReengagementSMS Campaign"action

    MinNEW: 3Limit characters requiredenforcement

    4

    ProvideVerify a"Add descriptionAction" button state

    FieldButton acceptsdisabled input,or charactershows countlimit updatesmessage

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

    MinNEW: 5UI characterslimit requiredindication

    5

    SelectTry "Consumer"to asduplicate theexisting audience typeaction

    DropdownStill showscounts Consumertoward option10-action selectedlimit

    SelectDuplicate "Consumer"email

    SingleNEW: selectionDuplication requiredcounting

    6

    SelectRemove Targetone List (optional)action

    Dropdown"Add showsAction" button becomes available consumer listsagain

    Select "Inactive Users"N/A

    OptionalNEW: fieldDynamic forlimit targetingmanagement

    7

    ClickAdd "Next"action toafter configure the triggerremoval

    NavigateCan toadd Triggeraction step,when stepunder 2 becomes activelimit

    N/A

    Button enabled when required fields filled

    8

    Select "Time-Based" trigger type

    Time-Based option selected, sub-options appear

    N/A

    Radio button selection

    9

    Select "Specific Date and Time"

    Date and Time input fields appear

    N/A

    Sub-option for time-based trigger

    10

    Set start date for the campaign

    Date picker opens, future date selectable

    Tomorrow's date

    Must be future date

    11

    Set time for the campaign

    Time picker allows time selection

    "10:00:00"

    24-hour format support

    12

    Click "Next" to configure communications

    Navigate to Actions step with trigger saved

    N/A

    Time-based trigger configuration saved

    13

    Add email action as the first step

    Click "Add First Action", select Email channel

    N/A

    First communication step

    14

    Create compelling re-engagement content

    Email composer with subject and body fields

    N/A

    Message creation mode

    15

    Enter email subject

    Subject field accepts input

    "We Miss You - Come Back for Exclusive Offers!"

    Compelling re-engagement subject

    16

    Enter email content

    Message body accepts rich text input

    "Dear [Customer.FirstName], We've noticed you haven't logged in for 30+ days. Here's what you've missed and a special offer to welcome you back..."

    Rich text with personalization

    17

    Click "Add Action"

    Email action added to workflow

    N/A

    First action configured

    18

    Add an SMS follow-upWhatsApp action

    ClickNEW: "AddLimit Action", select SMS channel

    N/A

    Multi-channel approach

    19

    Set timing for SMS

    Configure delay after email

    "2 days"

    Follow-up timing

    20

    Create SMS content

    SMS message field with character counter

    "UtilityConnect: We miss you! Check your email for exclusive offers. Reply STOP to opt out."

    160 character SMS limit

    21

    Click "Add Action"

    SMS action added to sequence

    N/A

    Second action configured

    22

    Review and create the workflow

    Click "Create Workflow"

    N/A

    Complete workflow creation

    23

    Verify workflow creation

    Workflow created with time-based trigger

    N/A

    Success confirmation

    24

    Monitor performance readiness

    Workflow appears in Active tab for performance assessment

    N/A

    Ready for effectiveness monitoringmanagement

    Verification Points:

    • Primary_Verification:Primary_Verification: Re-engagementMaximum 10 actions per workflow createdstrictly with correct time-based trigger configuration for specific date/timeenforced
    • Secondary_Verifications:Secondary_Verifications: ConsumerClear audienceerror selected,messaging, multi-channelUI actionsupdates (Email + SMS) configured, timing delays set properlydynamically
    • Negative_Verification:Negative_Verification: PastCannot date/timeexceed notlimit selectable,under workflowany ready for performance monitoringcircumstances




    Test Case 3:13: CreateView Workflowvs withEdit RecurringButton Event TriggerFunctionality

    Test Case ID: UX03US04_TC_003UX03US04_TC_013
    Title: ConfigureVerify distinct behavior of View and Edit buttons on workflow with recurring event trigger and frequency settingscards
    Priority: P2-HighP1-Critical
    Test Type: Functional
    Module: CommunicationWorkflow WorkflowsManagement
     

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

    Prerequisites:

    • UserExisting loggedworkflows inwith asboth BillingView Managerand Edit buttons
    • ValidUser 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 configureddisplayed 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
    • EventDelete type selectionfunctionality available

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    NavigateAttempt to Communicationdelete Workflowsactive pageworkflow

    NEW: System shows dependency check dialog

    WorkflowsActive page loadsworkflow with Active tab selectedusage

    N/A

    VerifyNEW: pageDependency header and navigationchecking

    2

    ClickReview "Newdependency Workflow" buttoninformation

    CreateNEW: NewShows Workflow"Used modalin opensX places" with Details step activedetails

    N/A

    ModalNEW: shouldUsage show 3-step wizardtracking

    3

    EnterView Workflowspecific Nameusage locations

    NEW: List of templates/processes using workflow

    Field accepts input, no validation errorsN/A

    "PaymentNEW: DueDetailed Reminder"

    Min 3 characters requireddependencies

    4

    EnterConfirm Descriptiondeletion despite dependencies

    NEW: Require explicit confirmation

    Field accepts input, character count updatesN/A

    "AutomatedNEW: payment reminders for utility bills"

    Min 5 charactersConfirmation required

    5

    SelectTest Audiencedeletion Typeof unused workflow

    NEW: Direct deletion without dependency warning

    DropdownUnused shows Consumer, Technician, Business User optionsworkflow

    SelectNEW: "Consumer"

    SingleClean selection requireddeletion

    6

    SelectVerify Targetdeletion List (optional)impact

    NEW: Dependent processes show broken references

    Dropdown shows available listsN/A

    SelectNEW: "HighImpact Usage Consumers"

    Optional fieldverification

    7

    ClickTest "Next"cancellation buttonof deletion

    NavigateNEW: toCancel Triggerpreserves step,workflow stepand 2 becomes activedependencies

    N/A

    ButtonNEW: enabledCancellation when required fields filled

    8

    Select "Time-Based" trigger type

    Time-Based option selected

    N/A

    Primary trigger type

    9

    Select "Recurring Event"

    Recurring event configuration fields appear

    N/A

    Sub-option selection

    10

    Select Event Type

    Dropdown shows available events

    "Bill Generated"

    System event for recurrence

    11

    Set Recurrence Frequency

    Enter numeric value

    "3"

    Frequency interval

    12

    Select Time Unit

    Dropdown shows Days/Hours/Weeks

    "Days"

    Time unit for frequency

    13

    Select Start Date

    Date picker for recurrence start

    Tomorrow's date

    Recurrence beginning

    14

    Set Time

    Time picker for daily execution

    "10:00:00"

    Specific time for recurrence

    15

    Click "Next"

    Navigate to Actions with recurring trigger saved

    N/A

    Configuration validated

    16

    Click "Add First Action"

    Communication channel selection appears

    N/A

    Action configuration starts

    17

    Select SMS channel

    SMS selected, character limit shown (160)

    N/A

    Channel-specific constraints

    18

    Click "Use Template"

    Available templates dropdown

    N/A

    Message composition

    19

    Select sms dropdown

    Template selected 

    "UtilityConnect: Your bill of $[Bill.Amount] is due on [Bill.DueDate]. Please pay to avoid service interruption."

    160 character limit, variables supported

    20

    Click "Add Action"

    SMS action added to workflow sequence

    N/A

    Action configuration saved

    21

    Click "Create Workflow"

    Workflow created with recurring trigger

    N/A

    Success confirmation

    22

    Verify recurrence details

    Workflow shows "Time-Based Trigger" with frequency

    N/A

    Recurrence configuration visiblehandling

    Verification Points:

    • Primary_Verification:Primary_Verification: RecurringDeletion triggerprocess configuredshows correctlyall usage dependencies before allowing deletion
    • Secondary_Verifications: Clear impact warning, explicit confirmation required
    • Negative_Verification: Cannot accidentally delete workflows with 3-day frequency for bill generation events
    • Secondary_Verifications: Start date and time saved, SMS content with bill variables configured
    • Negative_Verification: Invalid frequency values rejected, past start dates not selectabledependencies





    Test Case 4:15: AddAlert MultipleSystem Communicationfor ChannelsWorkflow Failures

    Test Case ID: UX03US04_TC_004UX03US04_TC_015
    Title: ConfigureVerify alert system triggers for workflow withand multipledelivery communication channels (Email + SMS + WhatsApp)failures
    Priority: P1-Critical
    Test Type: Functional
    Module: CommunicationAlert ActionsSystem
     

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

    Business Context:

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

    Quality Metrics:

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

    Prerequisites:

    • UserWorkflow loggedwith inconfigured as Customer Service Managertriggers
    • Browser:Alert Chromesystem 115+configured
    • Environment:Test Staging
    • Workflowscenarios Detailsfor trigger failures and Triggerdelivery already configured for "Multi-Channel Customer Outreach"
    • Multiple channel templates availablefailures

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    NavigateSimulate toevent-based Actionstrigger stepfailure

    NEW: Alert sent to workflow creator

    CommunicationFailed ActionsNSC-Created page displays "No Actions Added Yet"event

    N/A

    ReadyNEW: forTrigger actionfailure configurationalert

    2

    ClickVerify "Addalert Firstcontent Action"and delivery

    CommunicationNEW: channelAlert selectioncontains appearsfailure reason and workflow details

    N/A

    ActionNEW: configurationAlert startscontent verification

    3

    SelectCreate Emailworkflow channelwith 100 recipients

    EmailWorkflow selected,configured messagefor configurationdelivery appearstesting

    N/A100 test recipients

    FirstNEW: channelLarge selectionrecipient test

    4

    ClickSimulate "Create15% Newdelivery Message"failure

    NEW: Alert triggered when >10% messages fail

    Email15 composerfailed with subject and body fieldsdeliveries

    N/A

    MessageNEW: creationDelivery modefailure threshold

    5

    EnterVerify CCdelivery fieldfailure alert

    NEW: Alert shows failure percentage and details

    CC field accepts email inputN/A

    "manager@utilityconnect.com"

    AdditionalNEW: recipientFailure configurationalert verification

    6

    EnterTest emailalert subjectfor different failure types

    NEW: Different alerts for trigger vs delivery failures

    SubjectVarious fieldfailure accepts inputscenarios

    "WelcomeNEW: toAlert UtilityConnect - Your Service is Ready!"

    Email subject linedifferentiation

    7

    EnterVerify emailalert contentrecipient targeting

    NEW: Alerts sent to workflow creator only

    Message body accepts rich text inputN/A

    "DearNEW: [Customer.FirstName],Alert Welcome to UtilityConnect! Your service connection has been successfully created. Here's what to expect next..."

    Rich text with variablestargeting

    8

    SetTest timingalert frequency limits

    SelectNEW: "Immediately"Prevent alert spam for repeated failures

    N/A

    NoNEW: delayAlert for first action

    9

    Click "Add Action"

    Email action added, option to add another action appears

    N/A

    Sequential action setup

    10

    Click "Add Action" button

    Second action configuration opens

    N/A

    Multiple actions supported

    11

    Select SMS channel

    SMS selected, character limit shown (160)

    N/A

    Channel-specific constraints

    12

    Click "Create New Message"

    SMS message field with character counter

    N/A

    SMS message creation

    13

    Enter SMS content

    SMS message field accepts input

    "UtilityConnect: Welcome! Your service is active. Check your email for details. Reply HELP for assistance."

    160 character limit enforced

    14

    Set timing

    Select "After previous action", set delay

    "2 days"

    Delay between actions

    15

    Click "Add Action"

    SMS action added to sequence

    N/A

    Second action configured

    16

    Click "Add Action" button

    Third action configuration opens

    N/A

    Support for multiple actions

    17

    Select WhatsApp channel

    WhatsApp notification selected

    N/A

    Third channel type

    18

    Click "Create New Message"

    WhatsApp message field appears

    N/A

    WhatsApp message creation

    19

    Enter WhatsApp content

    WhatsApp message field accepts input

    "Welcome to UtilityConnect! 🎉 Your service connection is now active. We're here to help you get the most out of your utility services. Feel free to reach out with any questions!"

    WhatsApp specific formatting (1024 char limit)

    20

    Set timing

    Configure delay after SMS

    "1 day"

    Sequential timing

    21

    Click "Add Action"

    All three actions configured in sequence

    N/A

    Multi-channel workflow complete

    22

    Review action sequence

    Actions display: 1 email (immediate), 1 SMS (2 days), 1 WhatsApp (1 day)

    N/A

    Sequence validation

    23

    Click "Create Workflow"

    Workflow created with multi-channel actions

    N/A

    Complete workflow creation

    24

    Verify workflow in Active tab

    New workflow appears in Active workflows list

    N/A

    Workflow successfully created

    25

    Verify workflow card details

    Shows "3 actions", "Consumers", "1 email, 1 sms, 1 WhatsApp"

    N/A

    Multi-channel summary displayedthrottling

    Verification Points:

    • Primary_Verification:Primary_Verification: AllAlert threesystem communicationtriggers channelsappropriately configuredfor correctlyworkflow inand sequencedelivery withfailures
    • Secondary_Verifications: Alerts contain actionable information, proper timingrecipient delaystargeting
    • Negative_Verification:Secondary_Verifications: CCAlerts fielddon't configuredtrigger for email,normal characteroperations limitsor enforcedminor for SMS, WhatsApp message, timing delays set properly between actions
    • Negative_Verification: Maximum action limit (10) enforced, invalid timing configurations rejectedfailures




    Test Case 5: Use Template for Message Creation

    Test Case ID: UX03US04_TC_005
     Title: Configure communication action using existing template
     Priority: P2-High
     Test Type: Functional
     Module: Template Integration
     Tags: MOD-Templates, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-High

    Prerequisites:

    • Existing email templates available in system
    • At Actions step of workflow creation
    • Template library populated with test templates

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Click "Add First Action"

    Communication channel selection appears

    N/A

    Start action configuration

    2

    Select Email channel

    Email configuration options appear

    N/A

    Channel selection

    3

    Click "Use Template" tab

    Template selection interface appears

    N/A

    Toggle from "Create New Message"

    4

    Browse available templates

    List of email templates displayed with previews

    N/A

    Template library access

    5

    Select template

    Template "Welcome Email v2" highlighted

    "Welcome Email v2"

    Template selection

    6

    Preview template

    Template preview shows content and variables

    N/A

    Template preview functionality

    7

    Verify template variables

    Variables like [Customer.FirstName] visible

    N/A

    Variable placeholder support

    8

    Click "Add Action"

    Template-based action added to workflow

    N/A

    Template integration complete

    9

    Verify action summary

    Action shows template name and preview

    N/A

    Template reference maintained

    10

    Complete workflow creation

    Workflow created using template-based action

    N/A

    End-to-end template usage

    Verification Points:

    • Primary_Verification: Template successfully integrated into workflow action
    • Secondary_Verifications: Template variables preserved, template name referenced correctly
    • Negative_Verification: Deleted templates not available for selection




    Test Case 6: Edit Existing Workflow

    Test Case ID: UX03US04_TC_006
     Title: Edit existing workflow configuration through edit interface
     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 active workflow "Monthly Energy Usage Report"
    • User has edit permissions
    • Workflow edit interface accessible

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Navigate to Active workflows tab

    Active workflows displayed

    N/A

    Workflow list view

    2

    Locate workflow to edit

    "Monthly Energy Usage Report" workflow visible

    N/A

    Target workflow identification

    3

    Click edit icon (pencil)

    Redirect to edit workflow page

    N/A

    Edit action trigger

    4

    Verify edit interface

    Edit page opens with Details, Trigger, Actions, Preview tabs

    N/A

    Tab-based edit interface

    5

    Navigate to Details tab

    Workflow details displayed in read-only format

    N/A

    Details view in edit mode

    6

    Navigate to Trigger tab

    Current trigger configuration shown (Time-Based, Recurring)

    N/A

    Trigger modification interface

    7

    Modify trigger settings

    Change from Monthly to Weekly frequency

    Select "Weekly"

    Trigger frequency modification

    8

    Set new execution time

    Configure new execution schedule

    "Every Monday 8:00 AM"

    New timing configuration

    9

    Navigate to Actions tab

    Current actions listed with edit options

    N/A

    Actions management interface

    10

    Edit existing email action

    Modify email subject and content

    New subject: "Weekly Energy Update!"

    Content modification

    11

    Add CC/BCC fields

    Configure additional email recipients

    CC: "billing@utility.com"

    Enhanced email options

    12

    Navigate to Preview tab

    Updated workflow preview displayed

    N/A

    Changes preview

    13

    Click "Save Changes"

    Changes saved successfully, redirect to workflows list

    N/A

    Save modifications

    14

    Verify updated workflow

    Workflow shows updated trigger type and modification timestamp

    N/A

    Changes persisted

    Verification Points:

    • Primary_Verification: Workflow modifications saved and reflected in workflow list
    • Secondary_Verifications: Trigger frequency changed from Monthly to Weekly, email content updated, CC/BCC configured
    • Negative_Verification: Original monthly configuration no longer active




    Test Case 7: Filter Workflows by Status

    Test Case ID: UX03US04_TC_007
     Title: Filter workflows using status tabs (Active, Drafts, History)
     Priority: P2-High
     Test Type: Functional
     Module: Workflow Management
     Tags: MOD-Management, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Medium

    Prerequisites:

    • Workflows exist in different states (Active, Draft, Completed)
    • Multiple workflows for filtering
    • All workflow states represented in test data

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Navigate to Communication Workflows page

    Page loads with Active tab selected by default

    N/A

    Default filter state

    2

    Click "Drafts" tab

    Tab switches to Drafts, URL updates

    N/A

    Tab navigation

    3

    Verify Drafts content

    Only draft workflows displayed

    N/A

    Draft status filter

    4

    Verify draft workflow indicators

    Draft workflows show "Draft" status badge

    N/A

    Status visualization

    5

    Click "All Workflows" tab

    All workflows displayed regardless of status

    N/A

    No status filtering

    6

    Verify combined view

    Active + Draft + other statuses visible

    N/A

    Comprehensive view

    7

    Click "History" tab

    Completed/failed workflows displayed

    N/A

    Historical data view

    8

    Verify history content

    Only executed workflows with completion status

    N/A

    Execution history

    Verification Points:

    • Primary_Verification: Status filters work correctly, showing appropriate workflows
    • Secondary_Verifications: Tab selection persists, workflow counts accurate per filter
    • Negative_Verification: Workflows don't appear in incorrect status tabs




    Test Case 8: Search Workflows by Name

    Test Case ID: UX03US04_TC_008
     Title: Search for specific workflows using search functionality
     Priority: P2-High
     Test Type: Functional
     Module: Search & Navigation
     Tags: MOD-Search, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Medium

    Prerequisites:

    • Multiple workflows with different names exist
    • Search functionality available on workflows page
    • Test workflows: "Customer Welcome", "Payment Reminder", "Service Update"

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Navigate to workflows page

    Workflows page loads with search box visible

    N/A

    Search interface availability

    2

    Click in search box

    Search field active, cursor positioned

    N/A

    Search interaction

    3

    Enter partial workflow name

    Search results filter in real-time

    "Welcome"

    Partial match search

    4

    Verify search results

    Only workflows containing "Welcome" displayed

    N/A

    Filtered results

    5

    Clear search field

    All workflows displayed again

    N/A

    Search reset

    6

    Search for exact workflow name

    Exact match displayed

    "Payment Reminder"

    Exact match functionality

    7

    Verify single result

    Only "Payment Reminder" workflow shown

    N/A

    Precise filtering

    8

    Search for non-existent workflow

    No results displayed, appropriate message shown

    "NonExistent"

    No results handling

    9

    Verify empty state

    "No workflows found" message or similar

    N/A

    Empty state messaging

    10

    Search with special characters

    Search handles special characters appropriately

    "Service-Update"

    Special character support

    Verification Points:

    • Primary_Verification: Search functionality returns correct results based on workflow names
    • Secondary_Verifications: Real-time filtering works, empty states handled properly
    • Negative_Verification: Search doesn't return irrelevant results




    Test Suite: Workflow Execution & History

    Test Case 9: View Workflow Execution History

    Test Case ID: UX03US04_TC_009
     Title: View detailed execution history for completed workflows
     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 have been executed with various outcomes
    • History data available for display
    • Both successful and failed executions exist

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Navigate to Communication Workflows page

    Workflows page loads

    N/A

    Base navigation

    2

    Click "History" tab

    History view opens showing execution records

    N/A

    History tab access

    3

    Verify history layout

    Execution records displayed with expandable sections

    N/A

    History interface structure

    4

    Locate completed workflow execution

    "New Customer Welcome" with "Completed" status visible

    N/A

    Find successful execution

    5

    Expand completed execution

    Detailed execution information displayed

    N/A

    Expandable detail view

    6

    Verify execution details

    Recipients count, start/completion times, status shown

    Recipients: 142, Start: 11/20/2023 10:30:00 AM

    Execution metadata

    7

    Review message delivery details

    Individual message statuses (Email: Delivered, SMS: Delivered)

    N/A

    Per-message status tracking

    8

    Locate failed workflow execution

    "New Customer Welcome" with "Failed" status visible

    N/A

    Find failed execution

    9

    Expand failed execution

    Failure details and error information displayed

    N/A

    Error information access

    10

    Verify failure details

    Specific error messages and failed message details shown

    Error: "Invalid email address"

    Error reporting detail

    11

    Check in-progress execution

    "Reengagement Campaign" with "In-Progress" status

    N/A

    Active execution monitoring

    12

    Verify progress indicators

    Progress status and completion percentage if available

    N/A

    Progress tracking

    Verification Points:

    • Primary_Verification: Execution history displays comprehensive details for all workflow runs
    • Secondary_Verifications: Success/failure statuses accurate, timing information correct, individual message statuses tracked
    • Negative_Verification: No unauthorized access to execution data




    Test Case 10: Workflow Performance Metrics

    Test Case ID: UX03US04_TC_010
     Title: Verify 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
    • Performance data available for calculation
    • Various success/failure scenarios executed

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Navigate to All workflows

    All  workflows displayed with performance metrics

    N/A

    Metrics visibility

    2

    Locate workflow with execution history

    "New Customer Welcome" workflow card visible

    N/A

    Target workflow identification

    3

    Verify triggered count

    Number of times workflow was triggered displayed

    Triggered: 245

    Trigger event count

    4

    Verify completed count

    Number of successful completions shown

    Completed: 240

    Success count

    5

    Verify success rate calculation

    Success rate percentage calculated correctly

    Success Rate: 98.0%

    (240/245) * 100

    6

    Check workflow with different metrics

    "Product Update Announcement" with different performance

    Triggered: 8560, Completed: 8500, Success Rate: 99.3%

    Alternate performance data

    7

    Verify draft workflow metrics

    Draft workflows show zero or N/A for metrics

    Triggered: 0, Completed: 0, Success Rate: 0%

    Draft state handling

    8

    Navigate to workflow edit page

    Access detailed performance metrics

    N/A

    Detailed metrics view

    9

    Verify detailed performance section

    Extended metrics including failed count displayed

    Failed: 5 times

    Additional metric details

    Verification Points:

    • Primary_Verification: Performance metrics calculated correctly and displayed accurately
    • Secondary_Verifications: Success rates match manual calculations, metrics update with new executions
    • Negative_Verification: Metrics don't show inflated or incorrect numbers




    Test Suite: Data Validation & Error Handling

    Test Case 11: Workflow Name Validation

    Test Case ID: UX03US04_TC_011
     Title: Validate workflow name field requirements and error handling
     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-Low, Business-Medium

    Prerequisites:

    • Create workflow page accessible
    • Various invalid input scenarios prepared
    • Validation rules: minimum 3 characters, unique names

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Navigate to Create New Workflow

    Workflow creation modal opens

    N/A

    Start workflow creation

    2

    Leave workflow name empty

    Field shows as required, Next button disabled

    "" (empty)

    Required field validation

    3

    Enter 1 character

    Validation error: "Name must be at least 3 characters"

    "A"

    Minimum length validation

    4

    Enter 2 characters

    Same validation error persists

    "AB"

    Continued minimum length check

    5

    Enter exactly 3 characters

    Validation passes, no error message

    "ABC"

    Minimum threshold acceptance

    6

    Enter existing workflow name

    Error: "Workflow name already exists"

    "New Customer Welcome"

    Uniqueness validation

    7

    Enter special characters

    Name accepted with special characters

    "Test-Workflow_2024"

    Special character support

    8

    Enter very long name

    Field handles long names appropriately

    255 character string

    Maximum length handling

    9

    Enter name with spaces

    Leading/trailing spaces handled correctly

    " Valid Name "

    Space trimming

    10

    Enter valid unique name

    Validation passes, Next button enabled

    "Test Workflow 2024"

    Successful validation

    Verification Points:

    • Primary_Verification: All validation rules enforced correctly
    • Secondary_Verifications: Error messages clear and helpful, field validation real-time
    • Negative_Verification: Invalid names rejected, duplicate names prevented




    Test Case 12: Message Content Character Limits

    Test Case ID: UX03US04_TC_012
     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:

    • At Actions step of workflow creation
    • Different communication channels available
    • Character limit test strings prepared

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Select SMS channel

    SMS configuration appears with character counter

    N/A

    SMS channel selection

    2

    Enter text up to limit

    Character counter shows remaining characters

     character string(to be discussed)

    Within SMS limit

    3

    Verify character counter

    Counter shows "0 characters remaining"

    N/A

    Accurate character counting

    4

    Attempt to exceed limit

    Additional characters prevented or warning shown

    161+ character string

    Limit enforcement

    5

    Switch to Email channel

    No character limit warning for email

    N/A

    Channel-specific rules

    6

    Enter long email content

    Email accepts extended content without restrictions

    2000+ character string

    Email length flexibility

    9

    Switch to WhatsApp channel

    WhatsApp-specific character limit applied

    N/A

    WhatsApp channel rules

    10

    Verify WhatsApp limit

    Character limit appropriate for WhatsApp (1024 characters)

    1024+ character string

    WhatsApp constraint validation

    Verification Points:

    • Primary_Verification: Character limits enforced correctly for each communication channel
    • Secondary_Verifications: Character counters accurate, appropriate limits per channel
    • Negative_Verification: Limits not applied to channels that shouldn't have them




    Test Suite: Cross-Platform Compatibility

    Test Case 13: Browser Compatibility Testing

    Test Case ID: UX03US04_TC_013
     Title: Verify workflow creation functionality across different browsers
     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
    • Same test data across all browsers
    • Consistent test environment

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Open Chrome browser

    Navigate to workflows page successfully

    N/A

    Chrome compatibility

    2

    Execute Test Case 1 in Chrome

    Complete workflow creation without issues

    Standard test data

    Chrome functionality

    3

    Verify UI elements in Chrome

    All buttons, forms, and modals render correctly

    N/A

    Chrome UI consistency

    4

    Open Firefox browser

    Navigate to same workflows page

    N/A

    Firefox compatibility

    5

    Execute Test Case 1 in Firefox

    Complete workflow creation successfully

    Same test data

    Firefox functionality

    6

    Compare Firefox UI

    UI elements consistent with Chrome version

    N/A

    Cross-browser UI consistency

    7

    Open Safari browser

    Access workflows functionality

    N/A

    Safari compatibility

    8

    Test workflow creation in Safari

    All features work as expected

    Same test data

    Safari functionality

    9

    Verify Safari-specific elements

    Date/time pickers, dropdowns work correctly

    N/A

    Safari UI components

    10

    Open Edge browser

    Complete workflow creation process

    N/A

    Edge compatibility

    11

    Test all major features in Edge

    Create, edit, view workflows successfully

    Same test data

    Edge functionality

    12

    Document any browser differences

    Note any browser-specific behaviors

    N/A

    Compatibility documentation

    Verification Points:

    • Primary_Verification: Core functionality works consistently across all supported browsers
    • Secondary_Verifications: UI renders correctly, JavaScript functions properly, form submissions work
    • Negative_Verification: No browser-specific errors or functionality degradation







    Test Suite: Performance Testing

    Test Case 14: Page Load Performance

    Test Case ID: UX03US04_TC_014
     Title: Verify workflow page load times meet performance requirements
     Priority: P2-High
     Test Type: Performance
     Module: Page Performance
     Tags: MOD-Performance, P2-High, Phase-Performance, Type-Performance, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-Medium, Business-High

    Prerequisites:

    • Performance testing tools available
    • Large dataset of workflows (100+ workflows)
    • Network conditions controlled
    • Performance baseline: Page load < 3 seconds

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Clear browser cache

    Cache cleared, fresh page load

    N/A

    Baseline conditions

    2

    Navigate to workflows page

    Measure initial page load time

    N/A

    First load performance

    3

    Record load time

    Page loads within 3 seconds

    Target: < 3 seconds

    Performance requirement

    4

    Load page with many workflows

    Performance with large dataset

    100+ workflows

    Scalability testing

    5

    Measure filtering performance

    Status tab switching response time

    N/A

    Filter performance

    6

    Test search performance

    Search results appear within 1sec

    N/A

    Search responsiveness

    7

    Measure workflow creation modal

    Modal opens within 1 second

    N/A

    Modal performance

    8

    Test form submission performance

    Workflow creation completion time

    N/A

    Form processing speed

    9

    Monitor memory usage

    Page doesn't cause memory leaks

    N/A

    Memory performance

    10

    Test concurrent user simulation

    Performance under multiple users

    10 concurrent users

    Load testing

    Verification Points:

    • Primary_Verification: All page interactions meet defined performance thresholds
    • Secondary_Verifications: No performance degradation with large datasets, memory usage stable
    • Negative_Verification: No timeouts or performance errors under normal load




    Test Case 16: API Response Time Testing

    Test Case ID: UX03US04_TC_016
     Title: Verify API response times for workflow operations
     Priority: P1-Critical
     Test Type: Performance
     Module: API Performance
     Tags: MOD-API, P1-Critical, Phase-Performance, Type-Performance, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical

    Prerequisites:

    • API endpoints accessible for testing
    • Performance monitoring tools available
    • Baseline: API responses < 500ms for critical operations

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Test GET /workflows API

    Retrieve workflows list within 1sec

    N/A

    Read operation performance

    2

    Test POST /workflows API

    Create workflow within 1sec

    Valid workflow data

    Write operation performance

    3

    Test PUT /workflows/{id} API

    Update workflow within 1sec

    Modified workflow data

    Update operation performance

    4

    Test GET /workflows/{id}/history

    Execution history within 1sec

    N/A

    History retrieval performance

    5

    Test workflow execution trigger

    Trigger processing within 1sec

    N/A

    Trigger response time

    6

    Load test with multiple requests

    API maintains performance under load

    50 concurrent requests

    API load testing

    7

    Test database query performance

    Complex queries complete efficiently

    N/A

    Database performance

    8

    Monitor API error rates

    Error rate stays below 1%

    N/A

    API reliability

    9

    Test peak usage scenarios

    Performance during high usage periods

    N/A

    Peak load handling

    10

    Verify response consistency

    Response times consistent across calls

    N/A

    Performance stability

    Verification Points:

    • Primary_Verification: All API operations meet defined response time requirements
    • Secondary_Verifications: Performance consistent under load, error rates acceptable
    • Negative_Verification: No API timeouts or failures under normal conditions




    Test Suite: Security Testing

    Test Case 17: Role-Based Access Control

    Test Case ID: UX03US04_TC_017
     Title: Verify proper access control for workflow operations based on user roles
     Priority: P1-Critical
     Test Type: Security
     Module: Access Control
     Tags: MOD-Security, P1-Critical, Phase-Security, Type-Security, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical

    Prerequisites:

    • Different user roles configured: Utility Admin, Customer Service Manager, Billing Manager, Meter Manager
    • Role-based permission matrix defined
    • Test users for each role available

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Login as Utility Admin

    Full access to all workflow features

    Admin credentials

    Highest privilege level

    2

    Verify admin workflow access

    Can create, edit, delete all workflows

    N/A

    Admin permissions

    3

    Test admin-only features

    Access to system-wide workflow settings

    N/A

    Admin-exclusive functions

    4

    Login as Customer Service Manager

    Limited access based on role

    CSM credentials

    Role-specific access

    5

    Verify CSM permissions

    Can create customer-facing workflows only

    N/A

    Role-based restrictions

    6

    Test CSM restrictions

    Cannot access admin-only features

    N/A

    Permission boundaries

    7

    Login as Billing Manager

    Access to billing-related workflows

    Billing Manager credentials

    Department-specific access

    8

    Verify billing permissions

    Can create payment/billing workflows

    N/A

    Domain-specific permissions

    9

    Test cross-department access

    Cannot modify non-billing workflows

    N/A

    Department isolation

    10

    Login as Meter Manager

    Access to field operations workflows

    Meter Manager credentials

    Field operations access

    11

    Verify meter manager scope

    Limited to meter/field-related workflows

    N/A

    Scope-based permissions

    12

    Test unauthorized access attempts

    Proper error messages for denied access

    N/A

    Access denial handling

    Verification Points:

    • Primary_Verification: Each role has appropriate access levels, no unauthorized access possible
    • Secondary_Verifications: Permission boundaries enforced, proper error handling for denied access
    • Negative_Verification: Users cannot access functions outside their role permissions





    Test Suite: Integration Testing

    Test Case 19: External System Integration

    Test Case ID: UX03US04_TC_019
     Title: Verify integration with external systems for event triggers and notifications
     Priority: P1-Critical
     Test Type: Integration
     Module: System Integration
     Tags: MOD-Integration, P1-Critical, Phase-Integration, Type-Integration, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical

    Prerequisites:

    • External systems available: CRM, Billing System, Meter Management System
    • Integration endpoints configured
    • Test data synchronized across systems

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Create event-based workflow

    Workflow configured for NSC-Created event

    N/A

    Event trigger setup

    2

    Trigger NSC-Created in CRM

    External system generates service connection event

    New customer: John Doe

    External event generation

    3

    Verify workflow activation

    Workflow triggered by external event

    N/A

    Event integration

    4

    Monitor workflow execution

    Workflow processes customer data from CRM

    Customer data: John Doe details

    Data flow integration

    5

    Test billing system integration

    Workflow triggered by payment due event

    N/A

    Billing system connectivity

    6

    Verify meter system integration

    Field completion events trigger workflows

    Meter installation complete

    Meter system integration

    7

    Test notification delivery

    Messages sent through integrated channels

    N/A

    Notification system integration

    8

    Verify data synchronization

    Customer data consistent across systems

    N/A

    Data consistency

    9

    Test error handling

    Integration failures handled gracefully

    N/A

    Integration resilience

    10

    Monitor integration performance

    Integration operations within SLA

    N/A

    Integration performance

    Verification Points:

    • Primary_Verification: All external system integrations function correctly
    • Secondary_Verifications: Data flows properly between systems, error handling robust
    • Negative_Verification: Integration failures don't cause system instability




    Test Case 20: Email Service Integration

    Test Case ID: UX03US04_TC_020
     Title: Verify email delivery through integrated email service provider
     Priority: P1-Critical
     Test Type: Integration
     Module: Email Integration
     Tags: MOD-Integration, P1-Critical, Phase-Integration, Type-Integration, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-Critical

    Prerequisites:

    • Email service provider configured (SendGrid, AWS SES, etc.)
    • Test email addresses available
    • Email templates configured

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Create email workflow

    Workflow with email action configured

    N/A

    Email workflow setup

    2

    Execute workflow manually

    Email action triggers message sending

    test@example.com

    Manual execution

    3

    Verify email delivery

    Email delivered to recipient inbox

    N/A

    Delivery confirmation

    4

    Check email content

    Email content matches workflow configuration

    N/A

    Content accuracy

    5

    Test email variables

    Dynamic variables resolved correctly

    [Customer.FirstName] = "John"

    Variable substitution

    6

    Verify sender information

    From address and name correct

    from: noreply@utilityconnect.com

    Sender configuration

    7

    Test CC/BCC functionality

    Additional recipients receive email

    CC: manager@utility.com

    Additional recipients

    8

    Check delivery status tracking

    Delivery status updated in workflow history

    Status: Delivered

    Status tracking

    9

    Test bounce handling

    Bounced emails handled appropriately

    invalid@email.com

    Bounce processing

    10

    Verify unsubscribe handling

    Unsubscribe requests processed correctly

    N/A

    Unsubscribe functionality

    Verification Points:

    • Primary_Verification: Email delivery works reliably through integrated service
    • Secondary_Verifications: Content accurate, variables resolved, delivery status tracked
    • Negative_Verification: No email delivery failures for valid addresses




    API TEST CASES (Critical Level ≥7)

    Test Case 21: Workflow CRUD API Operations

    Test Case ID: UX03US04_TC_021
     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

    Business Context:

    • Critical API operations supporting core business functionality
    • Revenue_Impact: High
    • Integration dependency for external systems

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    POST /api/workflows

    Create new workflow successfully

    Valid workflow JSON

    Create operation

    2

    Verify response structure

    Proper JSON response 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 subsequent GET

    N/A

    Update verification

    7

    DELETE /api/workflows/{id}

    Delete workflow

    Workflow ID

    Delete operation

    8

    Verify deletion

    GET returns 404 for deleted workflow

    N/A

    Deletion verification

    9

    Test error scenarios

    Invalid data returns appropriate errors

    Invalid JSON

    Error handling

    10

    Verify status codes

    Correct HTTP status codes returned

    N/A

    Status code validation




    Test Case 22: Workflow Execution API

    Test Case ID: UX03US04_TC_022
     Title: Test workflow execution and status monitoring via API
     Priority: P1-Critical
     Test Type: API
     Module: Execution API
     Tags: MOD-API, P1-Critical, Phase-Regression, Type-API, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical

    Test Procedure:

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    POST /api/workflows/{id}/execute

    Trigger workflow execution

    Workflow ID

    Manual execution trigger

    2

    Verify execution initiation

    Execution started successfully

    N/A

    Execution confirmation

    3

    GET /api/workflows/{id}/status

    Monitor execution status

    N/A

    Status monitoring

    4

    GET /api/workflows/{id}/history

    Retrieve execution history

    N/A

    History access

    5

    Verify execution details

    Complete execution information available

    N/A

    Detail validation

    6

    Test concurrent executions

    Multiple workflows execute simultaneously

    N/A

    Concurrency testing

    7

    Monitor execution performance

    Executions complete within SLA

    N/A

    Performance monitoring

    8

    Test execution cancellation

    Cancel running workflow execution

    N/A

    Cancellation functionality

    9

    Verify failure handling

    Failed executions reported correctly

    N/A

    Failure processing

    10

    Test retry mechanisms

    Failed workflows retry as configured

    N/A

    Retry logic




    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
    • Network Usage: Optimized for low-bandwidth connections




    EXECUTION MATRIX

    Browser/DeviceBrowser Coverage:Coverage (Desktop Only):

    Browser/Device

    Version

    Priority

    Test Cases

    Browser/DeviceChrome Desktop

    Version115+

    PriorityP1

    TestAll Casestest cases

    ChromeFirefox Desktop

    115+110+

    P1

    AllCore testfunctionality cases(TC_001-007)

    FirefoxSafari Desktop

    110+16+

    P1P2

    Core functionality (TC_001-010)

    SafariEdge Desktop

    16+Latest

    P2

    Core functionality

    Edge Desktop

    Latest

    P2

    Core functionality

    iOS Safari

    16+

    P3

    Mobile-optimized tests

    Android Chrome

    13+

    P3

    Mobile-optimized tests


    TEST SUITE DEFINITIONS

    Test Suite Definitions:

    Smoke Test Suite (Pre-deployment):

    • TC_001: Create New Workflow - Happy Path
    • TC_006:TC_005: Edit ExistingWorkflow Workflow- Communication Channel Non-Editable
    • TC_009:TC_006: View Workflow Execution History (Updated Format)
    • TC_007: Workflow Performance Metrics (Updated Calculations)
    • TC_017:TC_013: Role-BasedView Accessvs ControlEdit Button Functionality

    Regression Test Suite (Release cycles):

    • TC_001 through TC_012 (Core functionality)
    • TC_015,TC_013, TC_016TC_014, TC_015 (Performance)Management and alerts)
    • TC_017, TC_018TC_009 (Security)Cross-browser desktop)
    • TC_021, TC_022TC_010 (API)API operations)

    Full Test Suite (Major releases):

    • All test cases TC_001 through TC_022TC_015
    • Cross-browser compatibility
    • Performance under loadtesting
    • Security penetrationvalidation
    • Integration testing
    • Integration with all external systems




    DEPENDENCYKEY MAPPINGUPDATES IMPLEMENTED

    Test Execution Dependencies:

    1. Infrastructure Setup →1. UserTarget Authentication → Basic Navigation
    2. Workflow Creation → Workflow Management → Workflow Execution
    3. Template Setup → TemplateList Integration Tests
    4. External System Configuration → Integration Tests
    5. Performance Baseline → Performance Tests

    External Dependencies:

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

    2. CRMRecurring System: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: AvailableSpecific limits for NSC-CreatedSMS, eventsWhatsApp, Email channels
    2. EmailAPI Service:Endpoints: ConfiguredSpecific forendpoint emailURLs delivery
    3. SMSand Gateway:authentication Active for SMS notifications
    4. Database: Populated with test data
    5. Authentication Service: User roles configured



    6. TRACEABILITY MATRIX

      Requirements Coverage:

      Acceptance Criteria

      Test Cases

      Coverage

      AC-1: Workflow creation UI

      TC_001, TC_002, TC_003

      Complete

      AC-2: Time/Event triggers

      TC_002, TC_003, TC_019

      Complete

      AC-3: Multi-channel support

      TC_004, TC_020

      Complete

      AC-4: Character limits

      TC_012

      Complete

      AC-5: Sequential actions

      TC_004

      Complete

      AC-6: Template integration

      TC_005

      Complete

      AC-7: Workflow editing

      TC_006

      Complete

      AC-8: Execution tracking

      TC_009, TC_010

      Complete

      AC-9: Performance metrics

      TC_010, TC_015, TC_016

      Complete

      AC-10: Status filtering

      TC_007

      Complete

      AC-11: Search functionality

      TC_008

      Complete

      AC-12: Error handling

      TC_011, TC_012

      Complete

      AC-13: Cross-browser

      TC_013, TC_014

      Complete

      AC-14: Security

      TC_017, TC_018

      Complete

      AC-15: Integration

      TC_019, TC_020

      Complete




      RISK ASSESSMENT

      High-Risk Areas:

      1. Workflow Execution Engine - Core business functionality
      2. External System Integration - Dependency on third-party systems
      3. Email Delivery - Critical for customer communicationmethods
      4. Performance Under LoadThresholds: -Confirmation Scalabilityof concernsperformance standards vs. <1 second requirement
      5. DataIntegration SecurityPoints: -Specific Complianceexternal systems and privacytheir integration requirements

      Mitigation Strategies:

      1. Comprehensive Integration Testing - Validate all external connections
      2. Performance Testing - Load testing with realistic user volumes
      3. Security Testing - Regular security audits and penetration testing
      4. Monitoring and Alerting - Real-time system health monitoring
      5. Disaster Recovery - Backup and recovery procedures tested




      This comprehensive test suite providesnow completealigns coveragewith forall your specified requirements and includes the Communicationupdated Workflowsfunctionality feature,while supportingmaintaining allthe 17quality BrowserStack test management reports with detailed traceability, performance benchmarks, and risk assessmentstandards for a B2B utility SaaS product.