|
Below, you'll find extensive information
on leading email software articles and products to
help you on your way to success.
Practical Measurements For Software Testing
By RTG Marketing
Every development company focuses on developing quality software. The only way to track the quality is evaluating it at every stage of its development. It requires some kind of metrics, which is obtained through effective testing methods. Each stage of testing is effectively monitored for the QA.
1. measurements are used for:
2. Deriving basis for estimates
3. Tracking project progress
4. Determining (relative) complexity
5. Understanding the stage of desired quality
6. Analyzing defects
7. Validating best practices experimentally
Here, some testing metrics are proposed for black box testing that has real world applications. It discusses:
Importance of testing measurement
Different techniques/processes for measuring testing
Metrics for analyzing testing
Methods for measuring/computing the metrics
Advantages of implementing these metrics
These metrics helps in understanding the inadequacies in different QA stages and finding better correcting practices.
What is measurement and why it is required?
The process of assigning numbers or symbols to attributes of real world entities for describing them according to defined rules is called measurement.
For developing quality software, several characteristics like requirements, time and effort, infrastructural cost, requirement testability, system faults, and improvements for more productive resources should be measured.
Measuring testing is required:
1. If the available test cases cover all the system’s aspects
2. For tracking problems
3. For quantifying testing
Choose the suitable metrics:
Several metrics can measure software-testing process.
Here, the following types of metrics are identified:
Base metrics:
These raw data are collected in a testing effort and applied in formulae used to derive Calculated Metrics.
The Test Metrics comprise of the Number of
Test Cases Passed, Failed, Under Investigation, Blocked, Re-executed and Test Execution Time.
Calculated metrics:
They convert the Base Metrics data into useful information. Every test efforts must implement the following Calculated Metrics:
% Complete
% Defects Corrected
% Test Coverage
% Rework
% Test Cases Passed & Blocked
% Test Effectiveness & Efficiency
% 1st Run Failures
% Failures
Defect Discovery Rate
Defect Removal Cost
Measurements for Testing
The corresponding testing process in development measures each step for ensuring quality product delivery.
1. Size:
The amount of functionality of an application determines this and is calculated by
Function Point Analysis
Task Complexity Estimation Methodology
2. Requirements review:
Before development, the requirement specifications (SRS) from the client are obtained. It must be:
Complete
Consistent
Correct
Structured
Ranked
Testable
Traceable
Unambiguous
Validate
Verified
The Review Efficiency is a metric that offers insight on the review quality and testing.
Review efficiency=100*Total number of defects found by reviews/Total number of project defects
3. Effectiveness of testing requirements:
It is measured by maintaining Requirement Trace-ability matrix and specification of requirements, which should have:
SRS Objective, purpose
Interfaces
Functional Capabilities
Performance Levels
Data Structures/Elements Safety
Reliability
Security/Privacy
Quality
Constraints & limitations
Next comes the updating of the crucial requirement trace-ability matrix or RTM, which determines the number and types of tests.
While measuring the mapping
|
|
We strive to provide only quality articles, so
if there is a specific topic related to software
that you would like us to cover, please contact
us at any time.
And again, thank you to those contributing daily
to our email software website.
|