Triaged Tester

February 27, 2009

Metrics based approach for test estimation

Filed under: Estimation,Guidelines,Metrics,Test Management — Triaged Tester @ 1:15 pm
Tags: ,

A useful approach is to track past experience of an organization’s various projects and the associated test effort that worked well for projects. Once there is a set of data covering characteristics for a reasonable number of projects, then this ‘past experience’ information can be used for future test project planning. (Determining and collecting useful project metrics over time can be an extremely difficult task.) For each particular new project, the ‘expected’ required test time can be adjusted based on whatever metrics or other information is available, such as function point count, number of external system interfaces, unit testing done by developers, risk levels of the project, etc. In the end, this is essentially judgment based on documented experience’, and is not easy to do successfully

February 26, 2009

Implicit Risk Context Approach for Test Estimation

Filed under: Estimation,Stratergies,Test Management — Triaged Tester @ 1:14 pm
Tags: ,

A typical approach to test estimation is for a project manager or QA manager to implicitly use risk context, in combination with past personal experiences in the organization, to choose a level of resources to allocate to testing. In many organizations, the ‘risk context’ is assumed to be similar from one project to the next, so there is no explicit consideration of risk context. (Risk context might include factors such as the organization’s typical software quality levels, the software’s intended use, the experience level of developers and testers, etc.) This is essentially an intuitive guess based on experience.

February 25, 2009

Metrics for Evaluating system testing

Filed under: Metrics,Quality,Tips — Triaged Tester @ 1:13 pm
Tags:

Metric = Formula

Test Coverage = Number of units (KLOC/FP) tested / total size of the system. (LOC represents Lines of Code)

Number of tests per unit size = Number of test cases per KLOC/FP (LOC represents Lines of Code).

Acceptance criteria tested = Acceptance criteria tested / total acceptance criteria

Defects per size = Defects detected / system size

Test cost (in %) = Cost of testing / total cost *100

Cost to locate defect = Cost of testing / the number of defects located

Achieving Budget = Actual cost of testing / Budgeted cost of testing

Defects detected in testing = Defects detected in testing / total system defects

Defects detected in production = Defects detected in production/system size

Quality of Testing = No of defects found during Testing/(No of defects found during testing + No of acceptance defects found after delivery) *100

Effectiveness of testing to business = Loss due to problems / total resources processed by the system.

System complaints = Number of third party complaints / number of transactions processed

Scale of Ten = Assessment of testing by giving rating in scale of 1 to 10

Source Code Analysis = Number of source code statements changed / total number of tests.

Effort Productivity = Test Planning Productivity = No of Test cases designed / Actual Effort for Design and Documentation

Test Execution Productivity = No of Test cycles executed / Actual Effort for testing

February 24, 2009

Test Estimation – best approach?

Filed under: Estimation,Test Management — Triaged Tester @ 1:12 pm
Tags:

What’s the best approach to software test estimation?
There is no simple answer for this. The ‘best approach’ is highly dependent on the particular organization and project and the experience of the personnel involved.

For example, given two software projects of similar complexity and size, the appropriate test effort for one project might be very large if it was for life-critical medical equipment software, but might be much smaller for the other project if it was for a low-cost computer game. A test estimation approach that only considers size and complexity might be appropriate for one project but not for the other

February 23, 2009

Test Estimate – Quick ‘n’ Dirty

Filed under: Estimation,Guidelines,Test Management — Triaged Tester @ 1:11 pm
Tags: ,

Here is what you can follow to arrive at an high level of estimation for test projects. It’s the quick and dirty way , but you would be surprised that it gives almost the correct results 🙂

testestimate

Next Page »

Blog at WordPress.com.