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
While we work on getting the HypoFuzz paperwork together, we'd love to hand out exploratory licenses to interested companies, <strong>at no cost</strong>. Get in touch!
102
+
<divclass="pricing-important-notice">
103
+
<divstyle="padding-bottom: 1rem;">
104
+
While we work on getting the HypoFuzz paperwork together, we'd love to hand out exploratory licenses to interested companies, <strong>at no cost</strong>. Get in touch!
105
+
</div>
106
+
<ahref="mailto:sales@hypofuzz.com?subject=Exploratory%20HypoFuzz%20licence" class="button button--cta pricing-card__button">Get in touch</a>
104
107
</div>
105
-
<ahref="mailto:sales@hypofuzz.com?subject=Per-seat%20HypoFuzz%20licence" class="button button--cta pricing-card__button">Get in touch</a>
Copy file name to clipboardExpand all lines: src/hypofuzz/docs/quickstart.rst
+5-7Lines changed: 5 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,16 +22,14 @@ Running HypoFuzz
22
22
23
23
The main entrypoint to HypoFuzz is ``hypothesis fuzz``. Installing HypoFuzz automatically adds this ``fuzz`` sub-command to the existing :ref:`Hypothesis CLI <hypothesis:hypothesis-cli>`.
24
24
25
-
The no-argument command ``hypothesis fuzz`` does two things:
25
+
Running ``hypothesis fuzz`` does two things:
26
26
27
-
* Starts a local dashboard webserver, and
28
-
* Executes your Hypothesis tests using all available cores
27
+
* Starts a local dashboard webserver.
28
+
* Discovers and executes your Hypothesis tests with all available cores.
29
29
30
-
These behaviors can be isolated with the ``--dashboard-only`` and ``--no-dashboard`` commands respectively. The number of cores used can be controlled with ``-n/--num-processes``.
30
+
These behaviors can be isolated with the ``--dashboard-only`` and ``--no-dashboard`` commands, respectively. The number of cores used can be controlled with ``-n/--num-processes``.
31
31
32
-
HypoFuzz uses :pypi:`pytest` to collect available tests. ``hypothesis fuzz`` should therefore be run in a directory where pytest can discover your tests.
33
-
34
-
Any arguments after ``hypothesis fuzz --`` are passed through to pytest. See :doc:`/manual/collection` for how to use this to control which tests are collected.
32
+
HypoFuzz uses :pypi:`pytest` to collect Hypothesis tests. ``hypothesis fuzz`` should therefore be run in a directory where pytest can discover your tests. To control how HypoFuzz collects tests, see :doc:`/manual/collection`.
0 commit comments