Building Tests with AI
Ora can create entire test automation projects or augment existing ones. It understands test structure (project → suite → case → step) and can generate complete, runnable test suites. Request filling and test-structure creation are handled by the TestBuilder specialist; structured test-design analysis is handled by the TestDesigner specialist.
Screenshot: Test Automation view with the Ora panel showing a generated suite and its test cases.
Creating a Test Project
"Create a new test automation project called 'User Management API Tests'"
Ora creates the .aprj project with proper structure — or prompts you for missing details (output directory, environment, etc.).
Generating Test Suites
Describe what you want to test, and Ora generates a suite with test cases:
"Create a test suite for the User API that covers CRUD operations"
"Generate smoke tests for all endpoints in this specification"
"Run all tests in the current suite and summarise the failures"
Designing Test Cases (ISTQB)
When you ask for coverage or combinations, Ora dispatches the TestDesigner specialist, which applies professional ISTQB techniques:
- Equivalence partitioning
- Boundary value analysis
- Pairwise / combinatorial testing
- Decision tables
- State transition testing
- MC/DC and other coverage techniques
The TestDesigner's design parameters are forwarded automatically to TestBuilder via working memory, so the implementation step skips redundant discovery.
Building Test Cases
Each test case contains a sequence of test steps. Ora creates them complete with assertions:
"Create a test case that creates a user, verifies the response, then deletes the user"
Ora generates:
- Send Request step —
POST /userswith a generated body - Assertion — status code 201, body contains a user ID
- Data Transfer — extract the user ID to a variable
- Send Request step —
DELETE /users/${userId} - Assertion — status code 204
Adding Test Steps
Modify existing tests conversationally:
"Add a JWT generation step before the request"
"Insert a wait step of 2 seconds between these two requests"
"Add a SQL query to verify the user was saved in the database"
Ora knows the step catalog and inserts the correct step type with appropriate configuration.
Data-Driven Testing
"Make this test data-driven with a CSV file containing 50 user records"
"Add random data generation for the email and username fields"
Ora converts the case to a data-driven test case and wires up the data source, mapping rules, and loop markers.
Load Testing
"Convert this test suite into a load test with 100 concurrent users for 5 minutes"
Load-test configuration with AI assistance is in active development. Manual configuration via the load test editor is recommended for production scenarios.
Tips
- Start with a small, specific request and iterate — "Create a test for login" works better than "Test the entire API".
- Reference the project/suite/case by name so Ora acts on the right item (with multiple projects loaded, Ora asks which one).
- Review generated steps before running — Ora explains its choices, but you have the final say.