fireproofsocks

fireproofsocks

I’m working on a umbrella app that relies on the built-in test coverage tools to generate reports, e.g

mix test --cover --export-coverage default
mix test.coverage

I’m noticing that modules that do nothing other than declare structs and mocked modules (mocked via mox) both show up as 0% coverage in the coverage report. For example:

defmodule Bar do
  defstruct [:a, :b, :c]
end
Mox.defmock(FooMock, for: Foo)

earn both modules an entry in the report, e.g.

Percentage | Module
-----------|--------------------------
     0.00% | Bar
     0.00% | FooMock
-----------|--------------------------
     0.00% | Total

Is the only way to ignore these types of modules from the final output to explicitly list them in the ignore_modules section, e.g.

def project do
[
    # ...
    test_coverage: [ignore_modules: [Bar, FooMock]]
]
end

There are reasons why we cannot currently use excoveralls or other tools for this (even though ExCoveralls doesn’t “mis-diagnose” these particular cases IIRC). Is there some other way to modify our report? Or is this report actually telling us something useful that I have overlooked?

Thanks for any insights!

First Post!

tjchambers

tjchambers

Did you ever get a response to this? Would be interested.

Last Post!

sodapopcan

sodapopcan

According to the docs, mix test.cover only covers executable lines of code. See here. It mentions:

Code in macros are also often executed at compilation time, and therefore may not be covered.

so that likely includes defstruct.

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

Latest on Elixir Forum

Elixir Forum

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews