Open pieterb opened 11 years ago
Well, at the moment, we don't even have an exhaustive test suite, although lately one of my colleagues wrote some scripts that test the core web service functionality, as part of our Nagios-based service monitoring system at SARA.
And Tibor has started writing some Cucumber tests. I saw they've been checked in here at GitHub, but I didn't have time to take a look at them yet. I think that, ideally, we could take the following steps:
I don't think CI would be overkill if you have already decided to write tests. From writing tests to CI it is basicly just a few more steps:
Regarding point 2., it is of course a main decision on how exhaustive to do this. Do you just load new code to an existing JRuby env or do you set up a completely new env, starting from scratch with no dependencies installed etc.? The latter option would have uncovered the issue with d8e67624ffef90862fb026574f1dbd2c2db0ec78 even without exhaustive test cases, because it was a configuration error. Given that we did spent at least one collaborative hour trying to narrow this down, I don't think CI is too wasteful. I do however agree that CI is not a top priority while we are still getting the governance and organizational framework together.
Hello Everyone,
in order to ensure that Tibor and my development on the EPIC API does not break any existing functionality new cucumber features using Httparty were written today. The features cover all CRUD operations of the service. However they are not an exhaustive test-suite. The tests can be found under the commit: 15689cc8541d2ab6ff3d723c2eb972bd170c6cc9 in the tkalman branch.
Best Regards Oliver
Tobias Weigel wrote:
Ulrich Schwardmann wrote:
Tobias Weigel wrote: