Distro Testing Plan

This article is the test plan for Distro testing

About Distro Testing

Distro Testing is intended to catch bugs that are distribution specific using the yocto-autobuilder.

Objectives

• Verify that Distro executes oe-selftest
• Verify that Dsitro is able to execute componenets (Eclipse, Toaster, WIC)
• Veirfy that Distro is able to build per package type (IPK, DEB, RPM)
• Verify that Distro is able to build different image types (LSB, non LSB)
• Verify that Distro is able to build per architecture (arm, x86)
• Verify that Distro is able to build per bootloader (systed, init)
• Verify that Distro is able to build poky-tiny
• Verify that Distro executes multilib

Test Strategy

The strategy will be divided in two groups one executed once in GDC autobuilders when the Distro is released (one time testing) and another tested continuously on public autobuilders

GDC Autobuilder

The first time that Distro is released it will be installed on GDC autobuilder and a series of build steps going to be applied to that Distro, once very build set is PASS that distro will be added to the list of supported Distros by QA, this is a only one time testing activity, not executed in every milestone o release test cycle.

Steps

Public Autobuilder

Once the distro was first time validated by QA team it will be running on public autobuilder different build set already defined [[]], after that it going to be under the focus of SWAT team

Process

This section describes the process to add a new Distro as supported on Yocto Project

Install Distro

To Be Updated

Execute Build Sets

Build sets to be executed are defined in below table, to add a Distro as supported all the build sets should be PASS

RPM	DEB	IPK	Component	Multilib	World	oe-selftest
ARM	x86_64	x86_32	Eclipse	x86 64/32	x86_64
init	systemd	systemd	Toaster	x86 64/x32	systemd
poky_lsb	poky	poky_tiny	buildtools	core-image-sato	poky
core-image-lsb	core-image-sato-sdk	core-image-minimal	read_only rootfs	poky	core-image-sato-sdk
			pam	init/systemd
			Log rotate	RPM,DEB,IPK

Update Supported Distro

Once all the build sets were executed and all were PASS at least once the Distro can be added to the list of supported Dsitros

meta-poky/conf/distro/poky.conf
-----
SANITY_TESTED_DISTROS ?= " \
             poky-1.7 \n \
             poky-1.8 \n \
             poky-2.0 \n \
             Ubuntu-14.04 \n \
             Ubuntu-14.10 \n \
             Ubuntu-15.04 \n \
             Ubuntu-15.10 \n \
             Ubuntu-16.04 \n \
             Fedora-21 \n \
             Fedora-22 \n \
             Fedora-23 \n \
             CentOS-6.* \n \
             CentOS-7.* \n \
             Debian-7.* \n \
             Debian-8.* \n \
             openSUSE-project-13.2 \n \

Test execution Cycle

GDC Autobuilder

• The execution cycle should be applied only one time when Distro is installed on the autobuilder, results under focus of QA team

Public Autobuilder

• There will be a continuous execution of random build sets defined on autobuilder, results under foucs of SWAT team

Release Criteria/ Exit Criteria

• All the defined build steps are PASS #Execute Build Steps
• Distro was added to the supported list #Update Supported Distros