SOFTWARE TESTING

AND QUALITY
ASSURANCE
MODULE 3
MODULE 3-Managing the Test Process
 Software Metrics:

Software metrics in software testing are quantitative measures used to assess various aspects of the
software development process and the quality of the software product. These metrics provide valuable
insights that help in improving the software's performance, quality, and maintainability. Here are some
commonly used software metrics in software testing:

1. Code Quality Metrics

● Cyclomatic Complexity: Measures the complexity of the code by counting the number of linearly independent
paths through the code. Lower values indicate simpler and more maintainable code.
● Code Coverage: Percentage of code executed by the test cases. Higher coverage means more code is tested,
reducing the risk of undetected bugs.
● Lines of Code (LOC): Measures the size of the software by counting the number of lines in the source code. This
can indicate the project's scale and help in resource estimation.
2. Test Metrics

● Defect Density: The number of defects found per unit size of the software (e.g., per
1000 lines of code). Lower defect density indicates higher software quality.
● Test Case Effectiveness: Ratio of the number of defects detected by a test case to
the total number of defects. Higher effectiveness means better testing.
● Test Execution Metrics: Measures like the number of test cases executed, pass/fail
ratio, and the time taken for testing provide insights into the testing process's
efficiency and effectiveness.
3. Process Metrics

● Defect Removal Efficiency (DRE): The ratio of defects removed during a specific
phase of development to the total defects found. Higher DRE indicates a more
effective defect removal process.
● Defect Leakage: Number of defects found after the software is released compared
to those found before release. Lower defect leakage indicates better testing and
defect management.
4. Performance Metrics

● Response Time: Time taken by the system to respond to a user request. Lower
response times indicate better performance.
● Throughput: Number of transactions processed by the system in a given period.
Higher throughput means better performance.
● Resource Utilization: Measures how efficiently the system uses resources like
CPU, memory, and network. Lower resource utilization for the same performance
indicates better efficiency.
5. Reliability Metrics

Mean Time to Failure (MTTF): Average time the system operates before failing. Higher MTTF
indicates better reliability.
Mean Time to Repair (MTTR): Average time taken to repair the system after a failure. Lower
MTTR indicates quicker recovery from failures.
Failure Rate: Number of failures over a specified period. Lower failure rates indicate higher
reliability.
6. Customer Satisfaction Metrics

● Customer Reported Defects: Number of defects reported by customers. Fewer customer-reported defects
indicate higher satisfaction.
● Net Promoter Score (NPS): Measures customer loyalty and satisfaction by asking customers how likely
they are to recommend the product to others.
● Customer Satisfaction Index (CSI): Aggregates customer feedback into a single score, reflecting overall
satisfaction.
Metrics

► Metrics is a measurement of the level that any impute belongs to a system product
or Process.
► There are four functions related to software Metrics
1)Planning
2) Organizing
3) Controlling
4) improving
These function plays crucial roles in the successful implementation and
utilization of software metrics in software testing and development processes. Here’s
a
 1. Planning

Planning involves defining the goals and objectives for using software metrics and
establishing a roadmap for how these metrics will be collected, analyzed, and utilized.
● Goal Setting: Determine what you want to achieve with software metrics (e.g.,
improving code quality, reducing defects, enhancing performance).
● Metric Selection: Choose appropriate metrics that align with your goals (e.g., defect
density, code coverage, response time).
● Data Collection Plan: Define how and when the data for these metrics will be collected
(e.g., during development, testing phases).
● Resource Allocation: Identify the resources (time, tools, personnel) needed to
implement and maintain the metrics program.
● Risk Assessment: Identify potential risks in the metrics program and plan for mitigation
strategies.
2. Organizing

Organizing involves structuring the team and processes to effectively collect, manage, and analyze the metrics
data.

● Role Assignment: Assign roles and responsibilities to team members for collecting, analyzing, and
reporting metrics.
● Tool Selection: Choose and implement tools for data collection, analysis, and visualization (e.g., test
management tools, code analysis tools).
● Process Integration: Integrate metrics collection and analysis into the existing development and testing
workflows.
● Training: Provide training for team members on how to use the tools and interpret the metrics data.
● Documentation: Create documentation for the metrics program, including definitions, processes, and
usage guidelines.
3. Controlling

Controlling involves monitoring the metrics program to ensure it is functioning as planned and making
adjustments as necessary to stay on track.

● Data Monitoring: Regularly monitor the collection and accuracy of metrics data.
● Performance Evaluation: Evaluate the performance of the development and testing processes based on
the collected metrics.
● Benchmarking: Compare the collected metrics against industry standards or historical data to identify
areas of improvement.
● Reporting: Generate regular reports on the metrics data and share them with stakeholders to keep them
informed about progress and issues.
● Feedback Loop: Establish a feedback loop to ensure that insights from metrics analysis are used to make
informed decisions and improvements.
4. Improving

Improving involves using the insights gained from metrics analysis to make continuous improvements in
the development and testing processes.

● Identify Weaknesses: Use metrics to identify areas of weakness or bottlenecks in the development
process (e.g., high defect density, low code coverage).
● Implement Changes: Make changes to processes, tools, or team practices based on the insights
gained (e.g., refactor complex code, enhance test coverage).
● Measure Impact: After implementing changes, measure the impact using the same metrics to
ensure that the changes are having the desired effect.
● Continuous Improvement: Establish a culture of continuous improvement where metrics are
regularly reviewed, and processes are continually refined.
● Best Practices: Document and share best practices and lessons learned from the metrics program to
promote knowledge sharing and improvement across the organization.
Testing Metrics for Monitoring and
Controlling

► Test Monitoring is the process of assessing and providing feedback on ongoing testing

activities. It uses certain techniques to make sure that specific goals are achieved during each

testing phase as planned.

► Monitoring involves comparing the current state of testing tasks with a pre-defined plan and

analyzing if the process is delivering the expected outcomes.

► Just as it’s important to monitor testing processes, the concept of website monitoring also

becomes central, ensuring websites perform optimally and align with user expectations.
► Test monitoring helps stakeholders stay informed about the testing efforts and the quality of the

software being developed.

► It provides visibility into whether the testing is on track, whether the quality goals are being met, and

whether any corrective actions are required to ensure successful project outcomes.
► 0It is an integral part of the software testing lifecycle and quality assurance processes.