home.social

#doctest — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #doctest, aggregated by home.social.

fetched live
  1. Released an updated version (0.3.1) of sijo-doctest, a #doctest library for
    #CommonLisp.

    This includes some quality of life features, bugfixes and support for #SBCL, #ECL, #CCL and #ABCL.

    github.com/simendsjo/sijo-doct

  2. Released an updated version (0.3.1) of sijo-doctest, a library for
    .

    This includes some quality of life features, bugfixes and support for , , and .

    github.com/simendsjo/sijo-doct

  3. Released an updated version (0.3.1) of sijo-doctest, a #doctest library for
    #CommonLisp.

    This includes some quality of life features, bugfixes and support for #SBCL, #ECL, #CCL and #ABCL.

    github.com/simendsjo/sijo-doct

  4. I have even played around with a few #microformats on top of JDAML -- one codenamed #Znatchke which is something in between HTML and #Markdown and one which shows how something like #doctest could be implemented with JDAML (suggested by @RyunoKi).

  5. I have even played around with a few #microformats on top of JDAML -- one codenamed #Znatchke which is something in between HTML and #Markdown and one which shows how something like #doctest could be implemented with JDAML (suggested by @RyunoKi).

  6. I have even played around with a few #microformats on top of JDAML -- one codenamed #Znatchke which is something in between HTML and #Markdown and one which shows how something like #doctest could be implemented with JDAML (suggested by @RyunoKi).

  7. When teaching #rust, I often see people have a "Wow 🤯!" experience when I show #rustdoc #doctest system: you write small pieces of Rust code in your documentation and they are then executed as part of your test suite.

    What people often don't know is that this system is ancient! I first met in #python and there it was introduced in 1999: groups.google.com/g/comp.lang.. That's 24 years ago!

    I don't know if this was the first implementation of this concept?

  8. When teaching #rust, I often see people have a "Wow 🤯!" experience when I show #rustdoc #doctest system: you write small pieces of Rust code in your documentation and they are then executed as part of your test suite.

    What people often don't know is that this system is ancient! I first met in #python and there it was introduced in 1999: groups.google.com/g/comp.lang.. That's 24 years ago!

    I don't know if this was the first implementation of this concept?

  9. When teaching #rust, I often see people have a "Wow 🤯!" experience when I show #rustdoc #doctest system: you write small pieces of Rust code in your documentation and they are then executed as part of your test suite.

    What people often don't know is that this system is ancient! I first met in #python and there it was introduced in 1999: groups.google.com/g/comp.lang.. That's 24 years ago!

    I don't know if this was the first implementation of this concept?

  10. When teaching #rust, I often see people have a "Wow 🤯!" experience when I show #rustdoc #doctest system: you write small pieces of Rust code in your documentation and they are then executed as part of your test suite.

    What people often don't know is that this system is ancient! I first met in #python and there it was introduced in 1999: groups.google.com/g/comp.lang.. That's 24 years ago!

    I don't know if this was the first implementation of this concept?

  11. I created a small extension that parses `pycon` syntax code blocks *without indentation and without fences*, and renders them using 's Highlight extension 🙂

    It will be useful in Python docstrings, to add examples anywhere just how expects them!

    It's immediately available to my sponsors and has been added to the GraviFridge goal (pawamoy.github.io/insiders/#10) 😊

  12. I created a small #Python #Markdown extension that parses `pycon` syntax code blocks *without indentation and without fences*, and renders them using #pymdownx's Highlight extension 🙂

    It will be useful in Python docstrings, to add examples anywhere just how #doctest expects them!

    It's immediately available to my sponsors and has been added to the GraviFridge goal (pawamoy.github.io/insiders/#10) 😊

  13. Ebenso kannte ich zwar "#unittest", aber "#doctest" war neu für mich, und auf den ersten Blick sogar eleganter, da die Tests im jeweiligen #docstring definiert werden, damit sofort erkennbar sind und auch noch als Dokumentation herhalten können. #python3

  14. Ebenso kannte ich zwar "#unittest", aber "#doctest" war neu für mich, und auf den ersten Blick sogar eleganter, da die Tests im jeweiligen #docstring definiert werden, damit sofort erkennbar sind und auch noch als Dokumentation herhalten können. #python3

  15. 🌠 I created a #GitHub repository with my #Python solutions for the #AdventOfCode puzzles

    🧩 All solutions use only the #PythonStandardLibrary with no need for external packages

    🔬 #Tests are included in function #docstrings and can be run using the #doctest module

    ⚠️ I don't think I will be able to enter the #solutions every day and definitely not in the morning

    🐍 I participate in #AoC to #improve my Python #knowledge rather than to compete in the #leaderboard

    👇
    github.com/pauloxnet/adventofc

  16. 🌠 I created a repository with my solutions for the puzzles

    🧩 All solutions use only the  with no need for external packages

    🔬  are included in function and can be run using the  module

    ⚠️ I don't think I will be able to enter the every day and definitely not in the morning

    🐍 I participate in to my Python rather than to compete in the

    👇
    github.com/pauloxnet/adventofc

  17. 🌠 I created a #GitHub repository with my #Python solutions for the #AdventOfCode puzzles

    🧩 All solutions use only the #PythonStandardLibrary with no need for external packages

    🔬 #Tests are included in function #docstrings and can be run using the #doctest module

    ⚠️ I don't think I will be able to enter the #solutions every day and definitely not in the morning

    🐍 I participate in #AoC to #improve my Python #knowledge rather than to compete in the #leaderboard

    👇
    github.com/pauloxnet/adventofc

  18. 🌠 I created a #GitHub repository with my #Python solutions for the #AdventOfCode puzzles

    🧩 All solutions use only the #PythonStandardLibrary with no need for external packages

    🔬 #Tests are included in function #docstrings and can be run using the #doctest module

    ⚠️ I don't think I will be able to enter the #solutions every day and definitely not in the morning

    🐍 I participate in #AoC to #improve my Python #knowledge rather than to compete in the #leaderboard

    👇
    github.com/pauloxnet/adventofc

  19. @HeidiSeibold I also write tests for my software. They are not primarily for usability but mostly for assuring quality and correctness, but I also think they can serve to demonstrate how the software works or should be expected to work.
    In , one testing framework, , is convenient for incorporating tests as examples into the documentation. This way they can both serve as usage examples in the before-mentioned docstrings and as automated tests.

  20. Did you know, that @[email protected] once ported #doctest (like known from #python, @[email protected], #cpp, #haskell, @[email protected], @[email protected] ) to @[email protected]?

    github.com/skippi/docspec#usag

    PS: Didn't try it yet but I'm pretty sure that it won't work in current Crystal versions without a patch.

  21. Did you know, that @[email protected] once ported @[email protected]'s #doctest to @[email protected]?

    github.com/skippi/docspec#usag

    PS: I didn't try it yet but I'm pretty sure that it won't work in current Crystal versions.

    RT @[email protected]

    skippi/docspec: A crystal library for automatically testing documentation examples. - github.com/skippi/docspec

    🐦🔗: twitter.com/fusillicode/status