generate unique runtime configs per webdriverio execution #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Webdriverio's test runner does not provide any api to pass data from launcher to runner processes for custom services. #66 used a workaround to pass the data to the child process with a temporary file like suggested in webdriverio/webdriverio#1914. But the name of the file was fixed and leads to wrong results when running multiple instances of webdriverio at the same time.
This PR improves the workaround and avoids conflicts when you run several instances of webdriverio simultaneously.
Running simultaneously the same config file requires a Node version with at least 6.13.0, 8.10.0, 9.2.0. In previous versions
process.ppid
isn't available. But this should be a edge case (maybe a wdio config that is configured via environment variables?).Changes: