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

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
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
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
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
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
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

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
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
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews