Test Management System for Software Documentation Automation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional static files used for software testing documentation are difficult to manage, especially as the number of files grows, making it challenging to track changes, identify test cycle scope, and collect statistics for Quality Assurance activities.

Innovation Solution

A computer-implemented method for generating and managing test documentation that includes creating test templates, scenarios, and cases, associating them, executing test cycles, and storing results in a database, with features like filtering and priority levels, and providing an API for integration with automated testing software.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If conventional static files are used for test documentation, then ease of manufacture is improved, but device complexity worsens as the number of files grows large

Engineering Contradiction:

Improveease of creating test documentationVSAvoidcomplexity of managing test documentation

Core Design Contradiction:

Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent merges multiple static test documentation files into a single integrated test management system that centralizes test plans, test cases, and results. This consolidation reduces the complexity of managing numerous separate files while maintaining ease of documentation creation through standardized templates and automated workflows.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The test management system provides multi-functionality by handling test plan creation, test case execution, result tracking, and statistical analysis within a single platform. This universal system replaces multiple separate static files with one system that performs all test documentation functions, reducing management complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If the number of static test files increases, then completeness of test coverage is improved, but ease of operation worsens due to difficulty in tracking changes and collecting statistics

Engineering Contradiction:

Improvecompleteness of test coverageVSAvoidease of tracking changes and collecting statistics

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system implements automated feedback mechanisms that track test execution results, change histories, and statistical metrics across all test files. This centralized feedback system allows users to monitor test coverage completeness and track changes automatically, eliminating the manual effort required when managing numerous static files.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary test management system that acts as a mediator between individual test files and users. This system provides centralized tracking, filtering, and statistical collection capabilities, making it easy to monitor test coverage and track changes across all test documentation without manually managing each file.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Loss of information

If static files are used for test results, then loss of information is minimized, but productivity worsens due to difficulty in managing and analyzing test data

Engineering Contradiction:

Improvepreservation of test dataVSAvoidproductivity of test management activities

Core Design Contradiction:

Loss of informationVSProductivity

Solution Approach 1:

The patent replaces manual mechanical processes of copying, pasting, and analyzing test data from static files with automated electronic systems. The test management system automatically captures, stores, and analyzes test results, eliminating manual data handling while preserving all test information and significantly improving management productivity.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system implements automated copying and replication of test results from execution environments to centralized storage, ensuring complete data preservation without manual intervention. This automated copying mechanism maintains data integrity while freeing up productivity by eliminating manual data transfer tasks.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS7913230B2Computer-implemented methods and systems for generating software testing documentation and test results management system using same

Publication Date: 2011.03.22 ORACLE INT CORP

AI summary

A computer-implemented method for generating and managing test documentation for a software product may include steps of generating a test template; generating at least one test scenario for each of a plurality of functional areas, each test scenario being configured to test a business flow that mimics how an end user would use the software product; associating the generated test scenario(s) with the generated test template; generating at least one test case that includes a plurality of test steps; associating the generated test case(s) with the generated test template; copying the test template to generate test results, the generated test results being independent of the generated test template, and carrying out a test cycle by executing the test scenario(s) and the test case(s) associated with the generated test results of the generated test template and storing the results of the executed test scenario(s) and the executed test case(s) in a database.