Test Leakage, from Rob Fletcher book, Spock: Up and Running:
When side effects from a test affect subsequent tests in the suite, we can describe that test as leaking. Test leakage is caused by badly managed resources. Typical causes of leakage include data in a persistent store that is not removed, changes to a class’ metaclass that are unexpectedly still in place later, ....
Learn how to avoid test leakage in Grails integration and functional.
@jeffscottbrown's talk at G3 Summit.
Sharp your Grails testing skills:
- Domain Classes
- Command Objects
- Tag Libraries
- Grails 3.3 Trait-Based Testing Library vs @TestFor approach
- REST APIs
@nulleric's talk at G3 Sumit. He discusses continuous build, continuous deployment, chat notification, session management, logging management, etc. You will find, in the slides, links to many services and Saas solutions. Bookmark this slide deck, and you will have a comprehensive list of services when you need to tackle any of those tasks.