It injects its testing code into the webpage via an http reverse proxy which means it doesn't require internal access to the browser and thus works for unmodified remote mobiles for example. One can simply get a URL that any browser can go to & start executing the tests. Many of the issues with using WebDriver or DevTools seem to be avoided.
Another part of the architecture I've found really useful is that test scripts execute in a nodejs environment outside the browser sandbox and thus have the ability to run external programs, make their own API calls, and so on.
It injects its testing code into the webpage via an http reverse proxy which means it doesn't require internal access to the browser and thus works for unmodified remote mobiles for example. One can simply get a URL that any browser can go to & start executing the tests. Many of the issues with using WebDriver or DevTools seem to be avoided.
Another part of the architecture I've found really useful is that test scripts execute in a nodejs environment outside the browser sandbox and thus have the ability to run external programs, make their own API calls, and so on.