BDD Automation Framework Generation via Preliminary Action

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Agile software development teams face challenges with manual or limited automation, leading to implementation backlogs, delayed timelines, and increased operational bugs.

Innovation Solution

The system and method for computer-implemented agile software development, testing, and implementation provide an interactive interface and generation tool that automates the creation of a BDD application framework, including step definition files, data payloads, and schema verification, thereby streamlining the automation development process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual or limited automation is used, then implementation backlogs increase and timelines are delayed, but automation complexity and initial effort are reduced

Engineering Contradiction:
Improveautomation development speedVSAvoidautomation framework complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by automatically generating the complete BDD automation framework structure, including feature files, step definition files, and test configurations, before the user begins actual testing work. This pre-generation of framework components eliminates the need for manual setup and reduces initial complexity barriers.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates standardized templates and copies of proven automation patterns, feature files, and test structures that can be rapidly replicated across different test scenarios. This allows teams to leverage existing successful frameworks rather than building from scratch, reducing complexity while maintaining effectiveness.

Inventive Principle:
Principle #26Copying

2Productivity

If manual testing is used, then implementation backlogs increase, but automation setup time and resource investment are reduced

Engineering Contradiction:
Improvetesting throughputVSAvoidautomation setup time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system executes preliminary actions to automatically configure the entire automation environment, generate feature files from requirements, create step definition templates, and set up test execution frameworks before actual testing begins. This pre-preparation eliminates time-consuming manual setup and enables rapid testing throughput.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system replaces manual mechanical processes of framework setup, file creation, and configuration with automated computational processes. The automated system generates code, configurations, and test structures that would otherwise require extensive manual writing and setup, significantly reducing setup time while enabling higher testing throughput.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If limited automation is implemented, then operational bugs increase, but automation maintenance and updates are simplified

Engineering Contradiction:
Improvesoftware qualityVSAvoidautomation framework structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The automation framework is segmented into distinct, modular components including feature files for test scenarios, step definition files for execution logic, and configuration files for setup. This segmentation allows each component to be independently maintained and updated, improving reliability while keeping the overall structure manageable through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system incorporates feedback mechanisms that automatically verify framework consistency, validate feature files against step definitions, and ensure proper configuration. This continuous feedback validation maintains high software quality by detecting issues early, while the automated feedback loops simplify maintenance by providing clear guidance on needed updates.

Inventive Principle:
Principle #23Feedback

4Productivity

If no automation framework is used, then development cycles are faster initially, but implementation backlogs and operational bugs increase

Engineering Contradiction:
Improvedevelopment cycle speedVSAvoidoperational bug rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions to automatically generate comprehensive automation frameworks that cover all critical test scenarios before development cycles begin. This pre-established framework enables rapid iteration while maintaining high reliability through automated validation and testing, preventing operational bugs from accumulating.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The automation framework is designed with universal applicability, serving multiple functions including test execution, validation, regression testing, and quality assurance. This multi-functionality allows a single framework to support various development needs, maintaining fast development cycles while improving reliability through comprehensive automated coverage.

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

Data Source

PatentUS12321256B1Behavior data driven automation test code generating system and method
Publication Date: 2025.06.03 MORGAN STANLEY SERVICES GROUP INC
  • US12321256B1 patent drawing
  • US12321256B1 patent drawing
  • US12321256B1 patent drawing

AI summary

Computer-implemented agile software development, testing, and implementation are provided. At least one computing device accesses at least one input file and processes the file(s) to generate an application framework including a plurality of files. An interactive interface including selectable options associated with the respectively accessible folders is provided. Via the interactive interface, editable access to each of the plurality of files is provided and the at least one computing device receives, via the interface, at least one edit to at least one of the files. A testing case of the generated application framework is generated, includes step definition files. The at least one computing device tests the generated application framework by stepping through automation provided by the generated application framework as a function of the step definition files. Moreover, the at least one computing device generates reporting associated with the testing of the generated application framework.