TestOps. The test suite indicated by the test execution is not running; another test suite is running

Web Testing
1

Hello
In TestOps, We scheduled a test collection run and I’m seeing how it’s going.

https://testops.katalon.io/team/461904/project/476724/executions/784

I’ve noticed that what I’m seeing in the details does NOT correspond to what’s actually running.
From what I can see, test execution 1859 should be running “8_5_IN_FacturasFlujos”.

image
image905×241 41.8 KB

https://testops.katalon.io/team/461904/project/476724/grid/plan/2208630/job/1859

Well, no. If you look at the debug.log to see how it’s going, it says “7_1_OR_PedidosExpress” is running, which, apparently, is test execution 1860.

image
image940×664 140 KB

The big problem is that yesterday, the “8_5_IN_FacturasFlujos” test suite didn’t run, and from what I see, it won’t run today either. In case something doesn’t add up between runs, yes, the order of the test suites within the test collection changed from yesterday to today.
Yesterday’s run.

https://testops.katalon.io/team/461904/project/476724/executions/779

And yes, this test user is NOT the user I’m using to access testOPs. I’m using a licensed user with administrator permissions.

1 Like
2

Hi @jb8katalon ,

Welcome to our community. Thank you for sharing your issue.

I see the mismatch between what TestOps UI shows for the job (#1859 showing 8_5_IN_FacturasFlujos) and what the debug.log reports actually running (7_1_OR_PedidosExpress, which belongs to execution #1860). Correct me if I understand wrong.

Have you changed the order of test suites inside your Test Suite Collection between runs? If yes, please before scheduling, confirm the order of test suites in the Test Suite Collection doesn’t change. If needed, duplicate the collection when you want a different order (instead of reordering the same one).

You can stop and remove any running/pending jobs before triggering the new one. This avoids cross-wiring of execution IDs.

Quick check by going into Test Suite Collection 7_1_OR_PedidosExpress and confirm its order hasn’t shifted relative to 8_5_IN_FacturasFlujos. If the order changed, that explains why job 1859 logs are out of sync with the UI.

3

Hi @jb8katalon,

Have your issue been resolved yet? If yes, please let us know your solution as reference to others. If no, feel free to provide more information so that we can better support. Thank you