-
Updated
Jun 6, 2022 - C++
#
doctest
Here are 82 public repositories matching this topic...
The fastest feature-rich C++11/14/17/20 single-header testing framework
testing
c-plus-plus
unit-testing
tdd
cpp
doctest
cpp14
cpp11
header-only
cpp17
single-file
testing-framework
cpp20
Boiler plate template for C++ projects, with CMake, Doctest, Travis CI, Appveyor, Github Actions and coverage reports.
coveralls
boilerplate
cmake
cpp
travis-ci
doctest
actions
project-template
code-review
codecov
template-project
code-coverage
folder-structure
cpp-17
github-actions
-
Updated
Jan 15, 2022 - CMake
A rewrite of Python's builtin doctest module (with pytest plugin integration) with AST instead of REGEX.
-
Updated
May 6, 2022 - Python
Catch2, Google Test and doctest Adapter for the VSCode
testing
typescript
cpp
doctest
vscode
googletest
gtest
vscode-extension
testing-tools
visual-studio-code-extension
catch2
testmate
-
Updated
May 22, 2022 - TypeScript
Run jsdoc examples as doctests.
-
Updated
Feb 10, 2021 - JavaScript
A simple, cross-platform, and continuously integrated C++14 project template
documentation
cmake
cpp
travis-ci
continuous-integration
doctest
cpp14
project-template
appveyor
doxygen
codecov
codacy
code-coverage
coverity-scan
codedocs
-
Updated
Sep 12, 2018 - CMake
eldipa
commented
Jun 2, 2022
Describe the feature you'd like
Because byexample runs on Python 3 only, these __future__ imports (unicode_literals and print_function) are not needed anymore as they are the default.
Removing them will make the code a little cleaner.
When removing the imports from the examples/test, extra care should be taken to not break them or to hide some under-testing thing.
enhancement
something nice to have but it is not neither critical nor urgent
good first issue
issues that should be easy to get done
How to test your python code. How to automatically run your tests for your Python code. How to get reports of the tests coverage
python
coveralls
travis-ci
continuous-integration
doctest
coverage-report
pytest
pylint
pytest-cov
measure-coverage
-
Updated
Sep 30, 2018 - Python
run black on documentation code snippets
-
Updated
May 9, 2022 - Python
A haxelib inspired by Python's doctest command that generates unit tests based on assertions specified within the source code.
-
Updated
Apr 18, 2022 - Haxe
Tabularised feature comparison between Catch, doctest and lest C++ test frameworks
-
Updated
Jul 12, 2021
doctests for typescript
-
Updated
Apr 8, 2022 - TypeScript
Julia library for functional testing.
-
Updated
May 19, 2022 - Julia
doctest runner against Elm-lang source files
-
Updated
May 28, 2022 - Elm
Benchmarks - Unit Testing Frameworks
-
Updated
Dec 9, 2019 - C++
Generate driver file for doctest's cabal integration.
-
Updated
Feb 14, 2022 - Haskell
Ninety-Nine Haskell Problems
-
Updated
Jan 1, 2017 - Haskell
cmake scripts for googletest / catch / doctest. Automatic tests registration, even inside library code.
-
Updated
Oct 30, 2018 - CMake
A crystal library for automatically testing documentation examples.
-
Updated
Jun 2, 2018 - Crystal
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."
Is there a how-to guide to write my own tool? I want to do some conditional stripping/modifying (e.g. insert a Python script into a cell) for a Kaggle notebook. I've been playing around for an hour and I've sort-of-got a tool working, but I can't get
nbqato pass in anything I can read. In my codesys.argvhas the original Notebook filename and if I rewrite that,nbqathrows an exception.k