
How do you measure out of the ordinary packages?
Independent testing groups are often asked how long and how much effort is required to test a piece of work. Several size estimation techniques are actively in use in many organizations. Each of these techniques begins by deriving size either based on a set of rules or through relative sizing. Size, once derived, is used to estimate effort. Effort is then used to generate cost, staffing and duration estimates. The first sizing technique is“Test Case Points”
Test Case Points are a unit of measurement generated from the the testable requirements based on a set of rules. The process is straightforward:
- Identify the testable requirements in a piece of work. Use Cases or technical requirements documents are used for identifying testable requirements.
- Identify the complexity of each testable requirement. Test case points evaluate four factors to determine complexity:
- The number of test steps. The number of execution steps needed to arrive at an expected (or unexpected) outcome after all preconditions have been satisfied.
- The number of interfaces to the other requirements. A simple count of the number of interfaces in the test case.
- The number of verification points. A simple count of the points in the test case that the results are evaluated for correctness.
- Need for baseline test data. An evaluation of whether data needs to be created to execute the test case.
Once all of the simple, medium and complex test cases are identified, they are summed by category.
- Weight each category.
- Sum the weighted categories together to yield the total test case points
The goal of test case points is to use size to generate an estimate. Every version of test case points I have worked with uses a set of factors to adjust the size as part of the sizing process.
- Develop an estimation adjustment weighting based on a set of factors (for those familiar with IFPUG Function Points this adjustment is a similar process to the one for determining the value adjustment factor). The factors are:
- Count or Single Factor Adjustment Factors
Factor 14 – Operating System Combinations (simple count)
Factor 15 – Browser Combinations (simple count)
Factor 16 – Productivity Improvement from Second Iteration Onwards (percentage) - Factors that leverage a combination of fixed factor and complexity weighting
Factor 1 – Domain Knowledge & Complexity
Factor 2 – Technical Know How
Factor 3 – Integration with other Hardware Devices such as Handheld Devices, Scanners, Printers
Factor 4 – Multi-lingual Support
Factor 5 – Software/Hardware Setup
Factor 6 – Environment Setup
Factor 7 – Build Management
Factor 8 – Configuration Management
Factor 9 – Preparation of Test Bed
Factor 10 – Stable Requirements
Factor 11 – Offshore/Onsite Coordination
Factor 12 – Test Data Preparation
Factor 13 – Network Latency
- Generate an estimate using the following formula
Weighted Test Case Points X Adjustment Factor X Historical Productivity Rate
In many cases, organizations generate estimates for types of work separately using the adjustment factors that that would affect the type of work. An example of a type of work is test case generation. Factor 5, software/hardware setup, would not be predictive of the effort for setting up test cases.
The process for deriving test case points is fairly straightforward (steps 1 – 4). The process of turning the test case points into an estimate is more complicated. Next, we will develop a short example and examine the strengths and weaknesses of the process – some which are very apparent and other are not.
April 6, 2017 at 11:56 pm
[…] Berriault provided an example from this presentation at QAI Quest 2017 for us to count test case points. Jeremy, QA Corner, indicated baseline data was required to effectively run the three […]
September 25, 2017 at 10:53 am
Good article!
One more awesome article about Estimating Effort of Test Automation Projects:
https://www.katalon.com/resources-center/blog/estimating-effort-test-automation/
Thank you.
September 27, 2017 at 4:19 am
Thanks for the article, it’s really helpful!
And agree with David about the “Estimating Effort of Test Automation Projects”. However, for the deeper approach, you guys should also read the references mentioned below that article.
February 26, 2021 at 12:29 pm
q1: I have a test case below, how do we calculate verification point for this? is it unique validation or all the validations?
q2: If the verification point is considered in 1st test case, are we not supposed to consider those verification points in the next subsequent test cases?
test steps:
1. Launch the Browser.
2. Enter the URL.
3. Enter User ID and Password of HR and Click on Log In.
4. Click on Close Button.
5. Click on ‘Initiate behalf of Employee’ from the card that says’ HR.
6. Click on ‘Select’ Dropdown of Select Claim Type and Select ‘Client Bonus/Reward/Incentive allowance’ Claim.
7. Copy the Data From the Excel file and Paste it in the Place saying ‘Paste your content here’.
8. Upload your .jpg file
9. Click on UPLOAD Button.
10. Click on ‘YES’.
11. Click on Menu Bar and Click on Initiate Claims.
12. Click on Checkbox for the Uploaded Claim and Click on Submit button.
13. Enter Remarks and Click on SUBMIT button.
14. Click on ‘YES’ Button.
15. Click on Dropdown near the name of the User ID and Click on Logout.
Expected result:
1. Browser should be launched.
2. URL Should be Entered
3. HR Partner Manual Page Pop up should be Displayed.
4.User Should be logged in successfully
5. LOB HR Initiate claim page should be displayed
6. Client Bonus/Reward/Incentive allowance Claim should be selected and by default Copy & Paste Option page should display.
7. Data should be Displayed in the Template format used.
8. File should be uploaded to the Page.
9. ‘Are you sure you want too proceed’ Message should be displayed.
10. ‘Data has been Saved successfully’ Message should be Displayed.
11. List of all the Claims that needs approval should be displayed.
12. Submit Pop up Should be Displayed
13 Message saying ‘Are you sure you want to proceed’ Should be displayed.
14. The Claim should be approved and the Claim should be removed from the Initiate Claim Page and Moved to Next Level of approval.
15. User should be successfully Logged out of the application.
May 9, 2022 at 3:25 pm
[…] Size As A Factor In Test Estimation: Test Case Points Overview […]