Jasmine tests - Cannot run single test when specifying test file

[simplygeekuk]

Description

I am unable to run a single test file when using the following command:
mvn test -Dtest=testfile

I get the error:

[ERROR] Failed to execute goal com.vmware.pscoe.maven.plugins:o11n-actions-package-maven-plugin:4.4.1:run-vro-tests (default-run-vro-tests) on project vro-actions: Unable to parse configuration of mojo com.vmware.pscoe.maven.plugins:o11n-actions-package-maven-plugin:4.4.1:run-vro-tests for parameter test: Cannot assign configuration entry 'test' with value '${test}' of type java.lang.String to property of type java.util.Map

[Description of the issue. Affected functionality / feature.]

Steps to Reproduce

run maven test command using -Dtest flag to specify a specific test file.

Preconditions: N/A

Expected behavior: test to run against single test file.

Actual behavior: unit test execution fails

Reproduces how often: 100%

Component/s: [What are the Build Tools for VMware Aria components affected by the issue (e.g. "common/artifact-manager", "maven/plugins/vra-ng", "typescript/vrotest", etc)]

Affects Build/s: [Which are the Build Tools for VMware Aria releases / builds affected by the issue]

Environment

Client

• Build Tools for VMware Aria Version: 4.4.1
• Visual Studio Code Version: 1.100.2
• OS Version: Windows 10

Dependencies

Run: curl -o- https://raw.githubusercontent.com/vmware/build-tools-for-vmware-aria/main/health.sh | bash and paste the output here:

Server

• vRealize Automation Version: 8.18.1
• vRealize Orchestrator Version: 8.18.1
• vRealize Operations Version: N/A
• vRealize Log Insight Version: N/A

Failure Logs

[ERROR] Failed to execute goal com.vmware.pscoe.maven.plugins:o11n-actions-package-maven-plugin:4.4.1:run-vro-tests (default-run-vro-tests) on project vro-actions: Unable to parse configuration of mojo com.vmware.pscoe.maven.plugins:o11n-actions-package-maven-plugin:4.4.1:run-vro-tests for parameter test: Cannot assign configuration entry 'test' with value '${test}' of type java.lang.String to property of type java.util.Map

Related issues and PRs

Additional Context

[VenelinBakalov]

Hi @simplygeekuk , I am not 100% sure we support execution of a single test suite, I think we only have the option to run all tests or skip all (using -DskipTests). I will check with the team.

[VenelinBakalov]

Currently this is not supported by the tool. We need to check if it is possible to extend with such capability

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[VenelinBakalov]

Btw I forgot to mention, if you are using jasmine there is an option to skip certain tests by adding x in front of the test or the suite (e.g. it(...) -> xit(...) and describe(...) -> xdescribe(...)). I know it is not the same as executing a single test but still as a workaround in case you need it until I clarify with the team whether it is possible to support this feature.

[simplygeekuk]

Hi @VenelinBakalov - Thanks for the update. One thing I will note from the documentation: https://github.com/vmware/build-tools-for-vmware-aria/blob/main/docs/archive/doc/markdown/use-workstation-vro-project.md

The Jasmine-JUnit adapter is part of the standard Maven lifecycle's testing phase, therefore tests will be discovered and executed every time you build your project. However, you can trigger tests explicitly:

mvn test # This will run all tests in the project without packaging it.
mvn test -Dtest=SomethingTest # This will run only tests in the SomethingTest.js file.

it looks like 'mvn test -Dtest=' did exist at some point?

[VenelinBakalov]

To be honest I am not sure, I saw the documentation reference but when I try to execute with an earlier version of Build Tools I receive an error:

 Unable to parse configuration of mojo com.vmware.pscoe.maven.plugins:o11n-actions-package-maven-plugin:2.44.0:run-vro-tests for parameter test: Cannot assign configuration entry 'test' with value '${test}' of type java.lang.String to property of type java.util.Map 

However, I think the feature should be implementable.