lenards
Any way to use Credo to check for `ExUnit.DocTest.doctest` occurrences?
I recently noticed in our codebase had some iex> usage in doc strings, but those modules did not have a corresponding ExUnit.DocTest.doctest/2. Some of the authors of these helpful iex> examples did not realize there was an extra step to get this examples checked as test (when I was new Elixir, I also did not realize this).
Is there any way to automate checks for this? Or is there something we might add to our Credo configure?
Curious if there might be a way to help avoid missing out on the feedback and checks. I love DocTest examples and want to keep promote their use.
Thanks in advance for thoughts or points.
First Post!
kanishka
For now, I created this small documentation PR: Update docs-tests-and-with.markdown · Pull Request #1669 · elixir-lang/elixir-lang.github.com · GitHub . Maybe others can suggest a better improvement to highlight this area.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









