1 Case points-TCP 1 What is a Test Case Point (TCP) TCP is a measure of estimating the complexity of an application. This is also used as an estimation technique to calculate the size and effort of a testing project. The TCP counts are nothing but ranking the requirements and the test cases that are to be written for those requirements into simple, average and complex and quantifying the same into a measure of complexity. In this courseware we shall give an overview about Test Case Points and not elaborate on using TCP as an estimation technique. 2 Calculating the Test Case Points: Based on the Functional Requirement Document (FRD), the application is classified into various modules like say for a web application, we can have ‘Login and Authentication’ as a module and rank that particular module as Simple, Average and Complex based on the number and complexity of the requirements for that module. A Simple requirement is one, which can be given a value in the scale of 1 to3. An Average requirement is ranked between 4 and 7. A Complex requirement is ranked between 8 and 10. Complexity of Requirements Requirement Classification Simple (1-3) Average (4-7) Complex (> 8) Total The test cases for a particular requirement are classified into Simple, Average and Complex based on the following four factors. • Test case complexity for that requirement OR • Interface with other Test cases OR • No. of verification points OR • Baseline Test data • Refer the test case classification table given below 1 Test Case Classification Complexity Type Complexity of Test Case Interface with other Test case Number of verification points Baseline Test Data Simple < 2 transactions 0 < 2 Not Required Average 3-6 transactions <3 3-8 Required Complex > 6 transactions >3 >8 Required A sample guideline for classification of test cases is given below. • Any verification point containing a calculation is considered 'Complex' • Any verification point, which interfaces with or interacts with another application is classified as 'Complex' • Any verification point consisting of report verification is considered as 'Complex' • A verification point comprising Search functionality may be classified as 'Complex' or 'Average' depending on the complexity Depending on the respective project, the complexity needs to be identified in a similar manner. Based on the test case type an adjustment factor is assigned for simple, average and complex test cases. This adjustment factor has been calculated after a thorough study and analysis done on many testing projects. The Adjustment Factor in the table mentioned below is pre-determined and must not be changed for every project. From the break up of Complexity of Requirements done in the first step, we can get the number of simple, average and complex test case types. By multiplying the number of requirements with it s corresponding adjustment factor, we get the simple, average and complex test case points. Summing up the three results, we arrive at the count of Total Test Case Points. 3 Chapter Summary This chapter covered the basics on  What is Test Coverage  Test Coverage measures  How does Test coverage tools work  List of Test Coverage tools  What is TCP and how to calculate the Test Case Points for an application Test Case Type Complexity Weight Adjustment Factor Number Result Simple 1 2(A) No of Simple requirements in the project Number*Adjust factor A (R1) Average 2 4(B) No of Average requirements in the project Number*Adjust factor B (R2) Complex 3 8(C) No of Complex requirements in the project Number*Adjust factor C (R3) Total Test Case Points R1+R2+R3 . give an overview about Test Case Points and not elaborate on using TCP as an estimation technique. 2 Calculating the Test Case Points: Based on the Functional. with other Test cases OR • No. of verification points OR • Baseline Test data • Refer the test case classification table given below 1 Test Case Classification