How to implement a lock in Selenium with Java?

Question

I want the Script to Openfile.exe only if the previous one i.e CreateNew.exe has finished executing.

Right Now whats happening is, when I run TestNG.xml file it runs all the @Test priority wise and within 5 sec TestNg output console shows all the @Test are passed.

While my AutoIT scripts are still running in parallel in background.

The code is as follows:

@Test (priority=1)
public void CreateNew() throws Exception
{       
    Runtime.getRuntime().exec("exeFiles\\CreateNew.exe");       
}

@Test (priority=2)
public void OpenaFile() throws Exception
{
        Runtime.getRuntime().exec("exeFiles\\OpenaFile.exe");
}

And the code of AutoIt file is as Follows:

createnew()

Func createnew()
    Sleep(2000)
    Run("Mspaint.exe")
    WinWaitActive("Untitled - Paint")
    Send("!f")
    Sleep(1000)
    Send("n")
    Sleep(2000)
    WinClose("Untitled - Paint")
EndFunc   ;==>createnew

A possible solution for this can be:-

• In your Java/Selenium code create a temparory lockfile
• Start Autoit.exe
• In your Java/Selenium code write a loop to check if lockfile still exists
• Last step in the AutoIt code removes the lockfile
• If the lockfile doesn't exist break out of loop and continue with the next code

Now does anyone know how to create and use this lockfile in code?

Answer 1

My answer borrows from NarendraC's answers.

@Test (priority=1)
public void CreateNew() throws Exception
{       
    Process p = Runtime.getRuntime().exec("exeFiles\\CreateNew.exe");
    p.waitFor();       
}

@Test (priority=2, dependsOnMethods={"CreateNew"})
public void OpenaFile() throws Exception
{
        Runtime.getRuntime().exec("exeFiles\\OpenaFile.exe");
}

The issue, from what I could tell, was that the first method exited prior to completion. By adding the wait onto the process it will wait for it to end. This will, I believe, give you the desired result.

Answer 2

Even why cant you try "dependsOnMethods", This will be useful in that sense.

Check out below example for use:

@Test (priority=2, dependsOnMethods={"CreateNew"})

Answer 3

I think a better (though more complicated) way of doing it, instead of thread sleep, is to use a messaging queue and publish/subscribe model.