On Thu, 2014-06-12 at 14:21 +0000, Kervinen, Antti wrote: > > There are plenty of test frameworks. The question still stands: > > are we allowed to run them as part of the .spec file and how do > > we get test results back out of an OBS build? > > The need for this kind of test automation is obvious. When a developer > changes code, tests may notice that something broke up. Those tests > may have be written for the modified component, or for some other > component that took a hit from the change. > > Regardless of the problem being in the code or in the tests, as a > developer, I would like to get an immediate a notification on the > problem. After that, I would like to access test logs, download the > image, and download the tests that were executed. Especially > important, of course, are the tests that I broke. After that, I would > be able to fix my code, broken tests, or both. > > In the system that Igor described, tests are written in separate test > packages that are installed on the system that is connected to Tizen > IVI HW.
How would that work when building in OBS (see question above)? What you describe sounds like it is targeting developers who have a development work station and a separate device running some Tizen image. In OBS, there is only a Tizen build chroot, but not a fully booted Tizen image. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
