Automated Test Case Generation from Agile Voice Conversations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In agile software development, converting voice conversations from meetings into test scenarios is challenging due to the lack of a holistic view of requirements, leading to defects escaping to production, as the process is often voice-based and not well-documented, making it difficult to intelligently and automatically generate test cases.

Innovation Solution

A computing platform with a natural language processing engine identifies and maps voice data from agile development meetings to software development project requirements, generating, prioritizing, and executing test cases, and optimizing system performance using an artificial-intelligence engine.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If test cases are manually generated from voice-based agile meetings, then test coverage may be achieved, but the process is time-consuming and prone to human error

Engineering Contradiction:
Improvetest case accuracyVSAvoidtime for test case generation
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces the manual mechanical process of transcribing and analyzing voice meetings with an automated system using voice recognition engines and natural language processing. The system automatically converts voice data to text, extracts requirements, generates test cases, and maps them to task items, eliminating manual intervention and significantly reducing time while maintaining or improving accuracy.

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

Solution Approach 2:

The system enables self-service by automatically processing voice meeting data without requiring manual input from testers or developers. The automated generation and mapping of test cases from voice conversations allows the system to serve itself, reducing dependency on human resources for this repetitive task.

Inventive Principle:
Principle #25Self-service

2Reliability

If individual testers or developers convert conversations to test scenarios, then some test cases are created, but a holistic view of requirements is difficult to achieve leading to defects escaping

Engineering Contradiction:
Improvedefect detectionVSAvoidholistic view of requirements
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system provides a universal platform that processes all voice meeting data across the entire development team, rather than relying on individual testers or developers. It performs multiple functions including voice-to-text conversion, requirement extraction, test case generation, and automatic mapping to task items, ensuring comprehensive coverage of all requirements from a holistic perspective.

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

Solution Approach 2:

The system implements feedback mechanisms by automatically mapping generated test cases to task items and tracking their execution status. This closed-loop feedback ensures that all requirements discussed in meetings are captured, tested, and verified, preventing defects from escaping to production.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If voice-based agile meetings are used for collaboration, then team collaboration is improved, but automatic test case generation becomes difficult due to lack of documentation

Engineering Contradiction:
Improveteam collaborationVSAvoidtest case generation process
Core Design Contradiction:
Ease of operationVSEase of manufacture

Solution Approach 1:

The patent replaces the manual documentation process with automated voice recognition and natural language processing. The system directly converts voice meetings into structured test cases without requiring manual transcription or documentation, making the process as easy as holding a voice meeting while automatically generating testable requirements.

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

Solution Approach 2:

The system introduces an intermediary layer (voice recognition engine and NLP processor) between the voice meeting and test case generation. This intermediary automatically translates unstructured voice conversations into structured test cases, bridging the gap between informal collaboration and formal testing requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11709765B1Intelligent test cases generation based on voice conversation
Publication Date: 2023.07.25 BANK OF AMERICA CORP
  • US11709765B1 patent drawing
  • US11709765B1 patent drawing
  • US11709765B1 patent drawing

AI summary

Aspects of the disclosure relate to generating test cases based on voice conversation. In some embodiments, a computing platform may receive voice data associated with an agile development meeting. Subsequently, the computing platform may identify, using a natural language processing engine, context of one or more requirements being discussed during the agile development meeting. Based on identifying the context of the one or more requirements being discussed during the agile development meeting, the computing platform may store context data into a database. Next, the computing platform may map the context data to a corresponding task item of a software development project. Thereafter, the computing platform may identify one or more test cases to be generated. Then, the computing platform may cause the identified test cases to be executed.