Test case approval - Revision history

Wikicatglobe at 10:37, 18 October 2013

2013-10-18T10:37:34Z

← Older revision		Revision as of 10:37, 18 October 2013
Line 1:		Line 1:
	<accesscontrol>~~Administrators~~</accesscontrol>		<accesscontrol>Main:MyGroup</accesscontrol>
	== How to get testcases approved ==		== How to get testcases approved ==

Cg_pham at 08:56, 4 October 2011

2011-10-04T08:56:35Z

← Older revision		Revision as of 08:56, 4 October 2011
Line 1:		Line 1:
			<accesscontrol>Administrators</accesscontrol>
	== How to get testcases approved ==		== How to get testcases approved ==

Catglobe: /* Specify which test can be automation-tested */

2010-05-14T02:11:22Z

Specify which test can be automation-tested

← Older revision		Revision as of 02:11, 14 May 2010
Line 23:		Line 23:
	**100% boundary values.		**100% boundary values.
	**xx% statement coverage.		**xx% statement coverage.
	*Together with QA, get it ~~aproved~~.		*Together with QA, get it approved.

	=== Input more information to the test to fulfill the testcase template. ===		=== Input more information to the test to fulfill the testcase template. ===

Catglobe: /* Create test cases in our System. */

2010-05-14T02:10:14Z

Create test cases in our System.

← Older revision		Revision as of 02:10, 14 May 2010
Line 41:		Line 41:
	*Specify required information.		*Specify required information.
	*For those test cases that are supposed to test automatically, specify the Unittest-related information.		*For those test cases that are supposed to test automatically, specify the Unittest-related information.
	*Send the test cases number to the Unittest ~~developement~~ team.		*Send the test cases number to the Unittest development team.
	*Together with QA, get its final approval.		*Together with QA, get its final approval.

	[[Category:Test case guidelines]]		[[Category:Test case guidelines]]

Catglobe at 09:24, 9 April 2010

2010-04-09T09:24:04Z

← Older revision		Revision as of 09:24, 9 April 2010
Line 30:		Line 30:
	#<u>'''Output:'''</u> a list of test cases in correct template and with detail information.		#<u>'''Output:'''</u> a list of test cases in correct template and with detail information.

	*Base on <u>''''~~How to write test case~~''''</u> section, write test cases for those scenarios in correct template and with detail information.		*Base on <u>''''[[General guidelines]]''''</u> section, write test cases for those scenarios in correct template and with detail information.
	*Together with QA, get it approved.		*Together with QA, get it approved.

Catglobe at 09:23, 9 April 2010

2010-04-09T09:23:21Z

← Older revision		Revision as of 09:23, 9 April 2010
Line 10:		Line 10:
	*In this phase, it's important that the FD as well as the related modules are understood clearly so that all the scenarios are listed. Every unclear scenarios should be discussed together with development team, including Tester, QA, BA and PM.		*In this phase, it's important that the FD as well as the related modules are understood clearly so that all the scenarios are listed. Every unclear scenarios should be discussed together with development team, including Tester, QA, BA and PM.
	*Spreadsheet should be used to specify the list.		*Spreadsheet should be used to specify the list.
	*Scenarios should be grouped and sorted (see <u>''''''What to test'''''')</u>		*Scenarios should be grouped and sorted (see <u>''''''[[What to test]]'''''')</u>
	*Scenarios' priority should be specified.		*Scenarios' priority should be specified.

Catglobe at 09:18, 9 April 2010

2010-04-09T09:18:13Z

← Older revision		Revision as of 09:18, 9 April 2010
Line 44:		Line 44:
	*Together with QA, get its final approval.		*Together with QA, get its final approval.

	[[Category:~~Test_case_guidelines~~]]		[[Category:Test case guidelines]]

Catglobe: Created page with '== How to get testcases approved == There are some steps that need to be followed to get your test cases approved: === Get a list of what to be tested === #'''Input:'''<…'

2010-04-09T09:06:23Z

Created page with '== How to get testcases approved == There are some steps that need to be followed to get your test cases approved: === Get a list of what to be tested === #'''Input:'''<…'

New page

== How to get testcases approved ==

There are some steps that need to be followed to get your test cases approved:

=== Get a list of what to be tested ===

#'''Input:'''Feature Design
#'''Output:''' a list of  testable scenarios in order.

*In this phase, it's important that the FD as well as the related modules are understood clearly so that all the scenarios are listed. Every unclear scenarios should be discussed together with development team, including Tester, QA, BA and PM.
*Spreadsheet should be used to specify the list.
*Scenarios should be grouped and sorted (see ''''''What to test'''''')
*Scenarios' priority should be specified.

=== Specify which test can be automation-tested ===

#'''Input:''' list of scenarios in order
#'''Output:''' 2 lists of scenarios: a list for manual test and a list for automation test

*In this phase, it is important that tester and dev work well together to specify which case can be implemented automation test and which one should be tested manually.
*Test data should be provided in details for those cases which will be added to automation test. They must at least fulfill these criteria:
**100% equivalence partitionning values.
**100% boundary values.
**xx% statement coverage.
*Together with QA, get it aproved.

=== Input more information to the test to fulfill the testcase template. ===

#'''Input:'''a list of testable scenarios which are approved.
#'''Output:''' a list of test cases in correct template and with detail information.

*Base on ''''How to write test case'''' section, write test cases for those scenarios in correct template and with detail information. 
*Together with QA, get it approved.

=== Create test cases in our System. ===

#'''Input:''' a list of test cases having detail information.
#'''Output:''' test cases are created in vnsurvey with all required information.

*In vnsurvey, create test cases in the same order with the list.
*Specify required information.
*For those test cases that are supposed to test automatically, specify the Unittest-related information.
*Send the test cases number to the Unittest developement team.
*Together with QA, get its final approval. 

[[Category:Test_case_guidelines]]