Testing Checklist v 1.0

7/29/2019 Testing Checklist v 1.0

1/9

Project Name:

Project Manager:

Ver. No. Ver. Date Description

Ver. No. Ver. Date Description Prepared By

R

A

1.014-Dec-09

Anantara

Prepared B

Document Version History

Template Version History

Testing Checklists

Project ID:

Document Information


2/9

Description Status

1 Is the scope of the Unit Testing specified?

2 Is a mechanism identified to map requirements and specifications to unit test cases?

3 Are standards listed for unit testing activity?

4 Are Tools required to support Unit testing activities planned?

5Does the test plan completely test the functionality of the unit as defined in the design

specification and in the system requirements specification?

6Are all variables (including global variables) input to the unit included in the features to be

tested in the test plan?

7 Do all variables output from the unit result from the features to be tested?

8 Is every procedure in the design exercised by the test?

9Are tests included for critical procedures to demonstrate that performance meets stated

requirements?

10For units that interface with other units, are invalid features tested to test for defensive

coding?

11Are the test features combined into test cases wherever practical to reduce the number of

test cases required?12 Is error handling logic tested?

13 Does each test case have a corresponding expected result?

14 Are generic test cases used wherever possible to reduce the number of test cases?

#

Unit Test Plan & Test Case Re


3/9

Remarks

view Checklist


4/9


5/9

#

Check Point Status

Yes / No / NA1 Are Integration Test Plan and Test Case under configuration control?

2If test is not performed as per plan, are the variations from the approved plan documented?

(change in integration sequence, test data, test environment, etc.)

3 Have all the test cases been executed?

4Has the Test Log been updated to reflect the test case status? (with appropriate comments

provided where need be.)

5Are testing limitations and issues documented and shared with the customers and impacted

team(s)?

6 Are the new test cases developed / modified documented for the functional changes?

7 Are the new test cases mapped in Requirements Traceability Matrix (RTM) document?

8 Is the defect report updated and baselined?

9 Is the defect report shared with the concerned members / team?

10 Are the defects regressed and closed?

11 Has the defect data analysis been conducted?

Checklist for Integration Testing


6/9

# Check Point Status

(Yes / No / NA)

1 Are the functional requirements available for generating test cases?

2 Are the design specifications / use cases available for generating test cases?

3Have the testers understood the Business requirements to test the application

effectively?

4Have the test cases been reviewed against Traceability matrix to check the test

coverage?

5 Have you got sample data from the Customer to create test data?

6 Is the test environment set as per the test plan?

7 Are the test cases taking care of database manipulations?

8 Are the test case records base-lined as per configuration management?

9 Are the test cases updated based on the change requests?

10 Is the defect tracking system in place for an effective Regression testing?

11 Are the test cases / scenarios identified for test automation?

12 Are the test records base lined as per configuration management?

13Are the test scenarios identified and approved by the Business analysts and

Customer?

14 Is the test data created for checking the module-to-module integration?

15 Is the test data created for checking the end-to-end business flow?

16 Are test scenarios taking care of uncertain and invalid conditions?

17 Are there test cases generated for checking concurrent user access?

18Are there test cases generated to check user privileges with respect to the

application?

19 Is there a test procedure available to verify Backup & Restoration procedures?

20Is there a test procedure available to verify Installation procedures independently by a

tester?

21 Apart from the test cases/ scenarios, has someone tested the application withoutfollowing any procedures to check the behavior of the application?

22 Is the system tested the application by simulating Network failure?

23 Is the application checked for its compliance with the targeted Operating Systems?

24 Have all the test results documented and defects tracked to closure?

25Are Constraints and issues faced during testing, documented and shared with the

stakeholders?

Checklist for System Testing

System Test Readiness


7/9

#

Check Point Status

(Yes / No / NA)

1 Are the objectives and scope of the Acceptance Testing specified?

2 Are all defects in earlier phase fixed and re-tested?

3 Is the Integrated System built with the latest, tested units?

4 Is the required input / test data for testing available?5 Is test environment set-up in-line with the Contract / as agreed with the Customer?

6 Are test cases identified to test all aspects of the Acceptance Criteria?

7 Are negative test cases identif ied?

8 Is System 'Installation Check' performed?

9 Is the System tested for 'Exceptional scenario and rare conditions?

10Have you defined acceptance criteria (e.g. performance, portability, throughput, etc.) on

which the completion of the acceptance test will be judged?

11Has the method of handling problems / defects detected during acceptance testing and their

disposition been agreed between you and the customer?

12 Are acceptance test cases for new / changed requirements developed?

13 Is the RTM updated to reflect the latest acceptance test cases?

14 Have all the test results documented and defects tracked to closure?

15 Have all steps of the test run been documented?(optional)16 Is the customer accepted version of the Solution archived/ baselined for future reference?

17Are Constraints and issues faced during testing, documented and shared with the

stakeholders?

18 Has the customer sign-off been obtained?

19 Has the customer feedback been administered?

Acceptance Testing Checklist

Test Preparation

Test Execution and Evaluation


8/9

Preliminary Design Review

1. Traceability

Did you ensure traceability of the design back to the systems specification and statement of requireme

Is a scheme used for naming of modules, data, and interfaces?

Are all modules, data, and interfaces uniquely identified?

2. Consistency

Is the data structure consistent with the information domain?

Is the data structure consistent with software requirements?

Is a standard design representation used?

Is a standard data usage representation used?

3. Completeness

Are software requirements reflected in the software architecture?

Are all referenced data defined?

Are all defined data used?

Are all referenced modules defined?

Are all defined modules used?

Are interfaces defined for modules and external elements?

Has maintainability been considered?

Have quality factors been explicitly assessed?

4. Efficiency

Are data grouped for efficient processing?

Are storage requirements allocated to design?

Is effective modularity achieved? Are modules functionally independent?

Design Walkthrough

1. Does the algorithm accomplish the desired function?

2. Is the algorithm logically correct?

3. Is the interface consistent with the architectural design?

4. Is the logical complexity reasonable?

5. Has error handling been specified?

6. Are local data structures properly defined?

7. Are structured programming constructs used throughout?

8. Is design detail amenable to implementation language?9. Has maintainability been considered?

10. Are all conditions and processing defined for each decision point?

11. Do all defined and referenced calling sequence parameters agree?


9/9

nts?

Testing Checklist v 1.0

Documents

Transcript of Testing Checklist v 1.0