You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think we make this assertion which we could have something like:
myTestSuite {
testingStrategies = [new MyCustomStrategyNamed('foo'), new MyOtherCustomStrategyNamed('foo')]
}
Assuming the name passed to the constructor is the Named of the strategy, we would calculate myTestSuiteFoo for both Test tasks. Note that using MyCustomStrategyNamed or MyOtherCustomStrategyNamed twice with the same constructor argument would in theory be a no-op as testingStrategies is a SetProperty and both strategy implementations should implement proper hash code and equals.
We don't believe it's an actual bug but it may become one when solving #70
The text was updated successfully, but these errors were encountered:
I don't think we make this assertion which we could have something like:
Assuming the name passed to the constructor is the
Named
of the strategy, we would calculatemyTestSuiteFoo
for bothTest
tasks. Note that usingMyCustomStrategyNamed
orMyOtherCustomStrategyNamed
twice with the same constructor argument would in theory be a no-op astestingStrategies
is aSetProperty
and both strategy implementations should implement proper hash code and equals.We don't believe it's an actual bug but it may become one when solving #70
The text was updated successfully, but these errors were encountered: