Yocto Project 2.8 Release Test Plan: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(42 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.
 
= 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 9
* Fedora 26
* Fedora 27
* OpenSuse42.3
* ubuntu 16.04
* ubuntu 17.10
 
= Test Cases =
 
* http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/runtime
* http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/selftest
* http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/manual
* 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
 
== ADT ==


{| class="wikitable"
{| class="wikitable"
! style="text-align: center; font-weight: bold;" | Component
! style="text-align: center; font-weight: bold;" | Module
! style="text-align: center; font-weight: bold;" | Environment
! style="text-align: center; font-weight: bold;" | Risk Description
! style="text-align: center; font-weight: bold;" | Auto
! style="text-align: center; font-weight: bold;" | Risk Level
! style="text-align: center; font-weight: bold;" | Manual
! style="text-align: center; font-weight: bold;" | Contingency plan
! style="text-align: center; font-weight: bold;" | Owner
! style="text-align: center; font-weight: bold;" | Owner
|-
|-
| rowspan="2" style="text-align: center;" | ADT
| style="text-align: center;" | BSP
| Fedora 25 i686
| 54 manual test cases
| Y
| medium
|  
| test cases to be automated
| AB
| Intel
|-
|-
| Ubuntu 16.04 x86_64
| style="text-align: center;" | Build Appliance
| Y
| 3 manual test cases, not executed by any QA team
| medium
| test cases to be automated
|  
|  
| AB
|}
== Kernel ==
{| 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
|-
|-
| Kernel
| style="text-align: center;" | Compliance
| Any Distro
| 4 manual test cases, not executed by any QA team
| medium
| test cases to be automated
|  
|  
| Y
| PG
|}
== Meta-Yocto ==
{| 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
|-
|-
| Meta-Yocto
| style="text-align: center;" | Kernel dev
| Any Distro
| 9 manual test cases, not executed by any QA team
| medium
| test cases to be automated
|  
|  
| Y
| PG
|}
== Toaster ==
{| 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
|-
|-
| Toaster
| style="text-align: center;" | OE-Core
| Any Distro
| 6 manual test cases
|
| medium
| Y
| test cases to be automated
| PG
| Intel
|}
 
== 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
| style="text-align: center;" | SDK
| Any Distro + runtime
| 1 manual test case, not executed by any QA team
| Y
| medium
| test case to be automated
|  
|  
| PG
|-
|-
| Any Distro + selftest
| style="text-align: center;" | Toaster
| Y
| 93 manual test cases, not executed by any QA team
| medium
| test cases to be automated
|  
|  
| PG
|}
|}


== Selftest ==
= Test Strategy =


{| class="wikitable"
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
! 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
|
| PG
|-
| Ubuntu 17.10
| Y
|
| PG
|-
| OpenSuse 42.3
| Y
|
| PG
|-
| Debian 9
| Y
|
| PG
|-
| Centos 7
| Y
|
| PG
|-
| Fedora 26
| Y
|
| PG
|-
| Fedora 27
| Y
|
| PG
|}


== Bitbake ==
= 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


{| class="wikitable"
= Test Cases =
! 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
|-
| Bitbake
| Any Distro
|
| Y
| PG
|}


== Build - Apliance ==
* http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/runtime
* http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/selftest
* http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/manual
* 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


{| class="wikitable"
== OE-CORE ==
! 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
|-
| Build - Apliance
| VM - Any Distro
|
| Y
| PG
|}
 
== Package Manager ==


{| class="wikitable"
{| class="wikitable"
Line 261: Line 145:
! style="text-align: center;" | Owner
! style="text-align: center;" | Owner
|-
|-
| Package Manager
| rowspan="8" style="text-align: center;" | OE-CORE
| Any Distro
| Ubuntu 16.04
| Y
|  
|  
| PG
|}
== Performance ==
{| 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;" | Performance
| Centos 7
| Y
| Y
|
| PG
| PG
|-
|-
| Ubuntu 16.04
| Y
|
| PG
|}
|}


