nebula-plugins / nebula-plugins/nebula-project-plugin

test results location is different than the binary output

Open
#82 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Groovy
Stars
98
Forks
19
PR merge metrics
No merged PRs in 30d

Description

in unit tests:
output binaries are generated under
"test-results/test/binary/"
test results are generated under
"test-results/test/"

in integrationTest:
output binaries are generated under
"test-results/integrationTest/binary/"
test results are generated under
"integTest-results/"

I would expect to have consistency and that the test results would be generated under "test-results/integrationTest/"

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

Inspect the Gradle test task output configuration and compare the unit-test and integrationTest result paths described in the issue. Verify the current locations, then confirm that integration-test results are placed under test-results/integrationTest/ consistently with the binary output.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy
Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.