Testing
Explyt helps you create tests, measure and increase coverage, investigate unstable runs, and work with test cases from a TMS. Choose a feature by the underlying task, not just by the type of test.
What to choose
| If you need to | Use |
|---|---|
| Find uncovered lines and branches and add tests that exercise them | Increase test coverage |
| Get a test from the data of a real run of Java or Kotlin code | Test generation from execution |
| Find out why a test sometimes passes and sometimes fails | Flaky test analysis |
| Connect Allure TestOps | TMS integration |
For regular test generation and refinement, use the Test mode. Availability of individual capabilities depends on the IDE and the language — check the feature matrix.
How to check generated tests
- Make sure the test pins down specific behavior and contains meaningful assertions.
- Run the narrowest test configuration through the IDE.
- Check the neighboring tests and the build if the change touches shared code.
- Review the generated files in Agent Changes.
- Do not accept a test just because the coverage percentage went up.
Practical tasks
- Add tests
- Increase test coverage
- Fix a flaky test
- Create a test from a real run
- Refactor without changing behavior
To run tests and builds, use IDE run configurations: they work with the SDK and the environment already set up in the project.