-
Notifications
You must be signed in to change notification settings - Fork 334
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
Runner Discovered Suites #2319
Runner Discovered Suites #2319
Conversation
@neko-kai Can you test out this PR to see if it adequately addresses your needs? |
…e all custom discovery
@bvenners Yes, I just tested – it fully solves the problem! (7mind/izumi#2120) |
…ature-runner-discovered-suites
@bvenners I resolved the conflicts, I can merge this in after your review. Thanks. |
(if (wildcard.isEmpty && membersOnly.isEmpty) taskDefs else (filterWildcard(wildcard, taskDefs) ++ filterMembersOnly(membersOnly, taskDefs)).distinct).map(createTask) | ||
val tasks = (if (wildcard.isEmpty && membersOnly.isEmpty) taskDefs else (filterWildcard(wildcard, taskDefs) ++ filterMembersOnly(membersOnly, taskDefs)).distinct).map(createTask) | ||
|
||
//runnerInstance().internalDiscoveredSuites.set(Some(discoveredSuites)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cheeseng Why is this line of code commented out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bvenners The discovered suites are set in line 170 already, I think I just forgot to remove this commented line, this feature is supported on native as well.
Expose discovered suites through Runner's discoveredSuites.