Skip to content

Continuous Testing

Quarkus revolutionized Java testing with Continuous Testing, running tests that cover the code you touched in the background. Quarkus Studio brings this directly into the VS Code interface.


When editing a test class (*Test.java), Quarkus Studio renders real-time pass/fail icons directly in the editor gutter:

  • 🟢 Passed: Indicates the test method passed in the latest continuous testing run.
  • 🔴 Failed: Indicates the test method failed. Hovering over the icon displays the assertion error and stack trace tooltip.
  • 🟡 Skipped / Paused: Indicates paused or excluded tests.

Quarkus Studio injects a continuous testing status indicator in the VS Code Status Bar:

Quarkus Tests: 42 Passed | 1 Failed | 0 Skipped

Clicking the HUD allows you to quickly toggle test execution, pause testing, or rerun the test suite.


When quarkusStudio.continuousTesting.rerunOnSave is enabled (default true), modifying and saving any Java or configuration file automatically triggers re-execution of previously failed tests.

Interactive CodeLens buttons appear above each test class and test method:

  • Run Test: Executes only this specific test method.
  • Rerun Failed: Instantly triggers re-testing for failing tests without executing the entire suite.

Quarkus allows swapping runtime configuration and mocking services via @TestProfile.

Use the command Quarkus Studio: Switch Test Profile (quarkus-studio.continuousTesting.switchProfile) to:

  • Pick from available @TestProfile implementations in the workspace.
  • Scaffold a new @TestProfile class.
  • Temporarily disable profile overrides.

While the Quarkus dev mode terminal is active, you can also use native Quarkus hotkeys:

Key Action
r Rerun all tests
f Rerun only failed tests
t Toggle continuous testing on/off
p Pause continuous testing
b Toggle broken-only mode
h View terminal help menu