Step to switch Capybara sessions

[matzke]

http://collectiveidea.com/blog/archives/2011/08/04/simultaneous-capybara-sessions-in-cucumber/

[foobear]

If a project wants to switch between multiple Capybara sessions, we recommend you add steps for that in the project. However, a single Capybara session is enough for almost all projects.

We won't be implementing this feature ourselves. Is this something you use regularly?

[matzke]

I use this regularly in projects with shared data access for testing optimistic locking (https://api.rubyonrails.org/classes/ActiveRecord/Locking/Optimistic.html) on data objects ...

• user A logs in and starts editing a shared database entry/object
• user B logs in and edits and saves the same object before A is ready
• user A saves his object and gets an "sorry data is already updated, please review"

... or else data would be overwritten.

However I understand, that different projects do not work on shared data or do not test it, because of time/money/etc.

[triskweline]

We have two projects where we also needed to test content locking. We solved that with custom steps that open new tabs via JavaScript. If we want to support this, I think the proposed step (When I am in the other user's browser) would make for a prettier Cucumber story than opening a new tab and hoping the test reader understands that this other tab represents the other user.

Another use case that I had once was realtime updates from another user (implemented with ActionCable, PubNubSub, Pusher or similar).

[foobear]

Using separate sessions for testing locking is a good use case, and saner than using a separate tab or window.

So let's add a step for that to Spreewald. Suggestions welcome. :)