Open GoogleCodeExporter opened 8 years ago
I think that not only makes sense for stepwise specifications.
It would be great to have spec wide parameterization like it's possible with
JUnit parameterized tests. In our case we'd like to test multiple targets
against a common spec consisting of multiple tests. As instantiating these
targets is expensive, it doesn't make sense to iterate data driven over the
targets for every single test. Instead there could be a @Shared def target that
only changes per global spec iteration.
Original comment by carsten....@codecentric.de
on 15 Jul 2014 at 1:01
It definitely makes sense as a general feature, but designing and implementing
it won't be trivial. If you are interested in contributing, please let us know.
Original comment by pnied...@gmail.com
on 15 Jul 2014 at 1:07
Original issue reported on code.google.com by
kl...@jumio.com
on 22 Nov 2012 at 9:48