Canmove, confirm
2,041
edits
Changes
→Ownership and Overlap
Tests can and should overlap between Gaia Integration and Gaia Acceptance. It is unacceptable process complication for QA to expect developers to always consult their needs and vice versa for every change. If the test flows are shared, it's all too easy for one group to inadvertently make a change that damages the purpose of the other. For acceptance, in particular, this is too risky, as proper acceptance depends heavily on maintaining a particular scope and depth.
Avoiding these communication issues and this risk requires separate tests, even to the point where there might be tests whose flow is entirely duplicated between the two suites.
While this seemingly violates "single point of truth," the different contexts in which the tests are specified, scoped and maintained actually makes these two different tests, much like two separate applications would never refer to each others' source unless it can be pushed into an independent library.
Via skillful reuse of View and other code modules between suites, each test suite can be treated as an independent target without increasing maintenance unacceptably. Ideally, only abstract fixture setup and flow is expressed in the test method, with all other maintainable aspects in shared modules. So long as both groups agree to maintain interfaces of shared code, they can both work freely.
Of course, each group should have an opinion on coverage for either suite, and can (and should) help expand each suite, but single point of ownership allows decisions to be made quickly as appropriate for each set of primary stakeholders.
