| /dports/databases/py-motor/motor-1.0/doc/examples/ |
| H A D | bulk.rst | 29 .. doctest::
58 .. doctest::
86 The first write failure that occurs (e.g. duplicate key error) aborts the
89 results up until the failure occurred and details about the failure - including
90 the operation that caused the failure.
92 .. doctest::
131 In the next example the first and third operations fail due to the unique
135 .. doctest::
177 .. doctest::
|
| /dports/databases/pymongo/pymongo-3.12.0/doc/examples/ |
| H A D | bulk.rst | 26 .. doctest::
54 .. doctest::
82 The first write failure that occurs (e.g. duplicate key error) aborts the
85 the exception instance provides the execution results up until the failure
86 occurred and details about the failure - including the operation that caused
87 the failure.
89 .. doctest::
124 In the next example the first and third operations fail due to the unique
128 .. doctest::
|
| /dports/devel/py-taskflow/taskflow-4.6.3/doc/source/user/ |
| H A D | atoms.rst | 90 to subflow atoms each time a failure occurs (making it possibly to resolve
91 the failure by altering subflow atoms inputs).
126 associated failure.
139 .. doctest::
157 each failure occurs. On each run :py:class:`~taskflow.retry.ForEach` retry
158 returns the next value from the collection and stops retrying a subflow if
161 it with the next value from the given collection ``['a', 'b', 'c']``. But if
164 retry ``r1`` (so they will not *consult* ``r1`` on failure).
166 .. doctest::
180 .. doctest::
[all …]
|
| /dports/math/octave-forge-doctest/doctest-0.7.0/inst/ |
| H A D | doctest.m | 33 %% @deftypefn {} {} doctest @var{target}
58 %% @code{doctest doctest} will execute this code:
68 %% If there's no output, just put the next line right after the one with
70 %% this will be recorded as a test failure.
142 %% >> a = 6 % doctest: +SKIP
144 %% >> plot(...) % doctest: +SKIP
154 %% >> a = 6 % doctest: +XFAIL
223 %% expected output by searching for the next @code{>>} or two blank lines.
236 %% A typical Texinfo-style doctest looks like:
252 function varargout = doctest(what, varargin) function
[all …]
|
| /dports/devel/doctest/doctest-2.4.7/doc/markdown/ |
| H A D | tutorial.md | 3 …d with **doctest** all you need is to download the [**latest version**](https://raw.githubusercont…
21 #include "doctest.h"
47 Now we get a failure - something like:
70 Although this was a simple test it's been enough to demonstrate a few things about how **doctest** …
83 **doctest** takes a different approach (to both NUnit and xUnit) that is a more natural fit for C++…
111 …doctest** to see if the subcase should be executed. One leaf subcase is executed on each run throu…
122 #include "doctest.h"
176 …er leaf subcase (so no leaf subcase can interfere with another). A fatal failure in a parent subca…
178 …doctest** is [**thread-safe**](faq.md#is-doctest-thread-aware) - using subcases has to be done onl…
188 #include "doctest.h"
[all …]
|
| /dports/devel/cquery/cquery-20180718/third_party/doctest/doc/markdown/ |
| H A D | tutorial.md | 3 …d with **doctest** all you need is to download the [**latest version**](https://raw.githubusercont…
21 #include "doctest.h"
47 Now we get a failure - something like:
70 Although this was a simple test it's been enough to demonstrate a few things about how **doctest** …
72 …doctest.h"``` and go. Usually it's a good idea to have a dedicated implementation file that just h…
83 **doctest** takes a different approach (to both NUnit and xUnit) that is a more natural fit for C++…
111 …doctest** to see if the subcase should be executed. One leaf subcase is executed on each run throu…
122 #include "doctest.h"
176 …er leaf subcase (so no leaf subcase can interfere with another). A fatal failure in a parent subca…
186 #include "doctest.h"
[all …]
|
| /dports/devel/doctest/doctest-2.4.7/ |
| H A D | CHANGELOG.md | 3 ## [2.4.7](https://github.com/doctest/doctest/tree/2.4.7) (2021-12-10)
4 [Full Changelog](https://github.com/doctest/doctest/compare/2.4.6...2.4.7)
20 - compiler errors in doctest.h using cmake in CLion [\#540](https://github.com/doctest/doctest/issu…
36 - Running doctest on embedded ARM Cortex µCs [\#506](https://github.com/doctest/doctest/issues/506)
98 - Compile failure with WinRT on 2.4.5 [\#465](https://github.com/doctest/doctest/issues/465)
226 - doctest in embedded [\#355](https://github.com/doctest/doctest/issues/355)
376 - Build failure on clang 7.0.1 on Fedora 29 [\#214](https://github.com/doctest/doctest/issues/214)
515 … BREAKING CHANGE !!! - Move to C++11 for next version of the library [\#137](https://github.com/do…
615 - Static Analysis results of doctest [\#83](https://github.com/doctest/doctest/issues/83)
648 - Print the test suite name on test case failure [\#65](https://github.com/doctest/doctest/issues/6…
[all …]
|
| /dports/databases/py-sqlite3/Python-3.8.12/Doc/library/ |
| H A D | doctest.rst | 4 .. module:: doctest
160 example(s) and the cause(s) of the failure(s) are printed to stdout, and the
236 cause(s) of the failure(s) are printed to stdout, using the same format as
327 line containing the code, and the expected output (if any) extends to the next
656 incorrect examples that fail independently of the first failure. When
667 failure won't even produce debugging output.
899 raised upon the first failure or unexpected exception in an example. This
951 Optional argument *name* is used in failure messages, and defaults to
955 failures. By default, output is generated only in case of an example failure.
1721 failure is encountered. If an unexpected exception occurs, an
[all …]
|
| /dports/databases/py-gdbm/Python-3.8.12/Doc/library/ |
| H A D | doctest.rst | 4 .. module:: doctest
160 example(s) and the cause(s) of the failure(s) are printed to stdout, and the
236 cause(s) of the failure(s) are printed to stdout, using the same format as
327 line containing the code, and the expected output (if any) extends to the next
656 incorrect examples that fail independently of the first failure. When
667 failure won't even produce debugging output.
899 raised upon the first failure or unexpected exception in an example. This
951 Optional argument *name* is used in failure messages, and defaults to
955 failures. By default, output is generated only in case of an example failure.
1721 failure is encountered. If an unexpected exception occurs, an
[all …]
|
| /dports/lang/python37/Python-3.7.12/Doc/library/ |
| H A D | doctest.rst | 6 .. module:: doctest
162 example(s) and the cause(s) of the failure(s) are printed to stdout, and the
238 cause(s) of the failure(s) are printed to stdout, using the same format as
329 line containing the code, and the expected output (if any) extends to the next
658 incorrect examples that fail independently of the first failure. When
669 failure won't even produce debugging output.
901 raised upon the first failure or unexpected exception in an example. This
953 Optional argument *name* is used in failure messages, and defaults to
957 failures. By default, output is generated only in case of an example failure.
1723 failure is encountered. If an unexpected exception occurs, an
[all …]
|
| /dports/lang/python38/Python-3.8.12/Doc/library/ |
| H A D | doctest.rst | 4 .. module:: doctest
160 example(s) and the cause(s) of the failure(s) are printed to stdout, and the
236 cause(s) of the failure(s) are printed to stdout, using the same format as
327 line containing the code, and the expected output (if any) extends to the next
656 incorrect examples that fail independently of the first failure. When
667 failure won't even produce debugging output.
899 raised upon the first failure or unexpected exception in an example. This
951 Optional argument *name* is used in failure messages, and defaults to
955 failures. By default, output is generated only in case of an example failure.
1721 failure is encountered. If an unexpected exception occurs, an
[all …]
|
| /dports/lang/python-tools/Python-3.8.12/Doc/library/ |
| H A D | doctest.rst | 4 .. module:: doctest
160 example(s) and the cause(s) of the failure(s) are printed to stdout, and the
236 cause(s) of the failure(s) are printed to stdout, using the same format as
327 line containing the code, and the expected output (if any) extends to the next
656 incorrect examples that fail independently of the first failure. When
667 failure won't even produce debugging output.
899 raised upon the first failure or unexpected exception in an example. This
951 Optional argument *name* is used in failure messages, and defaults to
955 failures. By default, output is generated only in case of an example failure.
1721 failure is encountered. If an unexpected exception occurs, an
[all …]
|
| /dports/lang/python39/Python-3.9.9/Doc/library/ |
| H A D | doctest.rst | 4 .. module:: doctest
160 example(s) and the cause(s) of the failure(s) are printed to stdout, and the
236 cause(s) of the failure(s) are printed to stdout, using the same format as
327 line containing the code, and the expected output (if any) extends to the next
656 incorrect examples that fail independently of the first failure. When
667 failure won't even produce debugging output.
899 raised upon the first failure or unexpected exception in an example. This
951 Optional argument *name* is used in failure messages, and defaults to
955 failures. By default, output is generated only in case of an example failure.
1721 failure is encountered. If an unexpected exception occurs, an
[all …]
|
| /dports/x11-toolkits/py-tkinter/Python-3.8.12/Doc/library/ |
| H A D | doctest.rst | 4 .. module:: doctest
160 example(s) and the cause(s) of the failure(s) are printed to stdout, and the
236 cause(s) of the failure(s) are printed to stdout, using the same format as
327 line containing the code, and the expected output (if any) extends to the next
656 incorrect examples that fail independently of the first failure. When
667 failure won't even produce debugging output.
899 raised upon the first failure or unexpected exception in an example. This
951 Optional argument *name* is used in failure messages, and defaults to
955 failures. By default, output is generated only in case of an example failure.
1721 failure is encountered. If an unexpected exception occurs, an
[all …]
|
| /dports/lang/python311/Python-3.11.0a3/Doc/library/ |
| H A D | doctest.rst | 4 .. module:: doctest
160 example(s) and the cause(s) of the failure(s) are printed to stdout, and the
236 cause(s) of the failure(s) are printed to stdout, using the same format as
327 line containing the code, and the expected output (if any) extends to the next
655 incorrect examples that fail independently of the first failure. When
666 failure won't even produce debugging output.
898 raised upon the first failure or unexpected exception in an example. This
950 Optional argument *name* is used in failure messages, and defaults to
954 failures. By default, output is generated only in case of an example failure.
1720 failure is encountered. If an unexpected exception occurs, an
[all …]
|
| /dports/lang/python310/Python-3.10.1/Doc/library/ |
| H A D | doctest.rst | 4 .. module:: doctest
160 example(s) and the cause(s) of the failure(s) are printed to stdout, and the
236 cause(s) of the failure(s) are printed to stdout, using the same format as
327 line containing the code, and the expected output (if any) extends to the next
656 incorrect examples that fail independently of the first failure. When
667 failure won't even produce debugging output.
899 raised upon the first failure or unexpected exception in an example. This
951 Optional argument *name* is used in failure messages, and defaults to
955 failures. By default, output is generated only in case of an example failure.
1721 failure is encountered. If an unexpected exception occurs, an
[all …]
|
| /dports/lang/python-legacy/Python-2.7.18/Doc/library/ |
| H A D | doctest.rst | 6 .. module:: doctest
170 example(s) and the cause(s) of the failure(s) are printed to stdout, and the
208 import doctest
247 cause(s) of the failure(s) are printed to stdout, using the same format as
334 line containing the code, and the expected output (if any) extends to the next
668 incorrect examples that fail independently of the first failure. When
903 raised upon the first failure or unexpected exception in an example. This
969 Optional argument *name* is used in failure messages, and defaults to
973 failures. By default, output is generated only in case of an example failure.
1787 failure is encountered. If an unexpected exception occurs, an
[all …]
|
| /dports/lang/python27/Python-2.7.18/Doc/library/ |
| H A D | doctest.rst | 6 .. module:: doctest
170 example(s) and the cause(s) of the failure(s) are printed to stdout, and the
208 import doctest
247 cause(s) of the failure(s) are printed to stdout, using the same format as
334 line containing the code, and the expected output (if any) extends to the next
668 incorrect examples that fail independently of the first failure. When
903 raised upon the first failure or unexpected exception in an example. This
969 Optional argument *name* is used in failure messages, and defaults to
973 failures. By default, output is generated only in case of an example failure.
1787 failure is encountered. If an unexpected exception occurs, an
[all …]
|
| /dports/math/octave-forge-doctest/doctest-0.7.0/inst/private/ |
| H A D | doctest_collect.m | 16 % This is Free Software, BSD-3-Clause, see doctest.m for details.
41 % comes after 'file' above for "doctest @class/method"
62 % covers "doctest @class", but not "doctest @class/method"
65 % covers "doctest class"
72 % covers "doctest class.method" and "doctest class/method"
87 % cheap hack to not indent when calling "doctest ."
193 % run doctest
229 fprintf(fid, ' expected failure, but test succeeded!');
423 % special comments "@c doctest: cmd" are translated
427 '(doctest:\s*.*)' ]; % want the doctest token
[all …]
|
| /dports/textproc/py-petl/petl-1.7.4/.github/workflows/ |
| H A D | test-changes.yml | 22 run: echo Resuming CI. Continuing next jobs...
82 echo 'Dismissed failure installing some optional package. Resuming tests...'
125 …nosetests -v --with-coverage --cover-package=petl --with-doctest --doctest-options=+NORMALIZE_WHIT…
|
| /dports/astro/py-astropy/astropy-5.0/docs/development/ |
| H A D | testguide.rst | 1 .. doctest-skip-all
353 then on the local copy will be used transparently. See the next section for
636 test cases and each failure would be a distinct issue, and Hypothesis
638 failure to be reported.
871 skip a doctest:
895 usage as a doctest, the entire function can be skipped in the doctest
916 .. doctest-skip::
926 .. doctest-skip-all
982 ``# doctest: +IGNORE_OUTPUT`` flag. This allows a doctest to execute (and
1039 or because the failure happens with only 32-bit Python.
[all …]
|
| /dports/multimedia/tautulli/Tautulli-2.8.0/lib/ |
| H A D | IPy.py | 1077 l = next(left)
1078 r = next(right)
1084 l = next(left)
1088 r = next(right)
1091 l = next(left)
1158 l = next(left)
1159 r = next(right)
1164 l = next(left)
1656 import doctest
1657 failure, nbtest = doctest.testmod() variable
[all …]
|
| /dports/net-mgmt/py-ipy/IPy-1.01/ |
| H A D | IPy.py | 1077 l = next(left)
1078 r = next(right)
1084 l = next(left)
1088 r = next(right)
1091 l = next(left)
1158 l = next(left)
1159 r = next(right)
1164 l = next(left)
1656 import doctest
1657 failure, nbtest = doctest.testmod() variable
[all …]
|
| /dports/science/py-cirq-aqt/Cirq-0.12.0/.github/workflows/ |
| H A D | ci.yml | 62 mypy-next:
63 name: Type check (next)
74 run: check/mypy --next || true
119 run: check/doctest -q
274 if: failure()
296 if: failure()
|
| /dports/science/py-cirq-core/Cirq-0.13.1/.github/workflows/ |
| H A D | ci.yml | 62 mypy-next:
63 name: Type check (next)
74 run: check/mypy --next || true
119 run: check/doctest -q
274 if: failure()
292 if: failure()
|