Invoking `IApp.Dispose()` does not terminate the webdriver about uno.uitest

[jeromelaban]

@ADD-David-Antolin we've been trying to reproduce the issue, but we're unable to when calling App.Dispose(). At this time, the driver is properly closed.

Have you tried invoking this method in the assembly tear down, or test tear down?

[ADD-David-Antolin]

@jeromelaban In TestBase.cs

[Setup]
public void SetupTest()
{
    this.App = AppInitializer.AttachToApp();
}

[TearDown]
public void TearDownTest()
{
    try
    {
        this.TakeScreenShot("teardown");
    }
    finally
    {
        this.App.Dispose();
    }
}

I assume that is test tear down.

[jeromelaban]

@ADD-David-Antolin yes, this is the case. Then if the driver stays active, it may be a bug in selenium or the driver itself. You may need to find a way to determine the PID of the process being launched based on the PTY being used by the build scripts.

Something like this could do, to terminate those processes:

ps -o pid,tty,cmd -ax | grep $(tty) | grep 'msedgedriver' | awk '{print $1}' | xargs kill

[ADD-David-Antolin]

@jeromelaban The agent machines are Windows server so it does not have a tty equivalent I think. Do you know the equivalent of what snippet but for PowerShell?

[jeromelaban]

@ADD-David-Antolin indeed, this technique does not work for Windows. Aside from fixing Selenium, something that is out of our hands at this point. Browsing the source from Selenium may explain why this happens (somewhere in there)