Mantis - Kaputt
|
|||||
Erweiterte Problemanzeige | |||||
|
|||||
ID: | Kategorie: | Auswirkung: | Reproduzierbar: | Meldungsdatum: | Letzte Aktualisierung: |
139 | general | kleinerer Fehler | immer | 2016-12-21 00:58 | 2016-12-21 00:58 |
|
|||||
Reporter: | Bergi | Rechnertyp: | |||
Bearbeitung durch: | Betriebssystem: | ||||
Priorität: | normal | BS-Version: | |||
Status: | neu | Produktversion: | |||
Produkt-Build: | Lösung: | offen | |||
Projektion: | keine | ||||
Aufwand: | keine | Behoben in Version: | |||
|
|||||
Zusammenfassung: | 0000139: Kaputt should check all specifications not only the first | ||||
Beschreibung: |
The docs say (and the code confirms) | When checking if the function matches its specification, | Kaputt will determine the first precondition from the list | that holds, and ensure that the corresponding postcondition | holds: if not, a counterexample has been found. This is not helpful in my standard usage. I've got multiple postconditions that I want to test, some of them with preconditions because they don't apply to every test case. I would rather have all the implications in the list checked on every test run. Or maybe I'm doing something wrong here, and I should rather use multiple tests for this? |
||||
Schritte zur Reproduktion: | |||||
Zusätzliche Information: | |||||
Problem-Beziehungen | |||||
Angehängte Dateien: | |||||
|
|||||
Problem-Historie | |||||
Änderungsdatum | Benutzername | Feld | Änderung | ||
2016-12-21 00:58 | Bergi | Neues Problem |
Zu diesem Problem gibt es keine Notizen. |