Maven
CI/CD & Code
Open source
<What you get/>
Locked, consistent dependency versions so local and CI runs behave identically
Profiles that switch scope and environment without code changes
Surefire and Failsafe configured so pipelines fail fast on cheap tests first
Existing dependency conflicts resolved rather than worked around
What it is
Maven manages dependencies, build lifecycle and test execution for Java projects. In a QA context its job is reproducibility: the same suite, resolved to the same library versions, runs identically on an engineer's laptop and on the build server. Surefire and Failsafe plugins hook the test phase into the pipeline.
How PerfectQA uses Maven
Maven is the build layer under most of our Java automation, and its value on test projects is mundane and important: everyone gets the same dependency versions. A suite that passes locally and fails in CI because of a version drift is a waste of a day, and locking that down is cheap. We use profiles to separate smoke from regression and to switch environment configuration without editing code, so the same command runs different scopes against different targets. Surefire and Failsafe are configured deliberately rather than left at defaults, because the distinction between unit and integration phases is what lets a pipeline fail fast on cheap tests before spending time on expensive ones. On inherited projects we usually find dependency conflicts that have been worked around rather than resolved, and untangling those is often the quickest route to a suite that behaves consistently.
Category
CI/CD & Code
In our stack
8 years
Projects
38 delivered
Frequent questions
Maven or Gradle?
Why do our tests pass locally but fail in CI?
Can we run just the smoke tests?
What's the difference between Surefire and Failsafe?
Every stack is different
Tell us yours, and we’ll show you where this fits
