oliveiragahenrique

oliveiragahenrique

I’m building a very simple application, every time you call ModuleX.get(id) the system perform the folowing actions:

  1. Search for id on database
  2. If sucess, return the id’s related value
  3. Otherwise create a default data structure and save it on the database under the id key

The problem is my docTests are failing because I use the same id on all of them. Because of it, operations on former tests impact on the result of the later ones, because of the data was persisted

Questions:

  1. Am I using doctests wrong?
  2. There is a way to perform a delete operation after each doctest?
  3. How did you guys would approach this problem?

Showing Posts 1 to 5

ityonemo

ityonemo

  1. this seems very ambitious for a doctest.
  2. are you using ecto sandboxes? I’m not 100% sure, but It should clean up after each doctest group. Try separating each of your cases into distinct ``` groups.
qhwa

qhwa

  1. No, there’s nothing wrong with it.
  2. Yes, as mentioned by @ityonemo, Ecto’s sandbox adapter helps. What’s inside your test/test_helper.exs ?
oliveiragahenrique

oliveiragahenrique OP

Actually my database is a very simple module that does binary parser and write it to disk using file name as identifier, I did not learn ecto yet.

I managed to make it work using the setup macro as following:

  setup do
    # Get the pids of all currently alive processes
    accounts_used_pids =
      DynamicSupervisor.which_children(Account.Cache)
      |> Stream.map(fn entry ->
        case entry do
          {_, pid, :worker, [Account.Server]} -> pid
          _ -> nil
        end
      end)
      |> Enum.filter(fn ele -> ele !== nil end)
    
    # Terminate all processes
    Enum.each(accounts_used_pids, &Process.exit(&1, :clean_up))
    
    # Reset the "database"
    File.rm_rf(Account.Database.folder_path())
    File.mkdir_p!(Account.Database.folder_path())

    :ok
  end

It might not be the optimal solution, but work for me! Thank you so much for the help!

oliveiragahenrique

oliveiragahenrique OP

Actually my database is a very simple module that does binary parser and write it to disk using file name as identifier, I did not learn ecto yet.

I managed to make it work using the setup macro as following:

  setup do
    # Get the pids of all currently alive processes
    accounts_used_pids =
      DynamicSupervisor.which_children(Account.Cache)
      |> Stream.map(fn entry ->
        case entry do
          {_, pid, :worker, [Account.Server]} -> pid
          _ -> nil
        end
      end)
      |> Enum.filter(fn ele -> ele !== nil end)
    
    # Terminate all processes
    Enum.each(accounts_used_pids, &Process.exit(&1, :clean_up))
    
    # Reset the "database"
    File.rm_rf(Account.Database.folder_path())
    File.mkdir_p!(Account.Database.folder_path())

    :ok
  end

It might not be the optimal solution, but work for me! Thank you so much for the help!

oliveiragahenrique

oliveiragahenrique OP

I managed to make it work using the setup macro as following:

  setup do
    # Get the pids of all currently alive processes
    accounts_used_pids =
      DynamicSupervisor.which_children(Account.Cache)
      |> Stream.map(fn entry ->
        case entry do
          {_, pid, :worker, [Account.Server]} -> pid
          _ -> nil
        end
      end)
      |> Enum.filter(fn ele -> ele !== nil end)
    
    # Terminate all processes
    Enum.each(accounts_used_pids, &Process.exit(&1, :clean_up))
    
    # Reset the "database"
    File.rm_rf(Account.Database.folder_path())
    File.mkdir_p!(Account.Database.folder_path())

    :ok
  end

The setup macro runs the code inside it after each test case. So I clean up the database and terminate all processes related to the account, after every test case.

It might not be the optimal solution, but work for me! Thank you so much for the help!

— All posts loaded —

Where Next? Top

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
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
roeland
Kia ora, We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
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
rahultumpala
Hello, I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance 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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
mcass19
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
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
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
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

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews