Multi-Entity Test Case Workflow Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing large-scale software testing processes is cumbersome and resource-intensive due to the complexity of tracking multiple test cases, roles, and results across various stages, especially in environments with multiple personnel and vast numbers of test cases.

Innovation Solution

Implementing a Multi-Entity Test Case (METC) execution workflow that assigns roles to test steps based on privilege levels, defines failure conditions, and specifies failure actions to automate and digitize the testing process, enhancing traceability and logging through a User Interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual test case management is used for large-scale software testing, then flexibility and adaptability are maintained, but the process becomes cumbersome and time-consuming

Engineering Contradiction:
Improvetesting efficiencyVSAvoidtime for managing test cases
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system enables self-service automation where the testing process automatically manages itself through defined workflows. Test cases are automatically executed, results are automatically logged, and notifications are automatically sent to relevant users, eliminating the need for manual intervention in routine testing tasks while maintaining flexibility through configurable workflows and role-based access control

Inventive Principle:
Principle #25Self-service

2Reliability

If multiple personnel are involved in testing with vast numbers of test cases, then comprehensive coverage is achieved, but tracking and management becomes complex

Engineering Contradiction:
Improvetesting coverageVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the testing process into distinct test steps with specific roles assigned to each step. This segmentation allows different personnel to be responsible for different aspects of testing while the system automatically tracks and manages the overall process. Each test case is broken down into manageable steps that can be independently executed and tracked, reducing the complexity of managing large-scale testing across multiple users

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system acts as an intermediary between multiple test personnel and the test cases. It provides a centralized platform that manages test case assignments, tracks execution status, logs results, and communicates with all users involved. This intermediary role simplifies the complex interactions between multiple testers and ensures comprehensive tracking without requiring direct coordination between all personnel

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If automated test framework is used, then execution speed increases, but setup and configuration becomes resource-intensive

Engineering Contradiction:
Improvetest execution speedVSAvoidframework configuration
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system performs preliminary configuration by allowing users to define test workflows, assign roles, and set up execution parameters before actual testing begins. Once configured, the automated framework executes test cases at high speed without requiring repeated setup. The preliminary action of defining the testing structure enables rapid execution while minimizing ongoing configuration overhead

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8938648B2Multi-entity test case execution workflow
Publication Date: 2015.01.20 TATA CONSULTANCY SERVICES LTD
  • US8938648B2 patent drawing
  • US8938648B2 patent drawing
  • US8938648B2 patent drawing

AI summary

The present subject matter relates to a method for managing a testing workflow, based on execution of at least one Multi Entity Test Case (METC) of the testing workflow. The method includes assigning at least one role to each of a plurality of test steps of the METC, where the at least one role is indicative of a privilege level to execute each of the plurality of test steps. The method also includes defining a failure condition for each of the plurality of test steps, where the failure condition is indicative of an expected result of execution of each of the plurality of test steps. The method further includes specifying a failure action associated with the failure condition for execution of each of the plurality of test steps, executing one of the plurality of test steps, and applying the failure action to proceed with the testing workflow.