SArthur
Test database vs. dev database when connecting Livebook notebook to local app
I am in love with Livebook! My hope is to use it for everything from data exploration and feature planning, documentation, and TDD in a cohesive way… amazing if it comes together!
On the TDD front, I have successfully connected a livebook notebook to my local app and am able to run basic tests. However, I’m stumped trying to test data creation. The snippet below worked the first time this was run (without the ref to the DataCase), but then fails thereafter because the original record is not being deleted after the test as happens with mix test. I tried adding the use DataCase line, but that results in the compile error below. Is this possible and can someone point me to any documentation to assist?
Many thanks in advance!
ExUnit.start(autorun: false)
defmodule MyTest do
use ExUnit.Case, async: true
# Everything above is boiler plate for livebook testing
use myApp.DataCase
alias myApp.Members
alias myApp.Members.Member
test "creates new Member with valid attrs and sets member_uuid" do
assert {:ok, %Member{member_uuid: member_uuid}} =
Members.create_member(%{name: "New Member", member_type: "foe", collapsed_name: "newmember"})
refute nil == member_uuid
end
end
# run below is boiler plate for livebook testing
ExUnit.run()
** (CompileError) priv/livebook/Adventures_in_testing.livemd#cell:6: module PreOrderApp.DataCase is not > loaded and could not be found
(elixir 1.13.2) expanding macro: Kernel.use/1
priv/livebook/Adventures_in_testing.livemd#cell:6: MyTest (module)
Most Liked
moogle19
Your mix.exs file probably contains the following lines:
defp elixirc_paths(:test), do: ["lib", "test/support"]
defp elixirc_paths(_), do: ["lib"]
so the "test/support" folder which contains your DataCase isn’t compiled in the default env for the notebook (which is :dev).
But I think there is currently no way to set the MIX_ENV before attaching to the notebook.
You could add:
defp elixirc_paths(:dev), do: ["lib", "test/support"]
above elixirc_paths(_) to compile the test/support files also in :dev.
Nezteb
Funnily enough I ran into this issue again, and my previous answer was close, but what I ended up doing is something like this:
MIX_ENV=test iex --sname nezteb --cookie nezteb -S mix phx.server
The MIX_ENV=test part is what I was missing last time. Livebook itself doesn’t need to run in test mode as long as you are using “Attached node” mode and connecting to your local iex sessions which is running with MIX_ENV=test. ![]()
Connect to the node in Livebook and then try something like this:
ExUnit.start(autorun: false)
defmodule MyAppTest do
# use ExUnit.Case, async: true
use MyApp.DataCase # this should work fine
test "it works" do
# Example using ExMachina (within the DataCase)
user = insert(:user)
assert user.id == 1
end
end
ExUnit.run()
Example evaluation:
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









