Bug 8455 - QA: Add tests to empty image
Summary: QA: Add tests to empty image
Status: RESOLVED FIXED
Alias: None
Product: Test Plans/Suite
Classification: QA/Testing
Component: test-plans/suite (show other bugs)
Version: 5.99
Hardware: x86 Multiple
: Medium minor
Target Milestone: Future
Assignee: New Comer Bugs
QA Contact:
URL:
Whiteboard: NEWCOMER
Depends on:
Blocks:
 
Reported: 2015-10-07 15:55 UTC by Alex Franco
Modified: 2021-02-14 11:09 UTC (History)
10 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Franco 2015-10-07 15:55:24 UTC 
As suggested by Paul Eggleton, an oe-selftest test should be added to ensure meta-selftest/recipes-test/images/test-empty-image.bb builds and is empty.
Comment 1 Alex Franco 2015-10-07 16:00:09 UTC 
Testing that test-empty-image builds is straightforward enough, but I'd like to better define a test for its emptiness.

Although PACKAGE_INSTALL, IMAGE_INSTALL and IMAGE_LINGUAS are empty for this image, it does inherit some "contents" from image. So, perhaps there are tests for "image" we can adapt for test-empty-image? What does a truly empty image look like?
Comment 2 Paul Eggleton 2015-10-20 07:25:08 UTC 
Well, a truly empty image would contain no files; unfortunately AFAIK that isn't currently possible because of bug 6478.

For now we just need a test that ensures that an empty image has no packages in it (i.e. nothing in the manifest).
Comment 3 Leonardo Sandoval Gonzalez 2016-05-25 20:50:50 UTC 
moving to 2.3, due to limited resources.
Comment 4 Jair Gonzalez 2017-08-29 21:44:45 UTC 
Moving to 2.5, due to limited resources.
Comment 5 Armin Kuster 2019-12-22 19:17:08 UTC 
this still seems reasonable.
Comment 6 khairul.rohaizzat.jamaluddin 2020-09-23 21:02:11 UTC 
Hi everyone,

I'm looking to try and work on this ticket.

I compared the contents of core-image-minimal/core-image-sato with test-empty-image and found that these 3 items always exists in all 3 cases.
   1. lost+found
   2. etc
   3. var

Is this the expected default files to exist in every image built (even on an 'empty' build)?

Also, need some clarification with the requirement of this ticket.

Current plan for this selftest case is to check in the 1st partition of the image built for these 3 items only. If additional files exists in the partition, it would be a failing case.

Please do correct me if my assumption/plan is off.
Comment 7 milan.opensource 2021-01-12 13:44:29 UTC 
The patch is sent to OE-Core mailing list for review.
Comment 8 milan.opensource 2021-02-14 11:07:57 UTC 
assign the bug to the default assignee as someone else has already made changes and those are merged to master.

Please update bugz whoever has worked on it.