Yocto 1.3 Overall Test Plan - Revision history

Jiajun at 14:11, 26 May 2012

2012-05-26T14:11:33Z

← Older revision		Revision as of 14:11, 26 May 2012
Line 5:		Line 5:
	\|-		\|-
	\| 0.3 \|\| Jiajun Xu \|\| Initial Version		\| 0.3 \|\| Jiajun Xu \|\| Initial Version
			\|-
			\| 0.4 \|\| Jiajun Xu \|\| Updated with comments from Yi Zhao, Hongna Xu and Yilong Sun
	\|}		\|}

2012-05-23T02:44:18Z

Functional Test

← Older revision		Revision as of 02:44, 23 May 2012
Line 167:		Line 167:
	* QA Testing Completed: It means QA finishes validation of a new feature and send the result on bugzilla or send to developer.		* QA Testing Completed: It means QA finishes validation of a new feature and send the result on bugzilla or send to developer.
	* No QA needed: It means there is no need to design any testcases for a new feature or QA has no resource to cover it.		* No QA needed: It means there is no need to design any testcases for a new feature or QA has no resource to cover it.
			* Covered by current QA Test Plan: It means current QA test plan already covers the feature. No new cases needed.

	'''Test Frequency''': New Feature test is a continuous QA work within feature development phase. After one new feature is finished, testcases for it will be added into weekly or fullpass test.		'''Test Frequency''': New Feature test is a continuous QA work within feature development phase. After one new feature is finished, testcases for it will be added into weekly or fullpass test.

2012-05-23T02:09:53Z

Test Strategy and Approach

2012-05-23T02:09:34Z

Test Strategy and Approach

2012-05-23T02:08:44Z

Core Build System(Covered in Weekly/Fullpass Test)

← Older revision		Revision as of 02:08, 23 May 2012
Line 240:		Line 240:
	** Package History		** Package History
	** ... etc		** ... etc
	* Distribution support Test: Test Core ~~buld~~ on latest CentOS, Ubuntu, Fedora and Opensuse Hosts		* Distribution support Test: Test Core build on latest CentOS, Ubuntu, Fedora and Opensuse Hosts
	* WebHob & Hob2 Test: Main UI and component functionality are validated		* WebHob & Hob2 Test: Main UI and component functionality are validated
	* Performance Test: Check Core build performance on standard host(Defined in perfromance test webpage)		* Performance Test: Check Core build performance on standard host(Defined in perfromance test webpage)

2012-05-22T01:19:33Z

ADT Test(Covered in Weekly Test)

2012-05-22T01:19:11Z

Core Build System(Covered in Weekly/Fullpass Test)

← Older revision		Revision as of 01:19, 22 May 2012
Line 235:		Line 235:
	==== Core Build System(Covered in Weekly/Fullpass Test) ====		==== Core Build System(Covered in Weekly/Fullpass Test) ====
	* Functionality Test: Test Core build feature on standard host configuration. For example:		* Functionality Test: Test Core build feature on standard host configuration. For example:
			** Build Appliance
	** multilib		** multilib
	** PR service		** PR service
	** Package History		** Package History
	** ... etc		** ... etc
	* Distribution support Test: Test Core buld on latest Ubuntu, Fedora and Opensuse Hosts		* Distribution support Test: Test Core buld on latest CentOS, Ubuntu, Fedora and Opensuse Hosts
	* Hob2 Test: Main UI and component functionality are validated		* WebHob & Hob2 Test: Main UI and component functionality are validated
	* Build appliance Test: Functionality and performance of self-hosted image are tested
	* Performance Test: Check Core build performance on standard host(Defined in perfromance test webpage)		* Performance Test: Check Core build performance on standard host(Defined in perfromance test webpage)

2012-05-22T01:18:18Z

Test Infrastructure

← Older revision		Revision as of 01:18, 22 May 2012
Line 217:		Line 217:

	=== Test Infrastructure ===		=== Test Infrastructure ===
	If QA has resource, test infrastructure will be investigated in Yocto v1.2. Automation test cases development should be test infrastructure independent.		If QA has resource, test infrastructure will be investigated in Yocto v1.3. Automation test cases development should be test infrastructure independent.

	=== Test Design ===		=== Test Design ===

2012-05-22T01:17:32Z

Test Automation

← Older revision		Revision as of 01:17, 22 May 2012
Line 212:		Line 212:
	To reduce testing time, test automation will be adopted in the testing. Part of following tests will be implemented as automation:		To reduce testing time, test automation will be adopted in the testing. Part of following tests will be implemented as automation:
	* BSP/QEMU functionality tests		* BSP/QEMU functionality tests
	* Hob2 tests
	* Build feature tests		* Build feature tests

	'''Note''': Currently only sanity tests(10 cases) are fully ~~automated. For 1.2, QA will make more than 60%(80-100 cases) cases~~ automated.		'''Note''': Currently only sanity tests(10 cases) are fully automated.

	=== Test Infrastructure ===		=== Test Infrastructure ===

2012-05-22T01:16:53Z

Fullpass Test

← Older revision		Revision as of 01:16, 22 May 2012
Line 152:		Line 152:
	In milestone test, test team will perform a full validation testing for candidate build, following test will be involved. It includes more tests than Sanity and Weekly Test.		In milestone test, test team will perform a full validation testing for candidate build, following test will be involved. It includes more tests than Sanity and Weekly Test.

	* Functional Test – which will test the items in Feature List(defined in https://wiki.yoctoproject.org/wiki/Yocto_1.~~2_Schedule~~), cover Core OS & System usage, ~~hob2~~, ~~build appliance~~, and other build features, etc.		* Functional Test – which will test the items in Feature List(defined in https://wiki.yoctoproject.org/wiki/Yocto_1.3_Schedule), cover Core OS & System usage, WebHob, Hob2, and other build features, etc.
	* Stress Test – system should be alive and functional in 24 hours workload test.		* Stress Test – system should be alive and functional in 24 hours workload test.
	* Power and Performance Test – which follow the power and performance test plan		* Power and Performance Test – which follow the power and performance test plan