-
Notifications
You must be signed in to change notification settings - Fork 0
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
Nested asserts cannot be transformed #1232
Comments
This test also fails on the previous milestone |
@leonard84, is this somehow contextually related to #783? |
We've only tried with 1.3, where this was working before. |
Hope the above pr fixes it for feature methods as well, because it is also a thing in
|
Yes @rtretyak the PR fixes both. |
As the merged PR does not contain any regression tests - is that a good idea? - I just built the current master and manually ran the tests presented by @paplorinc and @rtretyak this issue. They both pass now. |
What do you mean? |
Yeah, naming is not too consistent in some points in Spock sources :-D |
Basically everything in spock-specs is either test or fixture |
My bad entirely. But an additional re-test does not hurt, it was worth 5 minutes of my lifetime. :-) |
Yes, definitely, thanks for verifying fixes, also an important contribution. :-) |
The latest SNAPSHOT seems to have fixed these, thanks! |
Hey,
We've just tried out latest
Spock 2.0-M4
, we're getting the following exception:The cause seems to be that nested
assert
s seem to generate conflicting code, irrespective of their level or other previously generated ones (can be"".with {}
or whatever closure):The following reproducer can be used by running
./gradlew build
:https://github.com/paplorinc/spock-bug/blob/master/src/test/groovy/NestedAssertTest.groovy
The text was updated successfully, but these errors were encountered: