To be fair, none of these mistakes are currently covered by tests, so the best solution is to add more tests so this is automatically noticed. So far I have not had time to come up with a good (UI) test framework that does basic smoke tests like: - start a server, - start a target, - log in to the server, - import a set of artifacts, - associate them with a feature, a distribution, - hook all of them up, - store the changes, - validate that the target gets provisioned.
That's basically the smoke test I do manually a lot of the time (usually with a set of demo bundles from Felix, the famous drawing application). Greetings, Marcel On Feb 26, 2011, at 13:39 , Jean-Baptiste Onofré wrote: > Hi Marcel, > > For the Vaadin, maybe I made a mistake, I don't remember. > > For the Knopflerfish, I removed it before and readded it on friday. Maybe I > forgot something. > > Anyway, you're right, more than be able to build, testing the runtime is a > must have. > > My apologies, I will take attention of that in the future. > > Regards > JB > > On 02/26/2011 01:35 PM, Marcel Offermans wrote: >> Hey guys, >> >> This morning, while trying to work on another issue, I had to fix the build >> first because: >> >> a) somehow the Vaadin dependency was reverted back to the (not working) >> 6.5.0 version, instead of 6.5.1; >> b) the Knopflerfish log and useradmin bundles were missing from the >> ace-target-devserver. >> >> I know we're in a state of flux while improving the build, but please make >> sure things say in a working order. >> >> Greetings, Marcel >>
