Tests & debugging
Run, test and read the results
Repeatable profiles, test cases, coverage and rerunning failures.
Make a run repeatable#
Project profiles retain directories, variables and commands, runnable sequentially or in parallel. Follow output and status and stop the process started by the IDE. Creating a profile does not install tools or start the program.
- Open Run and prepare a profile with the project directory and commands.
- Check required SDKs and dependencies, then start explicitly.
- Read the output and open recognized source locations or the Problems panel.
From the summary to the failing case#
The Test panel discovers supported projects, including Node, Vitest, pytest, xUnit, Jest, JUnit and PHPUnit. Framework runtimes and dependencies must be available. Results distinguish passing, failing and skipped cases; filter or rerun the failures.
Where supported, coverage links lines to sources, and affected-test runs use project dependencies. An earlier result does not prove the state of sources changed after that run.
If a filter finds no cases#
Filters follow the framework: Jest uses a name expression, JUnit can use Class#method and xUnit uses VSTest expressions. Check the selected project and syntax before concluding that a test does not exist. An empty filter result is reported and must not be interpreted as a passing suite.