Not able to run multiple Qase Test Cases in parallel

[mdiep-asp]

Currently, if we try to run multiple Qase Test Cases in parallel (using maven surefire plugin + testng) by splitting all test cases into 3 test suites, we will see this error:

[main] INFO com.app.appium.provider.DeviceProvider - The test device is: cloud_ios
[main] INFO com.app.appium.utilities.AppiumDriverUtils - Activating app
[main] INFO com.app.appium.core.BaseTest - Test: testABC , Result:failed
[main] INFO com.app.appium.utilities.AppiumDriverUtils - Terminating app
[main] INFO com.app.appium.provider.DeviceProvider - The test device is: cloud_ios
[main] INFO com.app.appium.utilities.AppiumDriverUtils - Activating app
[main] ERROR io.qase.api.CasesStorage - Previous case is still in progress.
[main] INFO com.app.appium.core.BaseTest - Test: testDEF , Result:failed
[main] INFO com.app.appium.utilities.AppiumDriverUtils - Terminating app
[main] INFO com.app.appium.provider.DeviceProvider - The test device is: cloud_ios
[main] INFO com.app.appium.utilities.AppiumDriverUtils - Activating app
[main] ERROR io.qase.api.CasesStorage - Previous case is still in progress.
[main] INFO com.app.appium.core.BaseTest - Test: testGHI , Result:failed
[main] INFO com.app.appium.utilities.AppiumDriverUtils - Terminating app

Upon looking into Qase api, we saw this:

Seems like each test case run is associated with a thread. Even though we run the other test suites with a different maven instance, somehow the existing running test case thread from one suite was being called by others and caused this issue.

Wonder Qase actually supports running in parallel? If not, will Qase soon support it? Please help. Thanks

[savkk]

@mdiep-asp Hi! Could you give an example of the parallel running settings that you use?

[mdiep-asp]

@savkk we ran our mobile automation tests on CircleCI with these configs:

• We broke the entire test suite into a 3 smaller test suites
• Each smaller test suite was running on its own distinct workflow of CircleCI
• We used maven surefire plugin to execute these smaller test suites

We believe that even though there are 3 running distinct workflows. They are still on the same machine, and probably share the same threads pool.

[savkk]

@mdiep-asp, have you set up parallel run through testng? Could you give an example of testng configuration?

[mdiep-asp]

@savkk we didn't set up parallel run thru testng. We basically have 3 open terminals, each run with command like this mvn clean test -DtestngXmlFile=$PARAM_TESTNG_XML -DSuiteName=$PARAM_SUITE_NAME in parallel.

[savkk]

@savkk we didn't set up parallel run thru testng. We basically have 3 open terminals, each run with command like this mvn clean test -DtestngXmlFile=$PARAM_TESTNG_XML -DSuiteName=$PARAM_SUITE_NAME in parallel.

It looks really strange. If you run tests in different processes, they should not affect each other. They have their own memory.
If you run a single process, does this error not appear?