onurozgurozkan
Hi folks,
When we run mix test --cover, we see some modules which starts with Inspect.XXX.XXX at cover results.
mix test --cover
Output
Generating cover results ...
Percentage | Module
-----------|--------------------------
0.00% | Inspect.Datalayer.Account
0.00% | Inspect.Datalayer.User
0.00% | Datalayer.Account
0.00% | Datalayer.User
0.00% | Datalayer.Number
- Our system has
Datalayer.Account,Datalayer.User, etc modules but has notInspect.Datalayer.Account,Inspect.Datalayer.Usermodules. - We have more than 20 modules, but only 5 of them generate
Inspect.XXX.XXXmodule when we runmix test --cover. - All these modules has
use Ecto.Schemabehavior.
My questions are
- To understand what is happening here?
- Any suggestion? Should I exclude these modules (Inspect.XXX.XXX) from test? etc.
Regards.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
awerment
To answer your first question:
Inspectis an Elixir protocol that is implemented for some of your schema modules. Most likely because you haveredact: trueset on some fields. Ecto derives a customInspectimplementation in that case.In general: for each protocol
Protothat is implemented for a moduleMod, there will be an implementation module calledProto.Mod.As for testing or excluding the modules, maybe somebody else has a recommendation. (I‘m not tracking test coverage in any of my projects) You could write tests that check if the schema fields are redacted when inspected - at that point you’d be testing Ecto itself though
onurozgurozkan
Dear @awerment,
Thank you for your reply. I really understand what is going on.
Regards.