Maven Interview Questions

How do you run a specific TestNG suite from Maven in CI?

What are the Maven lifecycle phases that matter for a test project?

validate → compile → test-compile → test → package → verify → install → deploy; running a later phase runs every earlier phase in that lifecycle.

How do dependency scopes work, and which scope should test libraries use?

compile is the default and leaks to consumers, provided is supplied at runtime by the container, runtime is not needed to compile, and test is only on the test classpath — Selenium, TestNG and REST Assured all belong in test scope.

How do you use Maven profiles to run the same suite against different environments?

Define profiles per environment that set properties (base URL, browser, suite file), then activate with -P; the framework reads the properties as system properties.

How do you run a single test, a group, or a specific suite XML from the command line?

-Dtest=ClassName#method for Surefire, -Dgroups=smoke for TestNG groups, and -Dsurefire.suiteXmlFiles or -DsuiteXmlFile to point at a suite XML.

What is project object model, and why does it matter in Maven?

project object model is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply project object model in a production Maven project?

Apply project object model through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is default lifecycle, and why does it matter in Maven?

default lifecycle is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply default lifecycle in a production Maven project?

Apply default lifecycle through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is clean lifecycle, and why does it matter in Maven?

clean lifecycle is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply clean lifecycle in a production Maven project?

Apply clean lifecycle through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is site lifecycle, and why does it matter in Maven?

site lifecycle is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply site lifecycle in a production Maven project?

Apply site lifecycle through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is dependency scopes, and why does it matter in Maven?

dependency scopes is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply dependency scopes in a production Maven project?

Apply dependency scopes through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is transitive dependencies, and why does it matter in Maven?

transitive dependencies is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply transitive dependencies in a production Maven project?

Apply transitive dependencies through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is dependency mediation, and why does it matter in Maven?

dependency mediation is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply dependency mediation in a production Maven project?

Apply dependency mediation through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is dependency management, and why does it matter in Maven?

dependency management is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply dependency management in a production Maven project?

Apply dependency management through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is plugins, and why does it matter in Maven?

plugins is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply plugins in a production Maven project?

Apply plugins through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is Surefire plugin, and why does it matter in Maven?

Surefire plugin is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply Surefire plugin in a production Maven project?

Apply Surefire plugin through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is Failsafe plugin, and why does it matter in Maven?

Failsafe plugin is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply Failsafe plugin in a production Maven project?

Apply Failsafe plugin through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is profiles, and why does it matter in Maven?

profiles is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply profiles in a production Maven project?

Apply profiles through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is properties, and why does it matter in Maven?

properties is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply properties in a production Maven project?

Apply properties through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is settings.xml, and why does it matter in Maven?

settings.xml is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply settings.xml in a production Maven project?

Apply settings.xml through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is repositories, and why does it matter in Maven?

repositories is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply repositories in a production Maven project?

Apply repositories through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is SNAPSHOT versions, and why does it matter in Maven?

SNAPSHOT versions is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply SNAPSHOT versions in a production Maven project?

Apply SNAPSHOT versions through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is multi-module builds, and why does it matter in Maven?

multi-module builds is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply multi-module builds in a production Maven project?

Apply multi-module builds through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is parent POMs, and why does it matter in Maven?

parent POMs is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply parent POMs in a production Maven project?

Apply parent POMs through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is BOM imports, and why does it matter in Maven?

BOM imports is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply BOM imports in a production Maven project?

Apply BOM imports through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is build phases, and why does it matter in Maven?

build phases is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply build phases in a production Maven project?

Apply build phases through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is effective POM, and why does it matter in Maven?

effective POM is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply effective POM in a production Maven project?

Apply effective POM through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is offline builds, and why does it matter in Maven?

offline builds is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply offline builds in a production Maven project?

Apply offline builds through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is Maven Wrapper, and why does it matter in Maven?

Maven Wrapper is a core Maven concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply Maven Wrapper in a production Maven project?

Apply Maven Wrapper through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.