The task cancel API test was a bit flakey, #2028
Merged
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.
It was setting additional values in the integration setup on the class
itself but this setup is run once for possibly multiple classes e.g
EndpointUsage x;
new TestClass(x).Test1();
new TestClass(x).Test2();
new TestClass(x).Test3();
new TestClass(x).Test4();
new TestClass(x).Test5();
integration setup is an override per TestClass but only one of them will
be called per instance of
x
. So if the callback defines settingvariables on the
TestClass
instance usingthis
other TestClassinstances won't see this.
This PR makes CallIsolatedValues a class of its own that allows you to
register extended values that can be shared amongst all TestClass
instances.