Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

This lesson is about how to measure testing. You will find why just counting tests will not help us and what should we take into account when we need to say how much we tested and how much testing is left.

In this video you will learn about:

The importance of measurement theory concepts. The speaker emphasizes that counting elements, such as branches covered or bugs found, isn't sufficient for assessing the quality of testing. To convert numbers into meaningful answers, a model is needed. The discussion delves into measurement challenges like error, precision, purpose clarification, and the scale of measurement. An example involving the width of a projector screen illustrates these concepts. The lecture stresses the importance of understanding the attribute being measured to evaluate the validity of measurements, highlighting the need for a more sophisticated approach to measurement in software engineering.

Discussed terminology:

  • Why counting tests will not help us in measurement?

  • Measured Attribute - what we are trying to measure and WHY?

  • Scale of measurement

  • What measurement should contain

  • Measurement validity

  • No labels