Matching aliases on parallel tests running#5
Open
R3VoLuT1OneR wants to merge 1 commit intoAndyA:masterfrom
R3VoLuT1OneR:master
Open
Matching aliases on parallel tests running#5R3VoLuT1OneR wants to merge 1 commit intoAndyA:masterfrom R3VoLuT1OneR:master
R3VoLuT1OneR wants to merge 1 commit intoAndyA:masterfrom
R3VoLuT1OneR:master
Conversation
…hing on test alias
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I use TAP::Harness to run Selenium tests in parallel, on many browsers.
My test architecture allows me run one test ( one file ./t/test.t ), per browser.
So I should to fork the tests, and give each tests other args.
For smoothly run on TAP::Harness I give alias to each test and it run synchronously, but I want to run tests in parallel on many browsers.
Problem that I meet, it is that I can't use my test aliases to run in parallel, so I used to make some changes on TAP::Parser::Scheduler.
Actually I think that my solution is not so good, but I would glad to see that feature in TAP::Harness.