| Table of Contents |
|---|
Resources
Naming conventions
...
- The test 'def' should describe a high level scenario (not set up details or expected outcome)
- Each label should have a description. The label plus description should form a readable English sentence preferring high level (Product Owner)
type language over code level langue i.e. no method names etc.
(since the label is the first word of the sentence the description should start with a lower case character and end with a full stop)
Note. Well known acronyms should remain in uppercase as in normal (writing) language. e.g. 'the ROP period' - All blocks should be separated by a blank line except and 'and: ' block which really is a continuation of the previous block
Given-when-then v. expect. Given-when-then is the preferred format but expect block is useful in situations where it 'is more natural to describe
stimulus and expected response in a single expression' see also the Spock PrimerCode Block language groovy title Expect and Labels Example @Unroll def 'Celltrace scanner activation request with invalid ropPeriod value of #ropPeriod.'() { given: 'scanner details with an invalid rop period' eventHeaders = eventHeadersForCellTrace(ropPeriod, 'STREAMING') expect: 'the outbound request XML contains the default rop period of "FIFTEEN_MIN"' activateEventJobRequest.getRequest(eventHeaders).contains("<reportingPeriod>FIFTEEN_MIN</reportingPeriod>") where: 'ROP period is any of these invalid values' ropPeriod << [ null, 0, -1, 123 ] }- Expected outputs in Spock data tables should be separated with a double pipe symbol (||) to visually set them apart
...