0

I am trying to run my testcomplete test suites using azure devops pipelines and I want to achieve parallel execution using the same ex: running two suites in two configured agents simultaneously/parallely. I am able to achieve it using the build pipeline by adding two agent jobs which on running executes both the jobs parallely. But the same thing I am not able to acheive using release pipeline.

FYI: I don't want to use the slicing feature as it divides test cases in runtime based on test cases or assemblies. I want to configure it before execution and then trigger it

Improve this question
1
  • @DanielMann I have tried adding agent nodes in same release pipeline and on execution of the pipeline, the agent jobs run in sequence while in build pipeline it executes parallely which is what I want for the release pipeline too Commented Dec 13, 2023 at 5:47

1 Answer 1

Reset to default
1

I can reproduce the same situation in Release Pipeline.

When we add two jobs in a single release pipeline stage, the jobs will run in sequence by default.

enter image description here

enter image description here

We are not able to change this behavior for the time being.

To meet your requirement, you can refer to the following two methods:

1.If your job configuration is exactly the same, you can use the Multi-Agent option of the Agent job.

For example:

enter image description here

Result:

enter image description here

2.If you need to configure two jobs separately, you can add two stages and then add job in the stages respectively.

For example:

enter image description here

Note: You need to set the Triggers for the stages to After Release.

enter image description here

Result:

enter image description here

Update:

If you can consider using slicing feature in release pipeline, we can use the Multi-configuration option.

enter image description here

Here are the steps:

Step1: Set Pipeline variable with the test case filter info:

enter image description here

Step2: Use the test case filter in the multi-configuration option.

Step3: Use the variable in test case filter field of the test task.

For example:

enter image description here

When you run the Pipeline, the agent job will run the test with the test case filter settings.

For more detailed info, you can refer to this doc: Multi job configuration

Improve this answer
Sign up to request clarification or add additional context in comments.

7 Comments

Yeah I get that we have either the slicing option or the staging option. But 1.With slicing option, we can't configure which scripts/tests will be run on which agent as it picks up from the agent pool 2.With multi staging I will get separate reports but I am trying to capture a single report like how I get it in the build pipeline. Is there any option for that?
@GunacelanM May I know if the staging option can meet your requirement?
Yeah Staging looks fine but I am concerned about the reporting part where I get n different reports for n stages. Is it possible to capture it as a single report like how we do in the build pipeline
I can understand your concern. If you want to combine all test result from different stage, I am afraid that there is no method can do it for the time being. If you want to combine Code coverage result, you can consider using the extension:marketplace.visualstudio.com/…
@GunacelanM If you can consider using the slicing option, you may use the multi-configuration option. In this case, it can generate one report. Refer to my update in the answer
|

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.