Line 301: Line 165:
! pTest
! pTest
! Compliance
! Compliance
!  ltp
|-
|-
| rowspan="30" style="text-align: center;" | BSP
| rowspan="30" style="text-align: center;" | BSP
Line 311: Line 176:
|  
|  
|  
|  
|
|-
|-
| core-image-lsb-sdk
| core-image-lsb-sdk
Line 317: Line 183:
|  
|  
|  
|  
|
|-
|-
| rowspan="2" style="text-align: center;" | MinwTurbot 64bit
| rowspan="2" style="text-align: center;" | Coffee Lake
| rowspan="2" style="text-align: center;" | genericx86-64
| rowspan="2" style="text-align: center;" | genericx86-64
| core-image-sato-sdk
| core-image-sato-sdk
Line 325: Line 192:
|  
|  
|  
|  
|
|-
|-
| core-image-lsb-sdk
| core-image-lsb-sdk
Line 331: Line 199:
|  
|  
|  
|  
|
|-
|-
| rowspan="2" style="text-align: center;" | NUC 6
| rowspan="2" style="text-align: center;" | NUC 6
Line 339: Line 208:
| Y
| Y
|  
|  
| Y
|-
|-
| core-image-lsb-sdk
| core-image-lsb-sdk
Line 345: Line 215:
|  
|  
| Y
| Y
|
|-
|-
| rowspan="2" style="text-align: center;" | NUC 7
| rowspan="2" style="text-align: center;" | NUC 7
Line 353: Line 224:
|  
|  
|  
|  
|
|-
|-
| core-image-lsb-sdk
| core-image-lsb-sdk
Line 359: Line 231:
|  
|  
|  
|  
|
|-
|-
| rowspan="4" style="text-align: center;" | QEMU
| rowspan="4" style="text-align: center;" | QEMU
Line 367: Line 240:
|  
|  
|  
|  
|
|-
|-
| core-image-lsb-sdk
| core-image-lsb-sdk
Line 373: Line 247:
|  
|  
|  
|  
|
|-
|-
| rowspan="2" style="text-align: center;" | qemux86-64
| rowspan="2" style="text-align: center;" | qemux86-64
Line 380: Line 255:
|  
|  
|  
|  
|
|-
|-
| core-image-lsb-sdk
| core-image-lsb-sdk
Line 386: Line 262:
|  
|  
|  
|  
|
|-
|-
| rowspan="8" style="text-align: center;" | non x86
| rowspan="8" style="text-align: center;" | non x86
Line 394: Line 271:
| Y
| Y
|  
|  
|  
| Y
|
|-
|-
| style="text-align: center;" | MPC8315e-rdb
| style="text-align: center;" | MPC8315e-rdb
Line 402: Line 280:
| Y
| Y
|  
|  
|  
| Y
|
|-
|-
| style="text-align: center;" | Beaglebone Black
| style="text-align: center;" | Beaglebone Black
Line 410: Line 289:
| Y
| Y
|  
|  
|  
| Y
|
|-
|-
| rowspan="5" style="text-align: center;" | QEMU
| rowspan="5" style="text-align: center;" | QEMU
Line 419: Line 299:
|  
|  
|  
|  
|
|-
|-
| qemuarm-64
| qemuarm-64
| core-image-sato-sdk
| core-image-sato-sdk
| Y
| Y
| Y
| Y
| Y
|  
|  
|  
| Y
|-
|-
| qemuppc
| qemuppc
Line 433: Line 315:
|  
|  
|  
|  
|
|-
|-
| qemumips
| qemumips
Line 440: Line 323:
|  
|  
|  
|  
|
|-
|-
| qemumips64
| qemumips64
Line 447: Line 331:
|  
|  
|  
|  
|
|-
|-
| rowspan="10" style="text-align: center;" | Meta-Intel
| rowspan="10" style="text-align: center;" | Meta-Intel
Line 456: Line 341:
|  
|  
|  
|  
|
|-
|-
| core-image-lsb-sdk
| core-image-lsb-sdk
Line 462: Line 348:
|  
|  
|  
|  
|
|-
|-
| rowspan="2" style="text-align: center;" | MinwTurbot 64bit
| rowspan="2" style="text-align: center;" | Coffee Lake
| rowspan="2" style="text-align: center;" | corei7-64
| rowspan="2" style="text-align: center;" | corei7-64
| core-image-sato-sdk
| core-image-sato-sdk
Line 470: Line 357:
|  
|  
|  
|  
|
|-
|-
| core-image-lsb-sdk
| core-image-lsb-sdk
Line 476: Line 364:
|  
|  
|  
|  
|
|-
|-
| rowspan="2" style="text-align: center;" | NUC 6
| rowspan="2" style="text-align: center;" | NUC 6
Line 484: Line 373:
|  
|  
|  
|  
|
|-
|-
| core-image-lsb-sdk
| core-image-lsb-sdk
Line 490: Line 380:
|  
|  
|  
|  
|
|-
|-
| rowspan="3" style="text-align: center;" | NUC 7
| rowspan="3" style="text-align: center;" | NUC 7
Line 498: Line 389:
|  
|  
|  
|  
|
|-
|-
| core-image-lsb-sdk
| core-image-lsb-sdk
Line 504: Line 396:
|  
|  
|  
|  
|
|-
|-
| poky-tiny
| poky-tiny
Line 510: Line 403:
|  
|  
|  
|  
|
|}
|}


All component to be tested on 2.7 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 =


TBD
TBD
Line 523: Line 416:


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
-->


=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 547: 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 590: 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"