Yocto Project 2.8 Release Test Plan: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(25 intermediate revisions by 2 users not shown)
Line 38: Line 38:
|-
|-
|}
|}
=References=
Documents that support this test plan


= Introduction =
= Introduction =
Line 60: Line 57:
= Risk Analysis & Contingency Plan =
= Risk Analysis & Contingency Plan =


This is the document for Risk Analysis https://docs.google.com/spreadsheets/d/1K-MZYo5sfabwI2UozGp6Uuh2sw5y309bXkyEZRPEEgk/edit#gid=0
QA identified risks for this release are mentioned here.
 
{| class="wikitable"
! style="text-align: center; font-weight: bold;" | Module
! style="text-align: center; font-weight: bold;" | Risk Description
! style="text-align: center; font-weight: bold;" | Risk Level
! style="text-align: center; font-weight: bold;" | Contingency plan
! style="text-align: center; font-weight: bold;" | Owner
|-
| style="text-align: center;" | BSP
| 54 manual test cases
| medium
| test cases to be automated
| Intel
|-
| style="text-align: center;" | Build Appliance
| 3 manual test cases, not executed by any QA team
| medium
| test cases to be automated
|
|-
| style="text-align: center;" | Compliance
| 4 manual test cases, not executed by any QA team
| medium
| test cases to be automated
|
|-
| style="text-align: center;" | Kernel dev
| 9 manual test cases, not executed by any QA team
| medium
| test cases to be automated
|
|-
| style="text-align: center;" | OE-Core
| 6 manual test cases
| medium
| test cases to be automated
| Intel
|-
| style="text-align: center;" | SDK
| 1 manual test case, not executed by any QA team
| medium
| test case to be automated
|
|-
| style="text-align: center;" | Toaster
| 93 manual test cases, not executed by any QA team
| medium
| test cases to be automated
|
|}


= Test Strategy =
= Test Strategy =
Line 69: Line 116:
The Yocto Project QA team verifies each release against recent versions of the most popular Linux distributions that provide stable releases.  
The Yocto Project QA team verifies each release against recent versions of the most popular Linux distributions that provide stable releases.  
  * centos 7  
  * centos 7  
* Debian 8
  * Debian 9
  * Debian 9
  * Fedora 26
  * Fedora 28
  * Fedora 27
  * Fedora 29
  * OpenSuse42.3
  * Fedora 30
* OpenSuse 150
* OpenSuse 151
* OpenSuse 423
* OpenSuse Tumbleweed
  * ubuntu 16.04  
  * ubuntu 16.04  
  * ubuntu 17.10
  * ubuntu 18.04


= Test Cases =
= Test Cases =
Line 83: Line 135:
* http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/sdk
* http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/sdk
* http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/sdkext
* http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/sdkext
== ADT ==
{| class="wikitable"
! style="text-align: center; font-weight: bold;" | Component
! style="text-align: center; font-weight: bold;" | Environment
! style="text-align: center; font-weight: bold;" | Auto
! style="text-align: center; font-weight: bold;" | Manual
! style="text-align: center; font-weight: bold;" | Owner
|-
| rowspan="2" style="text-align: center;" | ADT
| Fedora 25 i686
| Y
|
| AB
|-
| Ubuntu 16.04 x86_64
| Y
|
| AB
|}
== eSDK ==
{| class="wikitable"
! style="text-align: center;" | Component
! style="text-align: center;" | Environment
! style="text-align: center;" | Auto
! style="text-align: center;" | Manual
! style="text-align: center;" | Owner
|-
| rowspan="2" style="text-align: center;" | eSDK
| Any Distro + runtime
| Y
|
| AB
|-
| Any Distro + selftest
| Y
|
| AB
|}
== Selftest ==
{| class="wikitable"
! style="text-align: center;" | Component
! style="text-align: center;" | Environment
! style="text-align: center;" | Auto
! style="text-align: center;" | Manual
! style="text-align: center;" | Owner
|-
| rowspan="8" style="text-align: center;" | OE-CORE
| Ubuntu 16.04
| Y
|
| AB
|-
| Ubuntu 17.10
| Y
|
| AB
|-
| OpenSuse 42.3
| Y
|
| AB
|-
| Debian 9
| Y
|
| AB
|-
| Centos 7
| Y
|
| AB
|-
| Fedora 26
| Y
|
| AB
|-
| Fedora 27
| Y
|
| AB
|}


== OE-CORE ==
== OE-CORE ==
Line 187: Line 151:
| PG
| PG
|-
|-
|}
== Package Manager ==
{| class="wikitable"
! style="text-align: center;" | Component
! style="text-align: center;" | Environment
! style="text-align: center;" | Auto
! style="text-align: center;" | Manual
! style="text-align: center;" | Owner
|-
| Package Manager
| Any Distro
| Y
|
| AB
|}
|}


Line 323: Line 271:
| Y
| Y
|  
|  
|  
| Y
|
|
|-
|-
Line 332: Line 280:
| Y
| Y
|  
|  
|  
| Y
|
|
|-
|-
Line 341: Line 289:
| Y
| Y
|  
|  
|  
| Y
|
|
|-
|-
Line 459: Line 407:


