Closed staabm closed 10 years ago
Committing the database file after the run is another option. But other than that, a remote DB instance or a webservice is what comes to mind. On the other hand, for CI, I don’t really think it is a very interesting use case.
Closing for now as I really feel this is out of scope as the test runner is supposed to be used for development, not for CI.
I agree that it should not be a short term goal, but in general a fast failing/fast feedback loop in the CI is also appreciated...
I am not sure if it is at all possible, but I think we can discuss things here:
Atm I don't see a chance to use the testlistener in travis builds because all storage results are local in the build and cannot persist between ci builds.
One solution could use a remote db/webservice as a remote storage for travis builds. But maybe there is even a easier way to achieve the same thing?