testable / openfin-wdio-testable-example Goto Github PK

Hi Avi. Thanks for putting this together!

I'm wondering if you've set up anything similar with other test tools and frameworks? I'm looking into working with several that are a little more modern than WebDriver, but noticing that many of them expect to launch the browser in a special / opinionated context, and not sure if they're a good fit for testing OpenFin apps on top of the OpenFin runtime and its executable.

If I use a tool that doesn't rely on the WebDriver protocol, I'm thinking I can get rid of the complex launch flow. I see you're using WebDriver's onWorkerStart hook to spawn a Node child process that opens the batch, passes through config and debugging port arguments, and then opens the RVM exe.
How does that make it over to the test.js file, so that the browser object is all ready to go and hooked into the running app?

I'm trying to determine how much of that flow I'll need to keep in mind with new tools, and whether they'd even support it. Playwright, Cypress, Taiko, and Puppeteer are on my list right now.

Hi all,
I downloaded the project recently and set up all the required following read me documentation.
Could some one help resolving this @wdio/cli:launcher: No specs found to run, exiting with failure?
I invoked wdio in .bin folder. I tried to replace the wdio.config.js file as well.

Thanking in advance,