When Sencha Studio is invoked it starts four Sencha Studio processes in Task Manager, when no tests are running; executing a test invokes 3-4 more Sencha Studio processes, as well as the appropriate driver.
When Sencha Studio is invoked it starts four Sencha Studio processes in Task Manager, when no tests are running; executing a test invokes 3-4 more Sencha Studio processes, as well as the appropriate driver.
Thanks for reaching out
Sencha Test relies on a few different child processes to fulfill its duties. Under the "Tasks" panel you can see the current tasks running under the hood. Also, part of that comes from Electron itself (you'll see "Sencha Studio Helper" running as a child process of "Sencha Studio").
When you're running WebDriver tests, Sencha Test will spawn sandboxes (one per browsers, give or take concurrency). That's meant by design, so the tests for each browser will run in a fresh environment, isolated from each other and from the Studio/stc process. The embedded Selenium server also runs on its own child process.
Hope it clarifies your question
Regards
Marcelo Bukowski de Farias