nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TestRun Assignee changes when changing the Assignee of the Test Execution

Gama, Márcio

I noticed that in some cases (have not found the pattern yet), when changing the Assignee of a Test Execution, the TestRun Assignee also change even if the Tests are already marked as PASSED.

This causes a lot of problems in terms of auditing (to know who did the tests).

Has anyone encountered this problem and found a way to prevent this from happening?

Thank you!

Accepted answers

All comments

Stefan Salzl

Hi @Gama, Márcio and welcome to the community,

Couldn´t reproduce the behaviour on my site (cloud) and cannot get a hint of a cause.

Did you check the "Activity" section within the TestRun? Any changes that were made in the issue should be logged there (like the history of issues). Maybe this gives a hint who, what or why the assignee was changed. Maybe we get a first information to further investigate any causing issue.

Best

Stefan

Gama, Márcio

Thank you for your feedback @Stefan Salzl

Unfortunately the Activity section does not provide any additional information.

Stefan Salzl

hi @Gama, Márcio

ok that seems really strange. Is it completly empty? it doesn´t even tracks that there has been a re-assignment?

Best
Stefan

Gama, Márcio

It just logs the change in the assignee of the Test Execution and not the change in the assignee of the Test Runs.

Former user

It is really really annoying that Xray automatically assign all test runs when an execution is assigned!
I can see in Xray documentation (Test execution page) that this is by default "Test Runs are assigned to the Test Execution issue assignee by default. ", but I really do not get why????

In our case we have a lot of test executions with many tests that should be run by different people/teams in a specific order (E2E test flows). We use the execution to keep track of where we are in the flow and every time a person has finished their test cases/steps, they assign to the next in the row. Every time test execution assignee is changed ALL test runs (whether PASSED or TODO) are assigned to the same person. THIS IS NOT THE BEHAVIOUR WE EXPECT. We off course want to have the testruns assigned to the relevant persons/teams and NOT to whoever is next in line to perform a step.

Why is this automatic assignment of test runs not a configurable option? It seems extremely unflexible and I do not know how we should structure our E2E test flows consisting of many test cases across teams and systems, if not by using Test Executions. Please advice how it could be done instead?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

xray

jira

jira-server

atl-orange

marketplace