I have just published a video about doing TDD with Livebook:
If you are not a video person, take a look at the notebook here.
If you can run an instance of livebook, click here:
The code I typed was that of a very simple calculator. Every function was written after a test for that function was written.
defmodule Calculator do def add(a, b) do a + b end def multiply(a, b) do a * b end end
Unfortunately, Livebook seems to force us to put the tests below the code that is being tested.
And, as Bro0klin Myers explained here, you have to add:
to the beginning of your test code.
You also have to put this line in your test module:
use ExUnit.Case, async: false
And you have to finish your test code with this line:
The content for the test code cell is:
ExUnit.start(auto_run: false) defmodule CalcutorTest do use ExUnit.Case, async: false describe "Testing the addition function" do test "2 plus 3 is 5" do assert Calculator.add(2, 3) == 5 end test "2 plus 2 is 4" do assert Calculator.add(2, 2) == 4 end end describe "Testing the multiplication function" do test "2 times 3 is 6" do assert Calculator.multiply(2, 3) == 6 end test "2 times 20 is 40" do assert Calculator.multiply(2, 20) == 40 end end end ExUnit.run()
What do you think? Is it a good idea to do TDD with Liveview?
Latest comments (2)
Hi Adolfo, Thank you for sharing this.
After following this format and replicating a basic, existing test connected to my project, the livebook test defaults to my dev database rather than the test database. This is muddying the data available for dev. Do you have any additional guidance on how to connect this test to the test database?
Sorry, I really don't know how to solve this problem. Did you ask at Elixir Forum? elixirforum.com/