|08:12 PM PST|
August 01, 2015
o Project Page
o Lists & IRC
o Kernel Errata
o LTP's Kernel Code Coverage
o LTP's Gcov Extension(lcov)
o LTP's Gcov-kernel Extension
o Coverage "Galaxy" Map
o LTP HowTo
o Inside LTP Testsuite
o 2.5 Execution Matrix
o 2.5 Test Plan
o 2.4 Test Plan
o STAX LTP Driver HowTo
o DOTS HowTo
o Linux Test Tools
o LTP man pages
o Expected errors for LTP
o Kernel Test Results
o 2002 Test Results
o 2001 Test Results
o Kernel Fix
o Open *POSIX Test Suite
o OpenHPI Test Suite
o (CTCS) Cerberus
o (STAF) Software Testing Automation Framework o EAL2+ Certification Test Suite o SuSE EAL3+ Certification Test Suite o Red Hat EAL3+ Certification Test Suite
Test Plan for 2.5 Stabilization
Table of Contents
The following terms are registered trademarks of International Business Machines Corporation in the United States and/or other countries: IBM, eServer, xSeries, pSeries, DB2, WebSphere. A full list of U.S. trademarks owned by IBM may be found at http://www.ibm.com/legal/copytrade.shtml.
Linux is a registered trademark of Linus Torvalds.
Other company, product, and service names may be trademarks or service marks of others.
By testing the 2.5 kernel while the kernel is still under development, the LTC Test team expects to help shorten the time required for the 2.6 kernel to stabilize.
As part of this effort, the LTC Test team is participating with the OSDL on 2.5 kernel stabilization Open Source project.
Although the LTC Test team will be using many different test tools and scripts, the team will not be running any formal functional test unless stated otherwise in this document.
For IBM eServer pSeries™ hardware the LTC Test team has access to three B80 machines, of which two are 2-way PPC64 machines and the third is a 4-way PPC64 machine. On these systems the team will run the following distributions:
Results information will be kept for all test runs. At minimum, the information gathered
will be either a log of TOP or SAR information collected during each run. If the individual
test suite creates any additional logs for a test run, those files will also
be kept. This information will be stored in a central repository
that is backed-up weekly.
There will be a minimal of six integration workloads. The workloads can be divided into three tests that are manual and three that are automated. The tests are as follows:
bugme.osdl.org. for xSeries machines and bugzilla.linux.ibm.com in the PPC64 Development Family for pSeries machines.
This section details the conditions that preclude entrance and exit from the test cycle.
In addition to the test cases listed in this document, several other software products will be used in testing on 2.5 kernels:
All of the following test cases will be run at least once. After running the following test cases, the LTC Test team will create a chart detailing if the test cases ran, if the test cases exposed any problems with the 2.5 kernel, and if the team will add the test cases to the standard 2.5 integration scenarios. This information will be documented in the Execution Plan found at IIOSB under Execution Plan for the 2.5 Stabilization Effort.
Execution PlanThe latest Execution Plan for 2.5 Stabilization can be found at Sourceforge under 2.5 Execution Matrix.