DevSecOps Continuous Testing With Automatic Test Trigger Mapping

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Continuous testing within a DevSecOps pipeline is not truly continuous due to manual triggering of tests, leading to inefficiencies and resource wastage, especially in large or complex applications with varied release cycles.

Innovation Solution

A system and method for automating the mapping of automated tests to commands and parameters, enabling automatic triggering based on defined criteria and conditions within the DevSecOps pipeline, ensuring seamless integration and resource optimization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual triggering of tests is used, then tests can be selectively executed for specific application releases, but significant delays occur and computing resources are used inefficiently

Engineering Contradiction:

Improvetesting efficiencyVSAvoidtesting delay

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-configuring test automation code bases, mapping tests to command-line commands and parameters, and establishing trigger conditions before actual testing is needed. This preparation enables automatic triggering without manual intervention, eliminating delays while maintaining selective test execution capability.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements self-service by automatically detecting trigger conditions (such as code commits or release events), selecting appropriate test suites, and executing tests without human intervention. The pipeline autonomously manages the entire testing process, from trigger detection to test execution and result reporting, thereby eliminating manual triggering delays.

Inventive Principle:

Principle #25Self-service

2Adaptability or versatility

If a single test automation code base contains tests for multiple applications, then test coverage is comprehensive, but only specific tests can be triggered manually for particular releases

Engineering Contradiction:

Improvetest coverageVSAvoidautomatic test selection

Core Design Contradiction:

Adaptability or versatilityVSExtent of automation

Solution Approach 1:

The system segments the test automation code base by organizing tests into modular units associated with specific applications or components. Each test suite is tagged with metadata identifying its target application, enabling the system to automatically select and execute only the relevant tests for a given release, thus achieving both comprehensive coverage and precise automatic selection.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system implements dynamic test selection by using configurable trigger conditions and parameters that adapt to different release scenarios. The pipeline dynamically determines which tests to execute based on the specific application being released, the type of code change detected, and predefined criteria, enabling flexible automatic test selection without manual intervention.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS20250321868A1System and method for continuous testing within a devsecops pipeline

Publication Date: 2025.10.16 THE TORONTO DOMINION BANK

AI summary

A computer system comprising at least one processor; and a memory coupled to the at least one processor and storing processor-executable instructions which, when executed by the at least one processor, configure the at least one processor to define at least one test automation code base associated with a continuous testing cycle; for the at least one test automation code base, define at least one automated test and criteria associated with the at least one automated test; and map the at least one automated test to a command and parameter to trigger the at least one automated test.