Onsi Fakhouri
Onsi Fakhouri
hey there - i think the issue might be on line 92-95 of tests.go. the closure captures `tests` which will be changed as you loop through `testsByClusterID`. you'll want `tests...
hey - that makes sense. the map issue should have been fixed in v2.7.0 - since that release ginkgo breaks ties for specs in the same location using the spec...
oh yes good catch - that’ll be a problem too. sorry this is so confusing :( there’s not a great way to ensure consistent order when a loop like this...
i really should add a checksum to validate that all trees are the same and give the user feedback. i’ll add that to the backlog.
thanks for adding the issue @pohly I'd like your input on some design questions. I can imagine two approaches: 1. `PreviewSpecs` simply constructs the spec tree and returns a `Report`...
I'm finally working on this and want to confirm that, just like `--dry-run`, `PreviewSpecs` will be mutually exclusive with `RunSpecs` and will require you to run in series. These constraints...
Hey @pohly and @Dannyb48 I now have a... preview of `PreviewSpecs` up on the master branch. The docs are [here](https://onsi.github.io/ginkgo/#previewing-specs) PTAL.
I'll take a look at allowing `PreviewSpecs` and `RunSpecs` to both run.
@pohly what about the constraint to run in series only?
actually - never mind. i think i've found a way around both constraints that isn't too expensive or too ugly. i'll push it to master after I add some tests