Difference between revisions of "Test case approval"
m |
Wikicatglobe (talk | contribs) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | <accesscontrol>Main:MyGroup</accesscontrol> | ||
== How to get testcases approved == | == How to get testcases approved == | ||
| Line 23: | Line 24: | ||
**100% boundary values. | **100% boundary values. | ||
**xx% statement coverage. | **xx% statement coverage. | ||
| − | *Together with QA, get it | + | *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. === | ||
| Line 30: | Line 31: | ||
#<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>'''' | + | *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. | ||
| Line 41: | Line 42: | ||
*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 | + | *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]] | ||
Latest revision as of 11:37, 18 October 2013
<accesscontrol>Main:MyGroup</accesscontrol>
Contents
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 approved.
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 'General guidelines' 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 development team.
- Together with QA, get its final approval.
