Keploy supports agent generation of tests API and recording interactions with subsequent playback. These modes help to work with the specification and current behavior of the service.
Two ways to collect initial checks
Keploy allows you to create scripts API for the description of the interface and play recorded interactions. If the team changes a new contract, start with its specification. If you need to save the behavior of an already working service before refactoring, recording in a test environment will be useful. The scripts have different starting points. In the first case, the check is compared with the requirements, in the second it is important to notice if the record reflects an old error.
Before generating, check the structure of the request and response examples. The unwritten error code in the specification easily turns into an empty statement that the request simply ended.
Training example with repeated request
Take the booking API and a description of the cancellation operation. Make a scenario in which a reservation is first created and then a cancellation request is sent twice. Check which statuses and data are returned in both cases. The result of the second request must be in accordance with the contract. If the condition in the contract is not yet defined, agree it before adding the test.
To rerun the scenario in CI, set up a way to create a fresh record or restore the test database to its initial state. Otherwise the first run may pass and the next run may pick up a booking that was already canceled.
Record interactions
A separate mode Keploy captures the requests and responses of dependencies for playback. Before recording, replace the keys and customer data with training values. At the acceptance, open the statements and check that the modified answer really leads to the fall of the desired test.
Suitable tasks
- Check API contract on the training scenario
- Play recorded interaction when changing service
Strengths
- Supports script generation by API description
- There is a separate record-and-replay workflow
Limitations
- Record reflects the behavior that was observed at the time of capture
- Account data and query bodies should be prepared in a test environment
Selection and conditions
- Free access
- Yes
- Trial period
- Not confirmed
- No sign-up required
- Not confirmed
- Russian interface
- Not confirmed
- Local installation
- Not confirmed
- API
- Yes
“Not confirmed” means there is not enough information. The feature may still be available; check the developer’s terms.
- Input formats
- Code, Text
- Result
- Code, Text
Terms
There is a free dating option and paid plans. The use of models and command capabilities depend on the plan and mode. Account data and query bodies should be prepared in a test environmentFrom task to first result
Practical example
- Task
- Check API contract on the training scenario
- What to prepare
- A description of the booking cancellation, test credentials, and the expected response to a repeated request.
Task brief or prompt
Make checks to create and two consecutive cancellations of one reservation. Match the answers to the specification and save the identifier from the first step.
Expected result
A test scenario with a repeatable initial state and verification of both responses.
How to check the result
- Make sure the restart gets a new test record.
- Change the expected status and check that the desired test falls.
An editorial teaching example of a task brief, not the result of hands-on testing of the service. Check that the required mode is available, that you have rights to the source material and that the intended use of the result is permitted.
Check details
Official sources
- Keploy Page
- Guide to Agent Test Generation
- Help for recording and reproducing requests
- Terms of access and payment
- Public REST API Keploy
This description is based on the developer’s material. Features, prices and availability may change; check the primary source before use.