Assertion Settings

Revision as of 15:56, 16 October 2006 by Konradm (Talk | contribs) (Critics)

Author: Matthias Konrad

Introduction

The Eiffel Language specifies several assertion types:

  • Preconditions
  • Postconditions
  • Invariants
  • Loop variants
  • Checks

In theory these assertions should be checked all the time. In practice, especially when working with huge systems, this is not possible. In some cases it is not even possible during the testing phase of the system. It is thus nessecary to decide which assertions should be tested. This decicion can be done by either the user or the compiler.

It is not enough to just enable or disable a certain assertion kind for the whole system. Large systems are composed of smaller parts and reused components (like the base library). These are typically tested independently (unit level testing). It should thus be possible to disable assertion testing on the tested part and enable it on the other parts.

In EiffelStudio the user has to decide which assertions need to be checked. He can do this on various levels (for each assertion kind):

  • Class
  • Cluster
  • Library
  • System

Critics

When the user specifies the assertions for a class he expresses a certain level of trust or mistrust towards it. When he enables invariant checking for a class he is not shure wether the specified invariants really hold, so they need to be checked. The same thing is true for loop variants, postconditions and checks. When he enables precondition checking for a class there is an ambiguity:

  1. He might say, that he doesn't trust the callers of the class, so the preconditions of this class need to be checked.
  2. Or he might not trust the class to hold the preconditions required by features it calls, so all the preconditions of the features called by this class need to be checked.

The current version of EiffelStudio uses the first approach. I think the latter complies better with the idea of trusting or mistrusting a class.