pwightman

pwightman

I have a form that starts like this:

When clicking “yes”, another form element appears:

The markup looks something like this:

    <%= f = form_container @changeset %>
      <%= question_title "Are you currently married?" %>
      <%= yes_no_buttons(f, :is_married) %>
      <%= if get_field(f, :is_married) do %>
        <div>
         <%= date_input_container(f, :marriage_date, "Marriage Date") %>
        </div>
      <% end %>
      <%= submit_button(f, @form_info) %>
    </form>

My initial attempt at a test looked something like this:

test "integration test", %{conn: conn} do
  form = create_form()

  {:ok, view, _disconnected_html} =
    live(conn, Routes.the_thing_path(conn, :index, form.uuid))

  view
  |> form("#step-form", data: %{"is_married" => "yes", "marriage_date" => "03/03/1999"})
  |> render_submit()
end

But this gives the following error, since the marriage_date input doesn’t exist until after is_married has been set:

     ** (ArgumentError) could not find non-disabled input, select or textarea with name "data[marriage_date]" within:

         <input name="_csrf_token" type="hidden" value="MHc6UyMLHB4HXjMDKCAkAiUJFTUGLTx0b2vgBHCHIleiwpirqBbpYBD1"/>
         <input class="form-check-input" id="step-form_is_married_yes" name="data[is_married]" type="radio" value="yes"/>
         <input class="form-check-input" id="step-form_is_married_no" name="data[is_married]" type="radio" value="no"/>

What would be a good way to integration test this scenario? I could attempt to “preload” some initial data into the data structure, but that sort of defeats the purpose of integration testing. I would hope that I could do something like:

view
|> form("#step-form")
|> update_form(data: %{"is_married" => true})
|> update_form(data: %{"is_married" => true, "marriage_date" => "03/03/1999"})
|> render_submit()

But that’s not a thing, and as far as I can tell, none of the provided functionality in LiveViewTest allows one to “interactively” fill out the form. I could settle for maybe manually calling the handle_event call in my LiveView that handles the data updates, but I don’t see how that’s done either. Any ideas?

Showing Posts 1 to 2

APB9785

APB9785

Creator of ECSx
view
|> element("#step-form") 
|> render_change(%{data: %{"is_married": "yes"}})

view
|> form("#step-form", %{data: %{"is_married" => "yes", "marriage_date" => "03/03/1999"}})
|> render_submit
pwightman

pwightman OP

Awesome, thank you! It throws me off that the view is stateful, I kept thinking once a render_* method was called, the view was “gone” and you just had the rendered string left, but it makes more sense now.

— 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
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
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
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