anonym | Anmelden | Neues Konto anmelden | 2022-05-17 19:47 UTC |
Startseite | Übersicht | Probleme anzeigen | Änderungsprotokoll | Roadmap | Dokumentation | Konto |
Einfache Problemansicht anzeigen [ Zu Notizen wechseln ] | [ erweiterte Anzeige ] [ Problem-Historie ] [ Drucken ] | |||||||||||
ID | Kategorie | Auswirkung | Reproduzierbar | Meldungsdatum | Letzte Aktualisierung | |||||||
0000139 | [Kaputt] general | kleinerer Fehler | immer | 2016-12-21 00:58 | 2016-12-21 00:58 | |||||||
Reporter | Bergi | Anzeigestatus | öffentlich | |||||||||
Bearbeitung durch | ||||||||||||
Priorität | normal | Lösung | offen | |||||||||
Status | neu | Produktversion | ||||||||||
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? |
|||||||||||
Zusätzliche Information | ||||||||||||
Tags | Keine Tags zugeordnet. | |||||||||||
Angehängte Dateien | ||||||||||||
|
Zu diesem Problem gibt es keine Notizen. |
Mantis 1.1.7[^] Copyright © 2000 - 2008 Mantis Group |