Script-Free End-to-End Test Automation Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing test automation tools require scripting and do not support end-to-end testing, are not customizable for multiple platforms, and cannot reuse test setups across different tools, limiting their effectiveness in performing various types of testing, including performance testing and functional validations.

Innovation Solution

A system and method for automating end-to-end testing without scripting, which includes a connection settings module for external systems, a test setup module for creating workflows by mapping source and target files, and a workflow execution module that retrieves and executes test workflows, generating results and facilitating reporting across multiple platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If conventional test automation tools are used, then testing can be automated to some extent, but scripting is required which increases complexity and reduces ease of operation

Engineering Contradiction:
Improvetesting automationVSAvoidscripting complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system performs repetitive testing tasks automatically without requiring human-written scripts. The test automation framework executes tests by itself based on predefined configurations, eliminating the need for testers to write and maintain complex scripting code while achieving comprehensive automation coverage

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary layer between the tester and the test execution engine. This intermediary framework translates simple test configurations into automated test actions, acting as a mediator that eliminates the need for direct scripting while maintaining automation capabilities

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If specialized test automation tools are used for specific testing types, then that specific testing can be performed, but the tools cannot support multiple testing types and platforms

Engineering Contradiction:
Improvetesting coverageVSAvoidplatform compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The test automation framework is designed with universal capabilities to perform multiple types of testing including functional, integration, performance, and compatibility testing across diverse platforms. A single unified tool provides multi-functional testing capabilities rather than requiring separate specialized tools for each testing type

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The framework employs dynamic configuration and adaptive execution capabilities that allow it to adjust to different testing requirements and platforms. The system can dynamically load appropriate test modules and configurations based on the target platform and testing type, providing versatile adaptability across multiple environments

Inventive Principle:
Principle #15Dynamics

3Reliability

If test setups are created for each testing activity, then testing can be performed, but the setups cannot be reused across different testing activities and tools

Engineering Contradiction:
Improvetesting accuracyVSAvoidsetup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The framework pre-configures test environments, data sets, and execution parameters in advance through reusable templates and configurations. These preliminary setups are prepared once and can be automatically loaded and adapted for multiple testing activities, eliminating the need to recreate setups for each test run

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables copying and reusing of test configurations, templates, and setups across different testing activities and platforms. Pre-defined test patterns and configurations can be replicated and adapted to new testing scenarios, reducing setup time while maintaining testing accuracy through consistent configuration reuse

Inventive Principle:
Principle #26Copying

4Productivity

If existing test automation tools are used, then some testing functions can be automated, but end-to-end testing without scripting is not supported

Engineering Contradiction:
Improvetesting efficiencyVSAvoidoperational simplicity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The framework achieves complete end-to-end test automation by performing all testing operations automatically without requiring any scripting. The system self-manages test execution, data validation, result collection, and reporting throughout the entire testing workflow, maximizing productivity while maintaining operational simplicity

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent merges multiple testing functions and operations into a unified end-to-end automation workflow. By combining configuration, execution, validation, and reporting into a single integrated process that requires no scripting, the system achieves both high productivity and ease of operation simultaneously

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10013339B2System and method for automating testing without scripting
Publication Date: 2018.07.03 COGNIZANT TECH SOLUTIONS INDIA PVT LTD
  • US10013339B2 patent drawing
  • US10013339B2 patent drawing
  • US10013339B2 patent drawing

AI summary

A system and computer-implemented method for automating end-to end testing is provided. The system comprises a connection settings module to receive information for connecting with one or more external systems. The system further comprises a test setup module to create test workflows, wherein creating the test workflows comprise selecting one or more pre-stored source files and corresponding one or more pre-stored target files and mapping input and output of each of the one or more selected pre-stored source files with the corresponding one or more selected pre-stored target files for testing additional source files associated with the one or more external systems. Furthermore, the system comprises a workflow execution module to connect with the one or more external systems using the received information to retrieve the additional source files and execute the created test workflows corresponding to the retrieved one or more additional source files.