In TestSprite, you can work with interface and API checks, see the results of execution and run repeated checks. Portal and integration are available.
One scenario with visible results
When testing a site, it is useful to start with an action that changes the data. For example, the user creates a draft and after reboot sees the former name. TestSprite supports scripts for the interface and API. For the first run, prepare a separate account and specify what sign is confirmed success. Opening the page by itself does not prove that the changes have survived.
In the report, compare the step at which the failure occurred with the task. Falling when the test server is unavailable and a save error are different reasons. It is easy to confuse them by launch status alone.
Draft form in the training application
Describe two tests. In the first, the user saves the completed form and opens it again. The second sends the form with an empty mandatory field and receives the expected error. Prepare an initial state for each launch. If both checks use the same account, remove the test draft or set a new name before repeating.
If the interface changes address after saving, separately check whether the test saves the original record ID. Otherwise, he may accidentally open someone else's draft and pass the check on a suitable title.
Separate API verification
For the software interface, you can specify expected statuses, response structure, and query sequence. Verify the final checks with the specification. It is not necessary to send data from the work circuit to the environment prepared for experiments.
Suitable tasks
- Check user action in the test interface
- Run a script with multiple API requests
Strengths
- There are checks of the interface and software interfaces
- Documented test run and report view
Limitations
- The test environment should be available for launch
- Falling script requires checking the state of data and environment
Selection and conditions
- Free access
- Not confirmed
- Trial period
- Not confirmed
- No sign-up required
- Not confirmed
- Russian interface
- Not confirmed
- Local installation
- Not confirmed
- API
- Not confirmed
“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 are plans with different limits. Before regular start-up, specify the terms of expenditure of test credits. Falling script requires checking the state of data and environmentFrom task to first result
Practical example
- Task
- Check user action in the test interface
- What to prepare
- The address of the learning environment, the test account, the form fields and the sign of the saved draft.
Task brief or prompt
Check the preservation of the filled draft and the failure with an empty mandatory field. After successful saving, open the record again by its identifier.
Expected result
Two scenarios with separate initial conditions and performance report.
How to check the result
- Review the steps and actual answers in the report.
- Check that the restart does not use someone else's draft.
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
This description is based on the developer’s material. Features, prices and availability may change; check the primary source before use.