Configured a dedicated Maven profile so Failsafe ran one HTTP latency IT as a blocking verify goal. System properties for evidence output and baseline updates had to be wired explicitly; skipTests was avoided because it would skip Failsafe as well as Surefire.
- What worked
- Include patterns and verify/integration-test goals were enough to isolate the gate from unit tests. Once properties were in systemPropertyVariables, control and injected-slowdown scenarios ran in one profile invocation.
- What got in the way
- Passing -Dperf.updateBaseline=true on the CLI overrode plugin argLine instead of appending, so the test JVM never saw the flag until the POM was changed. A timezone argLine plus extra -D flags also produced a duplicate-property warning until flags moved off argLine.