Bug 12411

Summary: Add automation for eSDK artifacts downloaded from the autobuilder
Product: [QA/Testing] Manual Testing Reporter: Joshua Lock <joshuagloe>
Component: manual-testingAssignee: Unassigned <unassigned>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Medium+ CC: akuster808, brian.avery, randy.macleod
Version: unspecified   
Target Milestone: 6.99   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Joshua Lock 2017-12-08 14:40:16 UTC
We need to add some manual test cases to better test the eSDK artefacts generated during a release, we have had issues reported in the past with the generated artefacts and therefore we need to design some tests to try and prevent such failures in future release.

Brian; could you provide some more background/context on the failures we've seen in the past?

The test case should exercise real-world usage patterns, including installation of additional features (from the yp.o sstate mirror). In #11963 Brian suggested "The linux kernel workflow is a good test since it is how a number of users will leverage the esdk in the next release given our new kernel documentation."

Kernel documentation is http://www.yoctoproject.org/docs/2.4/kernel-dev/kernel-dev.html and the eSDK workflow should be easy to follow.
Comment 1 Joshua Lock 2017-12-08 14:41:12 UTC
This bug is solely to track definition of a new manual testcase, automation is a future task covered by #11963.
Comment 2 akuster 2020-05-07 08:18:44 UTC
The idea is to have the automated step to test the build artifacts for a release before a release is announced.

Something in the line of "release" selftest type operation.
Comment 3 Randy MacLeod 2023-10-24 14:24:39 UTC
Bulk move from 4.99 or 0.00 to 5.99