Generating Test Designs from Design Documents
Overview
When a user attaches a design document in Word format to a chat message, the agent analyzes the contents of the design document and creates test cases in an Excel file based on the test perspectives defined in the system prompt.
This sample data aims to demonstrate a use case for streamlining development by utilizing design information across different stages.
What this sample can do
- Generate a draft test specification based on a design document in Word format
- Consider test perspectives such as normal, abnormal, and boundary values when generating test cases
- Output test specifications to the active Excel file
Target Users
This sample is primarily intended for the following users:
- Developers and testers who design test cases based on design documents
- Teams considering streamlining test design work
- Those who want to see examples of business automation across Office tools (Word/Excel)
Contents Included
This sample includes the following data as an example:
| Data | Filename |
|---|---|
| Agent Definition | Generate Test Design from Design Document.yaml |
| Input: Word Design Document | inputData/ADAS ECU Software Design Document.docx |
| Documentation | This README |
Using Sample Data
Prerequisites
- The Excel file that will be the output destination for the test specifications must be active.
Input/Output
- Input: Word format design document file
- Output: Writing test cases to the active Excel file
Procedure
- Open the Excel file containing the test specifications to be output and make it active.
- On the Agentiqs agent screen, hover your mouse over "Generate Test Design from Design Document" and click "Start Chat".
- In the Agentiqs chat screen, attach the Word design document that will serve as the input example.
- Instruct the agent to create the test specifications via chat.
- "Create test specifications in the active Excel file for the attached design document."
Target
- Agent: Generates test designs from design documents
Constraints
- Output content depends on the content of the input design document.
- Example: If the design document is not structurally well-written, it may not be able to be analyzed correctly, and the accuracy of the generated test cases may decrease.