V. Check list
1. Checklists of code
-
I - CHECK JAVA CODE
|
#
|
|
Yes
|
No
|
NA
|
1
|
DID YOU VERIFY YOUR CODE WITH CHECK STYLE AND FINDBUG?
|
|
|
|
2
|
Does the code correctly implement the design?
|
|
|
|
3
|
Does the code implement meet customer's requirement?
|
|
|
|
4
|
Are it use descriptive variable and constant names used in accord with naming conventions?
|
|
|
|
5
|
Are there variables with confusingly similar names?
|
|
|
|
6
|
Is it defining variables properly with meaningful, consistent, and clear names?
|
|
|
|
7
|
Did you remove all System.out.println()?
|
|
|
|
8
|
Did you remove unnecessary log information?
|
|
|
|
9
|
Check variables before use. Make sure that variables are not null.
|
|
|
|
10
|
Make sure that you have write java doc for class, method and complex source.
|
|
|
| Case and Requirement Mapping Review Checklist
Question
|
Yes
|
No
|
PASS
|
Note
|
Priority
|
DOCUMENT CONTROL
|
|
|
|
|
|
Does test case apply correct template?
|
x
|
|
|
OK
|
High
|
Does the naming convention follow CM Plan?
|
x
|
|
|
OK
|
High
|
Verify whether document control procedures have been followed by checking for the following:
|
|
|
|
|
High
|
Is it describes clearly modification history in [Records] sheet?
|
x
|
|
|
OK
|
High
|
Does it mention the corresponding version of Requirement in [Requirement Mapping] sheet?
|
x
|
|
|
OK
|
High
|
Is the document checked Spelling and Grammar in MS Excel tool (F7)
|
x
|
|
|
OK
|
Low
|
REQUIREMENT MAPPING REVIEW CHECKLIST
|
|
|
|
|
|
Do the requirement items cover all sections of the relevant Functional Spec? (Use Cases, Views, Role & Permission, Look & Feel, Workflow, Interface to other system)
|
x
|
|
|
OK
|
High
|
Are there requirement items for app data migration?
|
|
x
|
|
OK
|
High
|
Are there requirement items for app performance?
|
x
|
|
|
OK
|
High
|
Are test case reference listed out?
|
|
x
|
|
OK
|
Medium
|
Are test case number filled?
|
x
|
|
|
OK
|
Medium
|
TEST CASE REVIEW CHECKLIST
|
|
|
|
|
|
Requirement coverage
|
|
|
|
|
|
Is there at least one-1st priority test case for each requirement item in the Requirement Mapping?
|
x
|
|
|
OK
|
High
|
Is there test case for the app's general look & feel?
|
x
|
|
|
OK
|
High
|
Is there test case for the app GUI navigation?
|
x
|
|
|
OK
|
High
|
Are the test cases for each use case following the rule below? If No, please explain the reason in Notes column
|
|
|
|
|
High
|
Field validation test cases for each field data type of the relevant form.
|
x
|
|
|
OK
|
High
|
You have enough functional test cases for each business rule of the use case.
|
x
|
|
|
OK
|
High
|
Is there one security test case for each role of the system and the test case consists of functions that the role can perform?
|
x
|
|
|
OK
|
High
|
Do all mandatory columns are filled data?
|
|
|
|
|
High
|
Requirement ID
|
x
|
|
|
OK
|
High
|
Test case ID
|
x
|
|
|
OK
|
High
|
Test case Title
|
x
|
|
|
OK
|
High
|
Test Procedure
|
x
|
|
|
OK
|
High
|
Expected Result
|
x
|
|
|
OK
|
High
|
Priority
|
x
|
|
|
OK
|
High
|
Type
|
x
|
|
|
OK
|
High
|
Does title of test cases briefly and easy understand?
|
x
|
|
|
OK
|
Medium
|
Are common test cases (if they are used) included in the [Comment Case] sheet?
|
|
|
x
|
OK
|
Low
|
Do the data migration test cases cover the followings:
|
|
|
|
|
High
|
Test case selection
|
|
|
|
|
|
Does the test case consider the cases, where a user has several roles?
|
x
|
|
|
|
High
|
Do function test cases consist of both successful and unsuccessful cases?
|
x
|
|
|
OK
|
High
|
Other
|
|
|
|
|
|
Are you prioritizing the test cases?
|
|
|
|
OK
|
Medium
|
TEST DATA REVIEW CHECKLIST
|
|
|
|
|
|
Is test data prepared and baseline? If no, please give your explain in Note column
|
x
|
|
|
OK
|
High
|
Are many users for each role prepared for testing?
|
x
|
|
|
OK
|
High
|
5.5. Other material (if any) (including appendix A)
APPENDIX A. TEST LOGS
A.n Log for test n
A.n.1 Test Results
A.n.2 Incident Report
Chia sẻ với bạn bè của bạn: |
