Tinfoil Test Plan - Revision history

Jose G Perez Carranza: /* Features to be tested */

2017-01-12T19:44:45Z

Features to be tested

2017-01-12T19:40:21Z

Scope

← Older revision		Revision as of 19:40, 12 January 2017
Line 18:		Line 18:
	Test Cases will be designed to verify the different functionality of the API, all test cases should be designed to be executed in automated way.		Test Cases will be designed to verify the different functionality of the API, all test cases should be designed to be executed in automated way.

	The first stage of test is a set of basic test listed on [[#Features to be tested d ]]		- The first stage of test is a set of basic test listed on [[#Features already tested \| Features already tested]]

			- The subsequent improvements to the Test Suite should be listed on [[#Features to be tested \| Features to be tested]]

	= Test Strategy =		= Test Strategy =

2017-01-12T19:38:08Z

Scope

← Older revision		Revision as of 19:38, 12 January 2017
Line 15:		Line 15:

	= Scope =		= Scope =

			Test Cases will be designed to verify the different functionality of the API, all test cases should be designed to be executed in automated way.

			The first stage of test is a set of basic test listed on [[#Features to be tested d ]]

	= Test Strategy =		= Test Strategy =

2017-01-12T19:36:54Z

Test Strategy

← Older revision		Revision as of 19:36, 12 January 2017
Line 18:		Line 18:
	= Test Strategy =		= Test Strategy =

	~~Test Cases will be designed to verify the different functionality of the API, all test cases should be designed to be executed in automated way.~~		<TBD>

	== Test Automation ==		== Test Automation ==

2017-01-12T19:36:02Z

Objectives

← Older revision		Revision as of 19:36, 12 January 2017
Line 7:		Line 7:
	= Objectives =		= Objectives =

	Verify the ~~sanity~~ of Tinfoil API		Verify the functionality of Tinfoil API

	= Contacts =		= Contacts =

2017-01-12T19:35:35Z

Test Strategy

← Older revision		Revision as of 19:35, 12 January 2017
Line 18:		Line 18:
	= Test Strategy =		= Test Strategy =

			Test Cases will be designed to verify the different functionality of the API, all test cases should be designed to be executed in automated way.

	== Test Automation ==		== Test Automation ==

2017-01-12T19:32:00Z

Objectives

← Older revision		Revision as of 19:32, 12 January 2017
Line 6:		Line 6:

	= Objectives =		= Objectives =

			Verify the sanity of Tinfoil API

	= Contacts =		= Contacts =

2017-01-12T18:27:30Z

Test Cases Maintenance

← Older revision		Revision as of 18:27, 12 January 2017
Line 31:		Line 31:
	poky/meta/lib/oeqa/selftest/tinfoil.py		poky/meta/lib/oeqa/selftest/tinfoil.py

	- To create a new test case a Testopia instance should be created on [[https://bugzilla.yoctoproject.org/tr_show_plan.cgi?plan_id=25 OE-CORE]] under "Test Cases" the number given by Testopia should be added prior to the test case name as below:		- To create a new test case a Testopia instance should be created on [https://bugzilla.yoctoproject.org/tr_show_plan.cgi?plan_id=25 OE-CORE] under "Test Cases" the number given by Testopia should be added prior to the test case name as below:

	@testcase(<TESTOPIA_ID>)		@testcase(<TESTOPIA_ID>)

2017-01-12T18:27:11Z

Test Approach

← Older revision		Revision as of 18:27, 12 January 2017
Line 23:		Line 23:
	== Test Approach ==		== Test Approach ==

	Design of test are intended to cover the functionality of ~~tinfoil~~ API, all the test will be executed every milestone on GDC AB and ~~frecuently~~ on [https://autobuilder.yoctoproject.org main AB]		Design of test are intended to cover the functionality of Tinfoil API, all the test will be executed every milestone on GDC AB and frequently on [https://autobuilder.yoctoproject.org main AB]

	== Test Cases Maintenance ==		== Test Cases Maintenance ==

2017-01-12T18:26:37Z

Test Cases Maintenance

← Older revision		Revision as of 18:26, 12 January 2017
Line 36:		Line 36:
	def TEST_CASE_NAME(self):		def TEST_CASE_NAME(self):

	- To send the patches of created or modified test cases rules defined [http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded ~~guide~~ here] should be followed.		- To send the patches of created or modified test cases rules defined [http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded here] should be followed.

	=Features=		=Features=