Approach currently assumes the testing app can get references to started processes

[Holf]

For example, I can start a ChromeDriver.exe process manually, in which case I have a handle on the process and can use the AllForOne wizardry.

However, Selenium WebDriver can take care of instantiating ChromeDriver processes for you, in which case you don't get a reference to the process. Well, actually you can find it via reflection but it is buried pretty deep.

Need to consider either:

• An extension which will use reflection to give you a reference to ChromeDriver (or FireFoxDriver or whatever) when you're using Selenium WebDriver.
• A more comprehensive approach which polls a list of running processes to spot new ones that appear after your test app has started. For each new process, check if the test app is the parent process (pretty easy to do) and, if so, add it to the AllForOne managed process list.

Need to think on this a bit more...