<div dir="ltr"><div dir="ltr">On Wed, 11 Mar 2020 at 21:38, 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">I just started to evaluate the use of testexport.<br>
<br>
If you think about removing that feature, what is the preferred way to <br>
test a deployed target image?<br>
The idea here is to have two separate pipelines:<br>
<br>
1. build<br>
- a target-image-test (same as target-image but additional test <br>
facilities enabled, like ptest)<br>
- the testexport output<br>
<br>
2. test<br>
- fetch build results and install the target-image-test to the real hardware<br>
- run the exported runtime tests (host and target based cases)<br>
- check/save the generated testresults.json<br></blockquote><div><br></div><div>You can do all of these in a single pipeline using testimage:</div><div><br></div><div>1. built target-image-test</div><div>2. flash target-image-test to real hardware</div><div>3. bitbake -c testimage target-image-test (set TEST_TARGET to 'simpleremote', and ip/port for ssh access in local.conf)</div><div><br></div><div>Is there a reason you need two pipelines?</div><div><br></div><div>Alex<br></div></div></div>