-
Originally reported on Google Code with ID 147
```
Currently 0.4 fails to output the reason for a failure when running ant 1.8 and junit
4.8 in classpath. The test will fail but the excellent descrip…
-
Originally reported on Google Code with ID 263
```
Describe the new feature you have in mind:
Ability to have Spock generate TestNG test classes instead of JUnit test classes.
Which particular probl…
-
Originally reported on Google Code with ID 119
```
Describe the new feature you have in mind.
It would be nice if spock supports Cobertura Code Coverage plugin
Which particular problem would this fe…
-
Originally reported on Google Code with ID 129
```
What steps will reproduce the problem? If possible, provide source code and
stack trace.
package com.mayabansi.webapp.service.spock
import spock.l…
-
```
What steps will reproduce the problem? If applicable, please provide a
mapping configuration and sample record input to recreate the problem.
1.the test class in groovy and using Spock testing fr…
-
Finalize on the tech stack and document it.
-
We need to do the following before releasing 0.1.4
1. Merge #38
2. Remove support for and dependencies on shadowJar
3. Update the README with the new documentation - Explicitly state that it is a bre…
-
```
What steps will reproduce the problem? If applicable, please provide a
mapping configuration and sample record input to recreate the problem.
1.the test class in groovy and using Spock testing fr…
-
The tests are much easier to write with scala + scalatest, but it may be friendlier to developers to remove that and move to a pure java test framework.
-
Originally reported on Google Code with ID 177
```
When using expect / where, it is possible to specify a list of values, and Spock will
iterate through the list and check each value.
This works whe…