You are here

Consistent and Repeatable Metrics to Manage Test Activities

Implementing more and more new functionalities within an always getting shorter time frame is one of the biggest challenges for software developer today. The most development teams have backlogs of new features that are waiting for release. The problem is the often the full system test. Especially embedded hardware is slow and has very limited resources. Therefore, a full system test sometimes takes days or weeks. Unfortunately, the functional safety requires a proof of test on the real hardware. Long test times lead to delays between implementation and test activities. Defects were found very late in the release cycle which leads to stress for the development team, delays and unhappy customers because of buggy software.

In this speech I will discuss different metrics for managing testing activities which allow teams and team members to collaborate their testing activities and provide up to date metrics on the current release readiness.

Important metrics are code complexity, frequency of code changes, test case status and code coverage data. The right analysis of the collected data and a graphical report allows you to find bottlenecks earlier in the development process. The right information allows team leader to put one’s resources into the right places and get realistic assessments. 

The speech shows how does it work and gives key insights to software quality and how to use test collaboration, code coverage, change-based tests, change impact analysis, test case maintenance and continuous testing as solutions to solve the problems you probably recognize within the reports. The speech includes a live demo.


Key takeaways:

  • Key insight in different test methodologies.
  • How to check where I am in my testing activities, where I should look first, which part is most important etc.
  • How to get a useful report regarding the test activities.