doing Minitest system tests in Capybara w/Cuprite but loosing current_user on form POSTs on Rails 7.2 w/TurboStream

[wdiechmann]

this may easily be just about the dumbest question - and switching to Cuprite (from Selenium) was a huge bone - but it did not solve my initial issue 😢 and I apologise if I'm addressing the wrong crowd [ed. perhaps this is a Cuprite question]

The controller is working (and I've tested all "manually" and it also works) and my tests are all green - except for this system test which "spans" a POST and reports the following on SLOMO=0.5 CI=true rails test test/system/teams_test.rb

Failure:
TeamsTest#test_should_create_team [test/system/teams_test.rb:24]:
expected to find text "Team was successfully created" in "You need to sign in or sign up before continuing. Log in Email Password Remember me Sign up Forgot your password?"

bin/rails test test/system/teams_test.rb:14

i've battled this all day with 20 tabs open on Google, going through every example I have been able to get my hands on - yet no one of them have thrusted me in the right direction -

(the index action requires the sign_in too and so does the /teams/new url which tells me that the sign_in works in teams_test.rb too)

require "application_system_test_case"

class TeamsTest < ApplicationSystemTestCase
  setup do
    sign_in users(:one)
    @team = teams(:one)
  end

  test "visiting the index" do
    visit teams_url
    assert_selector "h1", text: "Teams"
  end

  test "should create team" do
    visit teams_url
    click_on "New team"

    fill_in "Email", with: @team.email
    fill_in "Name", with: @team.name
    click_on "Create Team"

    assert_text "Team was successfully created"
    click_on "Back"
  end
end

with the controller teams#create looking like this

class TeamsController < ApplicationController
  before_action :authenticate_user!
  before_action :set_team, only: %i[ show edit update destroy ]

  # GET /teams or /teams.json
  def index
    @teams = Team.all
  end
  ...
  # POST /teams or /teams.json
  def create
    @team = Team.new(team_params)

    respond_to do |format|
      if @team.save
        format.html { redirect_to team_url(@team), allow_other_host: true, notice: "Team was successfully created." }
        format.json { render :show, status: :created, location: @team }
      else
        format.html { render :new, status: :unprocessable_entity }
        format.json { render json: @team.errors, status: :unprocessable_entity }
      end
    end
  end

 ...
  private
    # Use callbacks to share common setup or constraints between actions.
    def set_team
      @team = Team.find(params[:id])
    end

    # Only allow a list of trusted parameters through.
    def team_params
      params.require(:team).permit(:name, :email)
    end
end

[wdiechmann]

I decided to do what I should have done all along - rails new test, bundle add devise, more - and then add Cuprite as driver like it says on the tin 😄

To quote myself above it was easily ... about the dumbest question because I had c/p'ed the configuration verbatim from a post by someone who knew what they were doing!! So much for weaponizing monkeys 🤣

Once I edited the configuration to point to where I had actually put the configuration files everything was all confetti and hurrays

TIL: don't blindfoldedly copy/paste configurations