Bug 5614 - Automated testing master image generation / operation
Summary: Automated testing master image generation / operation
Status: RESOLVED FIXED
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 1.6
Hardware: All Multiple
: High enhancement
Target Milestone: 1.6 M5
Assignee: Stefan Stanacar
QA Contact:
URL:
Whiteboard: 17 April 2014: Marked documentation f...
Depends on:
Blocks: 1596 5615
  Show dependency tree
 
Reported: 2013-11-29 18:26 UTC by Paul Eggleton
Modified: 2014-04-17 19:22 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Done (doc changes complete)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2013-11-29 18:26:19 UTC
For the automated testing, in order to deploy test images onto the hardware so we can boot into them, we need a "known good" image (referred to here as a "master" image) that we can first boot into in a separate partition, then interact with in order to deploy the image to be tested. This should be straightforward - we just need to send the image over ssh and extract/copy it onto the test partition. 

Thus this task involves:

1. Adding a recipe for a "master" image

2. Writing some code to interact with it to deploy the test image

3. Providing a means of setting up the partition layout, presumably using wic.
Comment 1 Stefan Stanacar 2014-03-31 10:00:06 UTC
Patches on the ML. 
Some notes: 
 1 and 3 - have been combined (wic wasn't used for now) - the partition layout is done from the installer thus the master image recipe.
 2 - code for TEST_TARGET = "GummibootTarget" exists, that works for EFI hardware only. Other BSP will probably need to subclass that and adapt for their bootloaders.
Comment 3 Paul Eggleton 2014-04-14 13:10:24 UTC
I think we can mark this one as resolved for 1.6. If we have further enhancements we can add additional enhancement bugs to cover them.
Comment 4 Scott Rifenbark 2014-04-15 21:51:19 UTC
What about the doc component for this release?  Is there something we need to cover?

Scott
Comment 5 Paul Eggleton 2014-04-16 08:39:07 UTC
Documentation should be covered by the automated testing additions that we did. We might want to add core-image-testmaster to the list of images in ref-images.xml though.
Comment 6 Scott Rifenbark 2014-04-17 13:56:12 UTC
Hi, 

See http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#ref-images for the list of images.  I have added the core-image-testmaster image to the list.  I need the description reviewed and approved before I can turn the doc flag on this bug. 

Scott
Comment 7 Paul Eggleton 2014-04-17 14:22:54 UTC
For the description could we say this instead:

A "master" image designed to be used for automated runtime testing. Provides a "known good" image that is deployed to a separate partition so that you can boot into it and use it to deploy a second image to be tested.

It may also be good to finish with a "more information" link to the automated runtime testing section as well.
Comment 8 Scott Rifenbark 2014-04-17 19:22:02 UTC
Hi Paul, 

I have implemented your suggestion.  You can see the change at http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#ref-images.  I am marking this documentation flag to "Done".

Scott