search

webdriverio-community / wdio-vscode-service

A service to test VSCode extensions from end to end using WebdriverIO
https://webdriverio-community.github.io/wdio-vscode-service/
MIT License
37 stars 28 forks source link

Allow isolated workspaces per test suite #132

Open bmingles opened 3 months ago

bmingles commented 3 months ago

It currently only seems possible to configure a single workspace path in wdio.conf.ts under wdio:vscodeOptions -> workspacePath. This works great for some scenarios, but it can be problematic in cases where test suites are run in parallel. Namely, changing vscode settings as part of tests is not isolated to the current test suite but bleeds into other concurrently running suites. It would be helpful to provide a mechanism for isolating workspace locations per test suite. One thought that comes to mind would be to support a callback function as a value for workspaceSettings that could dynamically return a file path when a test suite runs.

christian-bromann commented 3 months ago

I think this is a great idea! I am personally working at a lot of different things on WebdriverIO and probably won't have time to contribute to the VS Code service part anytime but I would appreciated any contributions on this side. Note that we pay out such contributions thanks for our project sponsors.

bmingles commented 1 month ago

@christian-bromann I’d love to hear more details about how you pay out for contributions

christian-bromann commented 1 month ago

You can read more about it here: https://bromann.dev/post/automated-contributor-expense-process/. Essentially everyone who reviews and merges PRs on behalf of the WebdriverIO project decides how much money should be expensed for the work. You will be able to expense the amount through OpenCollective.