In case you're wondering why I'm doing this, here's the explanation:
Our tests are run against a production snapshot of our database. This ensures that our tests are executing against the latest schema and any changes that may have made it into production. I'm not convinced this is the best way to go, but for now it's the only way to ensure existing data/schema doesn't break any of our assumptions.
1 of 1 people found this helpful
currently it's unfortunately not possible. Database content is cleaned after each test execution. However I'm aware that it should be more flexible and you should consider it improved with Alpha4
Thanks a lot for your feedback!
Thanks Bartosz -- pleaes ignore my cross-post on my other discussion ;-)
If it bothers me enough, I'll add a config option and submit a pull request.