jdaugherty commented on issue #14920: URL: https://github.com/apache/grails-core/issues/14920#issuecomment-3084842185
FYI adding `@Rollback` does cause a transaction to be added. It's just for the scope of that test method. If the test is creating data and not finding it, it's likely because the created objects aren't saying `flush: true` when saving or the code is setting up data in setup() which will rollback at the end of setup. The issue I often have is if testing a process that has `withNewTransaction` then the data will never be found because the test transaction never finishes. This is why we use the clean-up approach so we can test across transactions if performing end to end functional tests. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
