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
We have been running into problems with the new test framework. In some (strange) scenarios seemingly unrelated tests can cause other tests to fail, even across phase boundaries. In this case, the presence of a unit test utilizing DomainClassUnitTestMixin causes an integration test to fail. Switching to @mock or removing any one of 2 test cases causes the integration test to pass.
This is a really frustrating problem to encounter because it is not always obvious (to me at least) how to tweak the tests to workaround the issue.
The text was updated successfully, but these errors were encountered:
seeker136 said:
One of my colleagues tested against Git master and was able to reproduce. This seems unlikely to be an environmental issue, but we are running Windows (XP 32bit and 7) and Java 1.6.0_25 and 1.6.0_26. My colleague is spinning up linux VM right now to see he can reproduce the issue.
seeker136 said:
Now that I have narrowed down the issue, I was able to replace all instances of @TestMixin(DomainClassUnitTestMixin) + mockDomain() with @mock(....) and all the tests is happy again.
seeker136 said:
Confirmed that this issue cannot be reproduced on linux. If you could not reproduce under Linux or Mac, please re-open the ticket and test on Windows. Thanks!
Original Reporter: seeker136
Environment: Tested against 2.0-M2 and snapshot build #1501.
Version: 2.0-M2
Migrated From: http://jira.grails.org/browse/GRAILS-8176
We have been running into problems with the new test framework. In some (strange) scenarios seemingly unrelated tests can cause other tests to fail, even across phase boundaries. In this case, the presence of a unit test utilizing DomainClassUnitTestMixin causes an integration test to fail. Switching to @mock or removing any one of 2 test cases causes the integration test to pass.
This is a really frustrating problem to encounter because it is not always obvious (to me at least) how to tweak the tests to workaround the issue.
The text was updated successfully, but these errors were encountered: