AppiumDriverLocalService dosent spawn on MultiThreading

[saikrishna321]

@TikhomirovSergey i was trying to execute the appium android test in parallel where i wanted to start the appium-server programmatically for every thread.

TestNG by default provides a way were u can run methods in parallel and set the thread-count. When i trigger the appium server with AppiumLocalSerive it always hooks to a single thread.

When i start the appium server as we do from command line it works fine. I have a sample project to reproduce it.

https://github.com/saikrishna321/TestNGParallelThreads

When i set the ParallelMode.CLASSES i see the the appium server and the application launched on two thread(two devices) as expected. Please check the gist for logs

https://gist.github.com/saikrishna321/8a2e49ccc080a3faf014

When i set the ParallelMode.METHODS i dont see the methods executing in parallel, check the gist for logs and also i noticed the AfterClass for one of the has not completed, i see the process still running

https://gist.github.com/saikrishna321/6592f680dee7d70be59c

[TikhomirovSergey]

@saikrishna321 Thank you for the detailed report. I'll run into this problem as soon as possible.

[saikrishna321]

@TikhomirovSergey More info: i'm running my test with TestNG framework and below the testng.xml used to trigger the tests

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite thread-count="2" name="Suite" parallel="methods">
    <test name="Test">
        <classes>
            <class name="com.test.classes.TestNGMethodSelector">
                <methods>
                    <include name="methodOne" />
                    <include name="methodTwo" />
                </methods>
            </class>
            <class name="com.test.classes.DemoClassWithManyMethodsTest">
                <methods>
                    <include name="methodOne_1" />
                    <include name="methodTwo_2" />
                </methods>
            </class>
        </classes>
    </test> <!-- Test -->
</suite> <!-- Suite -->

[saikrishna321]

@TikhomirovSergey any updates in this.. i have updated the repo link .. all that i'm trying to do is just trigger appium server session as per the testng.xml

[TikhomirovSergey]

@saikrishna321
I'm working on .Net client, today or tomorrow going to finish this work.

The main idea is that it is not a bug (however, who knows :) ). AppiumDriverLocalService was designed as thread safe feature...

[saikrishna321]

@TikhomirovSergey hey thanks a lot for getting back..

Looking forward for you take a look at this .

[TikhomirovSergey]

There is a progress. Now I'm suspecting a bug!

[saikrishna321]

@TikhomirovSergey Great 👍 waiting to hear from you

[TikhomirovSergey]

Well. There are problems

First of all your samle code has some issues. I'm doubting that it was able to be run in multi-threads. Here is my improvement:

saikrishna321/TestNGParallelThreads#1

You can take a look at this. It is not necessary to merge this PR :)

Also there are problems on Java client side. It is possible to hang AppiumDriverLocalService in multiple threads. I've fixed it and I've got an improved build locally. The PR with this fix is coming soon.

Also ... even the Selenium Java client has an issue. :) It is reproduced on Windows 7/8. I've tried to run your code with ChromeDriverService and the result is the same. This bug can be avoided on the Appium Java client side.

[saikrishna321]

@TikhomirovSergey That's awesome ... I already have a project running AppiumDriverLocalService on multiple thread at class level parallelization it works .. but i have noticed that sometimes the app just opens n closes .. not sure why..

Looking for the PR with latest version.

Here is the repo:
https://github.com/saikrishna321/AppiumTestDistribution

Thoughts ?

[TikhomirovSergey]

@saikrishna321 I've ideas for now. Please open one more issue. I think it is the another problem and it is not related to this. ... And provide deatails as many as you can :).

But the new PR will be proposed very soon (this issue fix).

[saikrishna321]

@TikhomirovSergey sure i'm gonna do that.. i'm keeping this issue open until the new PR is out ..