<div dir="ltr"><div dir="ltr">On Wed, 11 Mar 2020 at 22:27, Stefan Kral <<a href="mailto:sk@typedivision.de">sk@typedivision.de</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>Doing build and test in one pipeline turns out to be more
complicated due to:
<p>- build machine may be different from test machine (with access
to hardware)<br>
- build the image is a one time job, tests may have to be repeated
reproducibly<br>
- executing long running tests slows down image creation (for
development)<br>
- tests on dedicated hardware should be runable asynchronously
when hw is available</p>
<p>Running tests by bitbake -c testimage could be an option but to
provide a full repo/bitbake/cache setup to run test cases sounds
not as easy as having just python installed. And for that,
testexport does its job quite well.<br>
</p>
<p>Btw. have you ever thought about to integrate/support some
external test framework (like robot framework)?<br></p></div></blockquote><div><br></div><div>Core project does all testing on qemu (using direct testimage); there are no resources to set up testing on real hardware. So those scenarios aren't well supported or tested, but patches/proposals welcome :)</div><div><br></div><div>Alex<br></div></div></div>