Abstract:

Test metrics are important indicator of efficiency & effectiveness of Software testing process. There are several test metrics identified as part of the overall testing activity in order to track and measure the entire testing process. These test metrics are collected at each phase of the testing life cycle. Their analysis is done and appropriate process improvements are determined. Measurements, data collection, analysis & improvement measures are parallel activities to testing life cycle activities.

When a testing team determines exactly what can be learned from each test and manages it according to the user experience, testing time can be spent wisely. Working on metrics development early in the process is a key, as it will impact the types of metrics needed to examine and ensure performance. Also, this provides the testing team with the time needed to draw up an efficient test plan, gather resources needed, and schedule the testing. Involvement of all stakeholders like developers, client representatives will give sharpness to outputs of metrics.

How to measure a test process is a required competence for an effective software test manager. Effective test process measurement is useful for designing and evaluating a cost-effective test strategy. Although existing research has addressed many metrics for those purposes, most metrics are used independently.

This paper summarizes a test process measurement and how it can be made more effective in Iterative model of development. Using analysis and measurement as drivers of the enhancement process is one major advantage of iterative software development. It provides support for determining the effectiveness of the processes and the quality of product. It allows one to study, and therefore improve and tailor, the processes for the particular environment. How to apply analysis done in previous iterations for improvement of testing process in next iteration? This is core area of discussion in this paper. Further discussions about implementation problems, how to apply test wisdom learned in previous iteration for metrics improvement, and cost saving due to measurement activities and metrics are presented.

A section of this paper will discuss improving metrics to provide more immediate, real-time feedback to testers on the quality of testing during each test phase, instead of waiting until the release. In order to accomplish this, team will have to focus on defining and developing 쐇ncremental quality, productivity, cost, and effectiveness metrics for the development and test process. 

Share
Related Documents
  1. [Ebook] Agile and Iterative Development - A Manager's Guide (5741)
  2. RAD (Rapid Application Development) Testing Model (2294)
  3. Testing in iterative development Cycle (1094)
  4. Best Practices for Software Projects - Iterative Development (1582)
  5. A Software Quality Model & Metrics For Risk Assessment (1306)
  6. Heuristic Test Stretegy Model (918)
  7. Testing life cycle (9 steps) (4811)
  8. Software Testing Maturity Model (1251)
  9. [Webinar] Lowering Product Delivery Risks through Lifecycle Quality Management (753)
  10. Scrum model (1353)
  11. Test Plan Evaluation Model (1196)
  12. Software Testing Maturity ModelSM(SW-TMMSM) - Slide (1641)
  13. IDEAL - Software Quality Improvement Model for Quality Certified Organizations (1766)
  14. Developing a Testing Maturity Model (1118)
  15. A Performance Process Maturity Model (1187)
  16. About V & V Model (22824)
  17. Systematic Model-Based Testing of Embedded Automotive Software (1857)
  18. Model verification and validation (V&V) (1039)
  19. [Ebook] Metrics and Models in Software Quality Engineering, Second Edition (6556)
  20. Relational Unified Process Model (1190)