On 12 June 2014 15:47, Patrick Ohly <[email protected]> wrote: > On Thu, 2014-06-12 at 15:03 +0300, Stoppa, Igor wrote:
[...] > I was describing my experience as a developer contributing to Moblin, > MeeGo and Tizen. During all that time, it has never been easy (or > possible at all) for a developer to run the QA tests themselves before > committing some potentially broken code into a git tree. I sympathize :-) Luckily Maemo provide a much more pleasant experience :-D I hope we can bring that back, eventually. > It's good to hear that at least the REs now have an easier access to > those tests; developers still don't. RE is easier to address as first step - it's a smaller target group. But there is no reason why developers should be left out in the cold. We just had to start from somewhere. [...] > Actually it's both: ideally, developers run tests before "git commit" > and "gbs submit", so that's before packaging. I tend to prefer, at least as final step of verification before submission, doing a mock execution of the full build process, which involves producing package(s) and image to flash (locally, not on the build farm). [...] > There are plenty of test frameworks. True, however the learning curve can be very different. > The question still stands: are we > allowed to run them as part of the .spec file and >From my POV anything goes, as long as it is possible to tell apart the various set of test cases and when they should be run. The spec file looks like a good place, but I suggest bringing this up in the arch forum. I think the approach should be standardized. > how do we get test > results back out of an OBS build? I'm working on this patch and should be ready very soon, but I do not have enough visibility (yet) to say when it will be released to tizen.org OBS. However I believe that it will be definitely deployed by the time the .spec question has been solved. -- cheers, igor _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
