doctest
Here are 58 public repositories matching this topic...
-
Updated
May 24, 2020 - CMake
I have documentation that looks like this
{-| Start creating a codec for a record.
type alias Point =
{ x : Int
, y : Int
}
pointCodec : Codec Point
pointCodec =
Codec.object Point
-- Note that adding, removing, or reordering fields will prevent you from decoding any data you've previously encoded.
|> Codec.-
Updated
Jun 26, 2019 - JavaScript
sphinx.ext.doctest lets you write doctests in your prose documentation (e.g. .rst files), which is really useful for ensuring that usage examples in those docs do in fact still work.
If it's possible to use xdoctest instead of the standard library doctest, that would be lovely - and could do with documentation. If not,
-
Updated
Jun 14, 2020 - TypeScript
Should add note for power-doctest auto mocking
-
Updated
Sep 12, 2018 - CMake
-
Updated
Sep 30, 2018 - Python
-
Updated
May 31, 2020 - Haxe
-
Updated
Jun 12, 2020
-
Updated
Aug 27, 2018 - Elm
Describe the feature you'd like
Now that we support Python 3.x only, it would be cool to modernize
a little the code.
-
Updated
Apr 5, 2020 - TypeScript
-
Updated
Jan 1, 2017 - Haskell
-
Updated
Dec 9, 2019 - C++
-
Updated
Oct 30, 2018 - CMake
-
Updated
Jun 2, 2018 - Crystal
-
Updated
Jun 1, 2020 - Julia
-
Updated
Nov 4, 2019 - Haskell
-
Updated
May 31, 2020 - Python
Improve this page
Add a description, image, and links to the doctest topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the doctest topic, visit your repo's landing page and select "manage topics."
I couldn't find this in the documentation or the FAQ: Is it possible to obtain the current test case's name from within that testcase's code? I mean, it should be, but how do we do it? That should be either in the FAQ or in some other relevant documentation file, IMHO.