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
{{ message }}
Repository navigation
Commit 15e547b
Browse filesBrowse the repository at this point in the historyBrowse files
This release continues the terminology change in :ref:`version 6.159.0 <v6.159.0>`, updating more internal wording and names from "example" to "test case".
Copy file name to clipboardExpand all lines: hypothesis/docs/reference/schema_observations.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -20,15 +20,15 @@
20
20
},
21
21
"representation": {
22
22
"type": "string",
23
-
"description": "The string representation of the input. In Hypothesis, this includes the property name and arguments (like ``test_a(a=1)``), any interactive draws from |st.data|, and additionally some comments from |Phase.explain| for failing examples."
23
+
"description": "The string representation of the input. In Hypothesis, this includes the property name and arguments (like ``test_a(a=1)``), any interactive draws from |st.data|, and additionally some comments from |Phase.explain| for failing test cases."
24
24
},
25
25
"arguments": {
26
26
"type": "object",
27
27
"description": "A structured json-encoded representation of the input. Hypothesis provides a dictionary of argument names to json-ified values, including interactive draws from the |st.data| strategy. If 'status' is 'gave_up', this may be absent or incomplete. In other libraries this can be any object."
28
28
},
29
29
"how_generated": {
30
30
"type": ["string", "null"],
31
-
"description": "How the input was generated, if known. In Hypothesis this might be an explicit example, generated during a particular phase with some backend, or by replaying the minimal failing example."
31
+
"description": "How the input was generated, if known. In Hypothesis this might be an explicit example, generated during a particular phase with some backend, or by replaying the minimal failing test case."
Copy file name to clipboardExpand all lines: hypothesis/docs/tutorial/replaying-failures.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,8 +76,8 @@ Prefer |@example| over the database for correctness
76
76
77
77
While the database is useful for quick local iteration, Hypothesis may invalidate it when upgrading (because e.g. the internal format may have changed). Changes to the source code of a test function may also change its database key, invalidating its stored entries. We therefore recommend against relying on the database for the correctness of your tests. If you want to ensure an input is run every time, use |@example|.
78
78
79
-
Replaying examples with |@reproduce_failure|
80
-
--------------------------------------------
79
+
Replaying test cases with |@reproduce_failure|
80
+
----------------------------------------------
81
81
82
82
If |settings.print_blob| is set to ``True`` (the default in the ``ci`` settings profile), and a test fails, Hypothesis will print an |@reproduce_failure| decorator containing an opaque blob as part of the error message:
0 commit comments