How can I split my test execution stage from the test parsing stage?

Aron Weiler

Using bamboo-specs, when I attempt to split my unit test execution up from my test-parse task, I always receive this error:

my-test-results.trx was ignored because it was modified (2021-12-02 15:20:32.000) before task started (2021-12-02 15:20:52.626)

This appears to be happening because I have my unit test execution running in a stage before my unit test parsing.

The parser finds the .trx files for my MSTest compatible unit tests, and then just outright fails because the test results were generated before the current parsing task was started.

What is the point of this restriction?  Is it somehow to ensure that the test-parser task is looking at the most current results?

Here is an example of what my bamboo-specs look like:

Stage 1:
  - tasks: 
    # Run the unit tests
    - script:
      interpreter: BINSH_OR_CMDEXE 
      scripts: 
      - <execute my unit tests>

Stage 2:
  - tasks: 
    # ... copy results into current dir somewhere ... #
    # Parse the unit test results
    - test-parser:
      type: mstest
      test-results:
        - "**/*.trx"

 

Eduardo Alvarenga

Hello @Aron Weiler

As per your description, you are running multiple Jobs within the same Stage in Bamboo. Jobs will run in parallel and will not consider the results of their sibling jobs.

To instruct a Plan to run tasks in a specific order, you need to assign each Job to distinct Stages. You can also assign all tasks sequentially within the same Job, but I feel that might not be your case.

Stages groups (or maps) jobs to individual steps within a plan's build process. For example, you may have an overall build process plan that comprises a compilation step, followed by several test steps, followed by a deployment step. You can create separate Bamboo stages to represent each of these steps.

Here is a graphical representation of how projects in Bamboo contain plans, plans contain stages, stages contain jobs and jobs contain tasks:

Don't forget that whenever you need to refer to resulting artifacts from one Job in the other, you'll need to share the artifact between Jobs and stages.

It may also be the case that the parser is not considering the 'trx' files as they were created by another task. Make sure to enable "Pick up test results that were created outside of this build" under the Task advanced options.

 

Kind regards,

Eduardo Alvarenga
Atlassian Support APAC