begedin
I’m trying to write a library which provides a complex phoenix live component the the app dependant on it.
As part of that, I’m also trying to test it, but it’s looking like being able to test the component in a deeper way is a tad complicated.
I effectively have to
- setup a full phoenix application, with an endpoint
- setup a view which renders the component and fully delegates all component interaction onto it’s own state
- setup a route for that view if I render using
live, or uselive_isolated - interact with and assert on the view itself, rather than the component
It works, but I’m wondering if anyone figured out anything simpler. Is there anything on the roadmap to simplify it?
It would even be useful to have just a conversation about it.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
eksperimental
I am sure if this could be useful, maybe you can use this as a starting point.
https://github.com/eksperimental/lean_phoenix_server
you will have to add LiveView
tfwright
I am working on a similar project and I just mimicked the approach in this test_helper from LiveDashboard. It has some stuff specific to that project so I was able to prune it down a bit from there.
begedin
Wont have time to check until the next weekend, but it looks like it might be. Thank you for this.
begedin
Didn’t actually consider looking at live dashboard, but it looks like it might be it. Seems like it sets up the bare minimum I’m looking for.
petemcfarlane
I wanted to do this today. In my test I defined a TestView module, which had a minimal
render()function, then I passed this to live_isolated() as a second parameter.This worked quite well, but it was awkward to test that
handle_eventcalls were bubbling up to the parent view, I also had to define a minimalhandle_eventfunction in theTestView, which assigned some properties to the socket, and then had a conditional in my render function to return a completely different view.I wonder if we could create a
live_component_in_viewfunction or something that just takes the stateful component, and add some other assertion forassert_handle_event("event", params)?begedin
That would be my ideal scenario. I was going to look into it this weekend and try and figure it out. That + some way to ship css and js easily with the component, as a library, would really allow for an easier time with portable 3rd party components.