All component to be tested on 2.8 are in [[#Test Items]] a detailed list of features per component can be found in Test Plan of the components [[QA_Master_Test_Plan#Component]]
All component to be tested on 2.8 are in [[#Test Items]] a detailed list of features per component can be found in Test Plan of the components [[QA_Master_Test_Plan#Component]]
<!--= Features pending to be tested =
<!--= Features pending to be tested =


Line 471: Line 417:
The complete List of QA Implementations for YP 2.8 can be found at [https://wiki.yoctoproject.org/wiki/2.8_QA_OWNED_BUGS Features Implementation by QA Team]
The complete List of QA Implementations for YP 2.8 can be found at [https://wiki.yoctoproject.org/wiki/2.8_QA_OWNED_BUGS Features Implementation by QA Team]
-->
-->
<!--= Features Not to be tested =
<!--= Features Not to be tested =
* TBD
* TBD
Line 477: Line 422:


=Approach=
=Approach=
Tests will be conducted per the documented test cases stored in Testopia. The test manager will create test runs for each tester. The tester will execute the tests in Testopia and mark each case as Pass / Fail / Skip /Blocked.
The tester should leave notes on actual results and any other relevant details when possible.


Once complete, the test manager should review the test run reports in Testopia and report back to the team by mail and in the wiki as a test report.
Testing will be done as per QA process defined in main QA wiki page at https://wiki.yoctoproject.org/wiki/QA#QA_Process.


= Pass / Fail Criteria =
= Pass / Fail Criteria =
Line 496: Line 439:
* Final Test report
* Final Test report
* Mail sent to the mailing list
* Mail sent to the mailing list
= Test Environment =
There are different environments and tools for every type of testing refer to [[QA_Master_Test_Plan#Test_Areas]] for more detailed information.


= Schedule =
= Schedule =
== M1 (Apr 29, 2019 to Jun 21, 2019)  ==
=== M1 Feature/Tasks Development / Cutoff is Jun. 9, 2019 ===
{{#bugzilla:
  |columns=id,from,to,estimated,summary,severity,priority,whiteboard,status
  |total=estimated
  |milestone=2.8 M1, 2.8 M2
  |severity=enhancement
  |sort=to,priority
}}
=== M1 Bugs ===
{{#bugzilla:
  |columns=id,from,to,estimated,summary,severity,priority,whiteboard,status
  |total=estimated
  |milestone=2.8 M1, 2.8 M2
  |severity=!enhancement
  |sort=to,priority
}}


The planed schedule for 2.8 can be found at [[Yocto_2.8_Schedule]]
The planed schedule for 2.8 can be found at [[Yocto_2.8_Schedule]]
Line 539: Line 457:
| 06/14/2019
| 06/14/2019
| DONE
| DONE
| https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2/
| https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults
|
|- bgcolor="93DB70"
|- bgcolor="93DB70"
| M2  
| M2  
|  
| 7/26/2019
|  
| 7/31/2019
|  
| DONE
|  
| https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=zeus&id=d550d40646e1ca78a4b5d106e1b20831208b4c37
|
|- bgcolor="93DB70"
|- bgcolor="93DB70"
| M3  
| M3  
|  
| 9/23/2019
|
| 9/26/2019
|  
| DONE
|  
| https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults
|
|- bgcolor="93DB70"
|- bgcolor="93DB70"
| M4
| 3.0
|
| 10/10/2019
|  
| 10/15/2019
|  
| DONE
|  
| https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults
|
|}
|}

Latest revision as of 07:16, 7 January 2020

{{#vardefine:ADT_MAUAL | 6539}} {{#vardefine:ADT_AUTO | 6540}} {{#vardefine:ANYQEMU_SATO_MANUAL | 6563}} {{#vardefine:ANYQEMU_SATO_AUTO | 6564}} {{#vardefine:ANYBSP_SATO_AUTO | 6558}} {{#vardefine:ANYBSP_LSB_AUTO | 6561}} {{#vardefine:ANYBSP_WIC_AUTO | 6560}} {{#vardefine:MMAX_CORE2_MANUAL | 6554}} {{#vardefine:MMAX_I7_MANUAL | 6557}} {{#vardefine:NUC_I7_MANUAL | 6556}} {{#vardefine:NUC_GEX86-64_MANUAL | 6555}} {{#vardefine:MMAX_GEX86-32_MANUAL | 6553}} {{#vardefine:GAL_SATO_AUTO | 6565}} {{#vardefine:CROPS_AUTO | 6541}} {{#vardefine:CROPS_MANUAL | 6542}} {{#vardefine:ECLIPSE_MANUAL | 6543}} {{#vardefine:KERNEL_MANUAL | 6714}} {{#vardefine:METAYOCTO_MANUAL | 6544}} {{#vardefine:TOASTER_AUTO | 6545}} {{#vardefine:TOASTER_MANUAL | 6546}} {{#vardefine:ESDK_MANUAL | 6547}} {{#vardefine:ESDK_AUTO | 6548}} {{#vardefine:OE-CORE_AUTO | 6549}} {{#vardefine:BITBAKE_AUTO | 6550}} {{#vardefine:RUNTIME_AUTO | 6551}} {{#vardefine:BUILD-APPLIANCE_AUTO | 6552}}

Reversion history

Version Modifier Comments
1.0 Jain Sangeeta First draft

Introduction

This is the the overall test plan for version 2.8 of the Yocto Project, for all the generic information this document will be pointing to QA Master Test Plan

Objectives

This test plan for Yocto Project 2.8 release supports the following objectives:

  • To define the tools to be used throughout the testing process.
  • To communicate to the responsible parties the items to be tested, set expectations around schedule, and define environmental needs.
  • To define how the tests will be conducted.
  • Release Criteria
  • Risks and contingencies

QA_Master_Test_Plan#Objectives_and_Tasks

Risk Analysis & Contingency Plan

QA identified risks for this release are mentioned here.

Module Risk Description Risk Level Contingency plan Owner
BSP 54 manual test cases medium test cases to be automated Intel
Build Appliance 3 manual test cases, not executed by any QA team medium test cases to be automated
Compliance 4 manual test cases, not executed by any QA team medium test cases to be automated
Kernel dev 9 manual test cases, not executed by any QA team medium test cases to be automated
OE-Core 6 manual test cases medium test cases to be automated Intel
SDK 1 manual test case, not executed by any QA team medium test case to be automated
Toaster 93 manual test cases, not executed by any QA team medium test cases to be automated

Test Strategy

Is followed the general strategy defined on QA_Master_Test_Plan#Testing_Strategy and below is showed specific information applicable only for 2.8 Release

Test Items

The Yocto Project QA team verifies each release against recent versions of the most popular Linux distributions that provide stable releases. 

* centos 7 
* Debian 8
* Debian 9
* Fedora 28
* Fedora 29
* Fedora 30
* OpenSuse 150
* OpenSuse 151
* OpenSuse 423
* OpenSuse Tumbleweed
* ubuntu 16.04 
* ubuntu 18.04

Test Cases

OE-CORE

Component Environment Auto Manual Owner
OE-CORE Ubuntu 16.04 Y PG

BSP/QEMU

Component Arch HW Environment Image Auto Manual pTest Compliance ltp
BSP x86 MinwTurbot 32bit genericx86 core-image-sato-sdk Y
core-image-lsb-sdk Y
Coffee Lake genericx86-64 core-image-sato-sdk Y Y
core-image-lsb-sdk Y
NUC 6 genericx86-64 core-image-sato-sdk Y Y Y
core-image-lsb-sdk Y Y
NUC 7 genericx86-64 core-image-sato-sdk Y Y
core-image-lsb-sdk Y
QEMU qemux86 core-image-sato-sdk Y Y
core-image-lsb-sdk Y
qemux86-64 core-image-sato-sdk Y Y
core-image-lsb-sdk Y
non x86 EdgeRouter EdgeRouter core-image-sato-sdk Y Y Y
MPC8315e-rdb MPC8315e-rdb core-image-sato-sdk Y Y Y
Beaglebone Black Beaglebone core-image-sato-sdk Y Y Y
QEMU qemuarm core-image-sato-sdk Y Y
qemuarm-64 core-image-sato-sdk Y Y Y Y
qemuppc core-image-sato-sdk Y Y
qemumips core-image-sato-sdk Y Y
qemumips64 core-image-sato-sdk Y Y
Meta-Intel MinwTurbot 32bit core2-32 core-image-sato-sdk Y
core-image-lsb-sdk Y
Coffee Lake corei7-64 core-image-sato-sdk Y Y
core-image-lsb-sdk Y
NUC 6 corei7-64 core-image-sato-sdk Y
core-image-lsb-sdk Y
NUC 7 corei7-64 core-image-sato-sdk Y Y
core-image-lsb-sdk Y
poky-tiny Y

All component to be tested on 2.8 are in #Test Items a detailed list of features per component can be found in Test Plan of the components QA_Master_Test_Plan#Component

Approach

Testing will be done as per QA process defined in main QA wiki page at https://wiki.yoctoproject.org/wiki/QA#QA_Process.

Pass / Fail Criteria

This criteria is defined in Yocto_Project_v2.8_Status#Yocto_Project_v2.8_Release_Criteria

Exit Criteria

As defined in QA_Master_Test_Plan#Entry and Exit Criteria

Test Deliverables

  • Final Test results
  • Final Test report
  • Mail sent to the mailing list

Schedule

The planed schedule for 2.8 can be found at Yocto_2.8_Schedule

Live Schedule & Execution History

MILESTONE STARTED FINISHED STATUS REPORT
M1 rc2 06/11/2019 06/14/2019 DONE https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults
M2 7/26/2019 7/31/2019 DONE https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=zeus&id=d550d40646e1ca78a4b5d106e1b20831208b4c37
M3 9/23/2019 9/26/2019 DONE https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults
3.0 10/10/2019 10/15/2019 DONE https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project_2.8_Release_Test_Plan&oldid=66808"