Good practices for testing remote Turbo Frames

I’m curious what patterns people are using for testing responses from remote loaded Turbo Frames. We end up with a lot of tests that look like this:

get foo_path
assert_response %(turbo-frame[src="#{bar_path}"]), count: 1

get bar_path
assert_response "div"

But it has a few downsides: it’s fairly verbose, and it isn’t easy to assert the combined content between foo_path and bar_path (which is what you’d be seeing in the browser now).

Has anyone got any nice patterns they can share for writing these sorts of tests?

System tests run in the browser and execute javascript, allowing you to test the presence of content loaded asynchronously.