-
Notifications
You must be signed in to change notification settings - Fork 40
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
Implement configurable scenario execution scheduler #331
Labels
Milestone
Comments
Suremaker
added
enhancement
An enhancement of the feature or new feature
LightBDD 4.X
Future version of LightBDD
labels
Aug 23, 2023
Suremaker
added a commit
that referenced
this issue
Aug 23, 2023
…lat scenario execution with callback mechanism Updated ScenarioExecutionScheduler to use ThreadPool to run scenarios Added IRuntimeObjectInfo with RuntimeId property Changed ExecutionPipelineAdapter to avoid using AsyncLocal when mapping scenarios to xunit tests
Suremaker
added a commit
that referenced
this issue
Aug 23, 2023
Suremaker
added a commit
that referenced
this issue
Aug 23, 2023
Suremaker
added a commit
that referenced
this issue
Aug 23, 2023
Suremaker
added a commit
that referenced
this issue
Aug 31, 2023
…hread Created IScenarioExecutionScheduler, IScenarioExecutionSchedulerAttribute and ScenarioExecutionSchedulerTypes allowing to use different schedulers for scenarios Added RunOnDedicatedThreadAttribute allowing to use the new scheduler
Suremaker
added a commit
that referenced
this issue
Sep 9, 2023
Note: consider implementing another constraint attribute, similar to |
Suremaker
added a commit
that referenced
this issue
Sep 10, 2023
… race condition and spawning unnecessary threads
Suremaker
added a commit
that referenced
this issue
Sep 10, 2023
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
Implement scenario execution scheduler with support for:
Environment.ProcessorCount
),High, Normal, Low
) impacting the execution order,Features
The text was updated successfully, but these errors were encountered: