Skip to content

fix: use correct Surefire user property for engine filtering - #4

Merged
arun279 merged 1 commit into
mainfrom
fix/surefire-engine-property-name
Apr 14, 2026
Merged

fix: use correct Surefire user property for engine filtering#4
arun279 merged 1 commit into
mainfrom
fix/surefire-engine-property-name

Conversation

@arun279

@arun279 arun279 commented Apr 14, 2026

Copy link
Copy Markdown
Owner

Summary

  • Fix engine filtering property from includejunit5engines to surefire.includeJUnit5Engines
  • The wrong name was silently ignored by Surefire, so all test engines still ran
  • Correct property name confirmed from Surefire test-mojo reference and SUREFIRE-2059
  • Bumps version to 0.1.3

Test plan

  • Install updated extension on Windows machine with the test project
  • Run a single scenario — verify only the Cucumber engine executes (no other test classes run)
  • Verify test results are found and displayed correctly

The property name is surefire.includeJUnit5Engines, not
includejunit5engines. The wrong name was silently ignored by Surefire,
causing all test engines to run. Fixed in SUREFIRE-2059.
@arun279
arun279 merged commit ea6f0a4 into main Apr 14, 2026
1 check passed
@arun279
arun279 deleted the fix/surefire-engine-property-name branch April 14, 2026 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant