Screen Transition Diagram for Exploratory Testing Auditability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Exploratory testing lacks auditability due to the absence of a testing design book, making it difficult to confirm testing procedures and reducing the efficiency of finding system problems, especially in projects where auditability is crucial.
Innovation Solution
A testing device with a first update unit for updating screen transition diagrams and a second update unit for dividing or integrating nodes in the diagrams based on user operations, allowing for efficient exploratory testing with reduced man-hours.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If exploratory testing is performed without a testing design book, then testing efficiency and problem detection capability are improved, but auditability deteriorates
Solution Approach 1:
The patent creates a visual copy (screen transition diagram) of the testing process that automatically records and displays the testing flow, screen transitions, and test results. This diagram serves as an audit trail without requiring manual documentation, thus maintaining auditability while preserving the efficiency of exploratory testing.
Solution Approach 2:
The screen transition diagram acts as an intermediary between the exploratory testing process and audit requirements. It automatically captures testing activities and presents them in a structured visual format, bridging the gap between flexible exploratory testing and formal auditability requirements.
2Loss of information
If script testing is used to ensure auditability, then auditability is improved, but testing efficiency and flexibility deteriorate
Solution Approach 1:
Instead of requiring testers to manually create documentation (traditional approach), the patent inverts the process by automatically generating the screen transition diagram from observed testing activities. The documentation is created by the system rather than by manual effort, reversing who performs the documentation task.
Solution Approach 2:
The testing system performs self-documentation by automatically recording testing activities, screen transitions, and results in the screen transition diagram. This eliminates the need for separate manual documentation efforts, allowing the system to serve its own auditability needs without external intervention.
3Loss of information
If manual documentation is performed during exploratory testing, then auditability is improved, but man-hour and time consumption increase
Solution Approach 1:
The patent performs preliminary action by automatically capturing and recording testing activities as they occur, rather than requiring post-testing documentation. The screen transition diagram is built incrementally during the testing process itself, eliminating the need for separate documentation time.
Solution Approach 2:
The system maintains continuous recording of testing activities throughout the exploratory testing process. The screen transition diagram is continuously updated as testers navigate through screens, ensuring that documentation is an ongoing automatic process rather than a discrete time-consuming task.
Data Source
AI summary
A testing device includes: a first update unit that updates a screen transition diagram that is displayed on a display device and shows a transition of a screen state according to input of an operation on a screen relating to a program to be tested; and a second update unit that divides or integrates a node according to an operation of the node for each screen or each screen state in the screen transition diagram. Thus, the testing device makes it possible to obtain the advantage of exploratory testing while reducing a man-hour to perform the exploratory testing.


