Fl4m3Ph03n1x

Fl4m3Ph03n1x

I have a Behaviour that forces whoever implements it to implement a couple functions. For the sake of this discussion, let’s take the examples from the behaviours documentation.

defmodule Parser do
  @callback parse(String.t) :: {:ok, term} | {:error, String.t}
  @callback extensions() :: [String.t]
end

Now, let’s imagine that I see some repetition in the modules that implement this behaviour or that I want to add an universal parse! method. The preferred approach for this would be to use dynamic dispatching:

defmodule Parser do
  @callback parse(String.t) :: {:ok, term} | {:error, String.t}
  @callback extensions() :: [String.t]

  def parse!(implementation, contents) do
    case implementation.parse(contents) do
      {:ok, data} -> data
      {:error, error} -> raise ArgumentError, "parsing error: #{error}"
    end
  end
end

But now I am left with a question. How would I test parse! ?
Since this is pretty much working like an abstarct class at this point, how would you test it?

The only way I see it would be to use a Mock for the implementation parameter, but I am not sure about this approach.

Any ideas?

Showing Posts 1 to 2

yurko

yurko

I’d go for a bit of macros and implement a module that has the repetitive pars and is used by other modules that can override this functionality. S. GenServer for an example: elixir/lib/elixir/lib/gen_server.ex at v1.7.3 · elixir-lang/elixir · GitHub unless your server module implements it’s own terminate/2 the default is called.

Qqwy

Qqwy

TypeCheck Core Team

Creating a ‘fake’, or ‘simple’ implementation of the behaviour for testing purposes is a very common approach, so you do not have to feel unsure about this one :slight_smile:.

Of course, this only is able to test the behaviour itself, not the various implementations of it.

— All posts loaded —

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
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
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

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews