Home

A tool to compute test paths of Java methods and constructors.

---

Calculating the code coverage of a test suite depends on the identification of the executed test paths. Available code coverage tools are limited to a few basic tracing strategies and do not provide this information as proper test paths, precluding its use in further analyses. ExecutionFlow aims to generate the test paths of a project at the method level in a suitable format to be manipulated and used for different analysis. It relies on the use of aspect-oriented programming (AOP) to collect information concerning the methods and constructors covered by one or more test methods, a debugger for inspecting the code and a test framework for executing the test method.

⚠ Warnings

• If it is necessary to stop the application from running, use the Stop button in the ExecutionFlow window (See more). If you interrupt by another way (such as the eclipse stop button) and the original files are not restored, check the troubleshooting section before opening an issue.
• Not compatible with projects that use gradle
• Do not modify the source file while the application is running, as it may interfere with file processing
• It is mandatory to have 'src' directory in the project root

See all limitations and important notices here.

🕑 Runtime

The time to compute the test path depends on three factors:

• Size of the file containing the test method of the method / constructor to be generated test path
• Size of the file containing the method / constructor to be generated the test path
• Number of instructions the method executes