nittin

nittin

How to ensure 100% code coverage for Ash?

I’m using ExCoveralls to measure code coverage in an Ash-based project, and I noticed that lines written through Ash DSL macros don’t appear as SLOC in the coverage report.

For example, in the following action:

create :create_task do
  ...
  change set_attribute(:state, "created")
end

the macro line isn’t counted toward coverage. However, when I rewrite it using an anonymous function:

create :create_task do
  ...
  change fn changeset, _context ->
    Ash.Changeset.set_attribute(changeset, :state, "created")
  end
end

the lines inside the function are counted as SLOC.

Is there any recommended way to get meaningful coverage metrics when using Ash DSL macros?
Are there any tools or approaches that better support coverage reporting for Ash-generated code?

Thanks!

First 2 of 2 Posts Switch mode

ken-kost

ken-kost

They are compile-time constructs, it’s a limitation of coverage tools with metaprogramming, not specific to Ash. You did find a trick to turn it into runtime code but the question is why even do this, i.e. 100% sounds better but beyond that is it really necessary?

arcanemachine

arcanemachine

Meaningful code coverage != 100% code coverage

Ensure the code is well-tested, then look at the number that comes out. That’s the number you need. 80% is generally considered very good.

Don’t waste your time trying to get 100% code coverage.

— All posts loaded —

Where Next?

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
silverdr
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated! To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead. Sta...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
michallepicki
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
type1fool
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
akoutmos
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New

We're in Beta

About us Mission Statement