You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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!
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
The text was updated successfully, but these errors were encountered: