Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[💡 Feature]: Provide a public interface to receive the current spec file #12535

Open
1 task done
christian-bromann opened this issue Mar 20, 2024 · 1 comment
Open
1 task done
Labels
help wanted Issues that are free to take by anyone interested Idea 💡 A new feature idea

Comments

@christian-bromann
Copy link
Member

Is your feature request related to a problem?

As a developer or QA tester I would like to know which spec file the worker is running in order to execute the right steps in my require or other type of setup script.

Currently the only way to get ahold of the spec file that is being run in the worker is through a custom service. However there are ways to run setup scripts outside of services, e.g. mochaOpts.require that might want to use this type of information.

Describe the solution you'd like.

Come up with a public interface to retrieve the information of which spec files are being run in the worker. We could introduce a new environment variable e.g. WDIO_SPEC_FILES that contains a stringified version of an array with the absolute paths to the test files.

Describe alternatives you've considered.

n/a

Additional context

issue came up in ionic-team/stencil#5542

Code of Conduct

  • I agree to follow this project's Code of Conduct
@christian-bromann christian-bromann added Needs Triaging ⏳ No one has looked into the issue yet Idea 💡 A new feature idea labels Mar 20, 2024
@christian-bromann christian-bromann added help wanted Issues that are free to take by anyone interested and removed Needs Triaging ⏳ No one has looked into the issue yet labels Mar 20, 2024
@wdio-bot
Copy link
Contributor

Thanks for reporting!

We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Issues that are free to take by anyone interested Idea 💡 A new feature idea
Projects
None yet
Development

No branches or pull requests

2 participants