fchabouis
Test coverage includes dependencies?
Hi,
I tried the mix test --cover command and was surprised to see included in the results coverage analysis of the dependencies I use.
This doesn’t seem relevant to me, as I’m only interested in the coverage of my code.
Is this expected or am I doing something wrong ?
I have an umbrella app, and I tried to launch the command both on the root of the umbrella or for a specific app, the result is the same.
Thanks for your help !
Marked As Solved
hauleth
I assume that you are talking about all that Jason.Encoder.* modules:
These aren’t dependencies, these are actual modules in your application, just autogenerated as I assume you are using @derive Jason.Encoder in them. The reason for that is that is how the protocols work - under the hood these are behaviours with additional function that is runtime-dispatched.
Also Liked
Last Post!
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
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #hex
- #security










