You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/developer-guide/testing.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,6 +69,19 @@ Other useful constructs are the following:
69
69
|`__goblint_check(1); // reachable`| Checks that the line is reachable according <br> to Goblint results (soundness). |
70
70
|`__goblint_check(0); // NOWARN (unreachable)`| Checks that the line is unreachable (precision). |
71
71
72
+
#### Meta
73
+
Comments at the end of lines can also indicate metaproperties:
74
+
75
+
| Annotation | Expected result/comment |
76
+
| ---------- | ----- |
77
+
|`NOCRASH`| No analyzer crash |
78
+
|`FIXPOINT`| No fixpoint error |
79
+
|`NOTIMEOUT`| Analyer terminates |
80
+
|`CRAM`| Automatic checks are only in corresponding Cram test |
81
+
82
+
These comments only document the intention of the test (if there are no other checks in the test).
83
+
Analyzer crash, fixpoint error and non-termination are checked even when there are other checks.
84
+
72
85
## Cram Tests
73
86
[Cram-style tests](https://dune.readthedocs.io/en/stable/tests.html#cram-tests) are also used to verify that existing functionality hasn't been broken.
74
87
They check the complete standard output of running the Goblint binary with specified command-line arguments.
0 commit comments