microsoft / microsoft/vscode-java-test

Question: how to run tests with properties from alternative pom file

Open
#1,365 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ai-triaged enhancement junit low-priority maven question test-execution
Dominant language
TypeScript
Stars
340
Forks
173
Avg merge
1d 19h
Merged PRs (30d)
18

Description

I'm trying to run tests for a project which uses Arquillian integration test framework. The project has an alternative pom.xml file (outside of the root dir of the project) which should be used when runninng tests via maven

mvn clean install -f testsuite/integration-arquillian/pom.xml

but when running tests from vscode, I get exceptions/errors that seem like I'm missing all the mandatory default properties that are defined in the pom files but are missing when running tests via vscode.

Would you have any pointers for me on how to setup Java test runner for vscode for a project like this? I'd appreciate any help!

The project I'm working with is keycloak and the pom with the (apparently ignored) properties is testsuite/integration-arquillian/tests/pom.xml.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Java test runner setup for VS Code and compare its test launch behavior with mvn clean install -f testsuite/integration-arquillian/pom.xml. Inspect the referenced Keycloak testsuite/integration-arquillian/tests/pom.xml properties and determine whether the alternative POM can be selected. Done means the Arquillian tests run from VS Code with the required properties.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, vscode
Domain
testing, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.