winkingzhang/idea-run-wdio

The WebdriverIO Plugin is going to be your brilliant ideas to run test cases over @wdio/cli.

Wenqing's essays

You can use the editor on GitHub to maintain and preview the content for your website in Markdown files.

Whenever you commit to this repository, GitHub Pages will run Jekyll to rebuild the pages in your site, from the content in your Markdown files.

Markdown

Markdown is a lightweight and easy-to-use syntax for styling your writing. It includes conventions for

Deploy Locally with Jekyll Serve

This repo can be run locally using Ruby and Gemfiles.

Testing your GitHub Pages site locally with Jekyll - GitHub

How to generate TOC

The jekyll-gitbook theme leverages jekyll-toc to generate the Contents for the page. The TOC feature is not enabled by default. To use the TOC feature, modify the TOC configuration in _config.yml:

toc:
    enabled: true

License

This repo is open sourced under the Apache License, Version 2.0.

idea-run-wdio's Issues

How to show test suites hierarchy in the results panel

Thanks for making this plugin - it's great to be able to click the run/debug buttons next to the tests at last! I've missed that so much since working with Webdriver. I just installed the plugin on a project with a lot of tests and it worked straight away.

The only thing missing is there is nothing listed in the test-suite hierarchy view in the results panel (neither run or debug) which normally lists the tests in the describe/it tree, with green/red ticks and crosses etc. I only see "Instantiated tests..." while the test runs, then when the tests finish it has a red "Test framework quit unexpectedly" though the test passed and exited normally.

Is this part supposed to work or has it not been implemented yet?

If it is supposed to be working, do you know why it might not be functioning in my project?

I'm using PhpStorm 2023.1 - Build #PS-231.8109.199, built on March 30, 2023

"@wdio/cli": "^8.11.1",
"@wdio/local-runner": "^8.11.1",
"@wdio/mocha-framework": "^8.11.0",

Normally it would look something like this (different project):

[Feature] Add support for providing additional program arguments to wdio

As the title says, it would be awesome to have support for providing additional program arguments to wdio. I have a use case where I provide a js file as my config that uses commander to collect flag arguments for changing the base url to work off of, what environment should be used (e.g. dev or int), and whether to be headless or not.

When Debug it discregards Mocha timeout settings in wdio.conf.js and still expects it to be 2000ms

I have
mochaOpts: {
ui: 'bdd',
timeout: 600000
},

in my wdio.conf.js which I specified in the plugin configuration settings. But when Debug the test fails with

Error: Timeout of 2000ms exceeded. The execution in the test "New sale Creste Customer Test" took too long. Try to reduce the run time or increase your timeout for test specs (https://webdriver.io/docs/timeouts). (C:\Ira\Work\AutoTests\cr_qa\SaperaWebdriverIOTests\tests\POSTests\AllPosTests.js)
at createTimeoutError (C:\Ira\Work\AutoTests\cr_qa\SaperaWebdriverIOTests\node_modules\mocha\lib\errors.js:498:15)
at Test.Runnable._timeoutError (C:\Ira\Work\AutoTests\cr_qa\SaperaWebdriverIOTests\node_modules\mocha\lib\runnable.js:431:10)
at Timeout. (C:\Ira\Work\AutoTests\cr_qa\SaperaWebdriverIOTests\node_modules\mocha\lib\runnable.js:246:24)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)

When Run the same configuration everything is ok

Additional Info:
When the update ( 2021.7.23-0) was installed the runner has stopped working and I had to select another Wdio test frameworks in the configuration settings , apply the change and then switch it back to 'Mocha'. That helped but now I have this one..

Add Jasmine framework support

Currently test execution starts with --framework Mocha

It would be nice to be able to start tests with --framework Jasmine

--framework Mocha needs to be --framework mocha

When I run a test in Idea, it uses the option "--framework Mocha", but then I get an error message that only "mocha" (lowercase) is supported.
This is with the latest versions of Idea and all dependencies.

IntelliJ IDEA 2023.2.5 (Ultimate Edition)

"devDependencies": {
"@testing-library/react": "^14.1.2",
"@testing-library/user-event": "^14.5.1",
"@types/mocha": "^10.0.6",
"@types/node": "^20.10.3",
"@types/react": "^18.2.42",
"@types/react-dom": "^18.2.17",
"@typescript-eslint/eslint-plugin": "^6.13.2",
"@typescript-eslint/parser": "^6.13.2",
"@typestrong/ts-mockito": "^2.6.6",
"@vitejs/plugin-react": "^4.2.1",
"@wdio/browser-runner": "^8.24.9",
"@wdio/cli": "^8.24.9",
"@wdio/globals": "^8.24.9",
"@wdio/mocha-framework": "^8.24.12",
"@wdio/spec-reporter": "^8.24.9",
"autoprefixer": "^10.4.16",
"eslint": "^8.55.0",
"eslint-config-prettier": "^9.1.0",
"eslint-plugin-prettier": "^5.0.1",
"eslint-plugin-react": "^7.33.2",
"eslint-plugin-react-hooks": "^4.6.0",
"prettier": "^3.1.0",
"ts-node": "^10.9.1",
"typescript": "^5.3.2",
"vite": "^5.0.5",
"vite-tsconfig-paths": "^4.2.1"
}