I reported this issue to one of the Learn instructors during my pairing session. I deleted all the migrations, models, controllers so that all the tests were failing. Then I did the lab from scratch and got the tests passing. It's been 3 days since I reported this issue.

The master branch contains answers from the solution branch. Students are unable to work on it since it is completed.

It seems this test needs to clear the database before creating the admin user, because Amy Phoeler is still in there from a previous test. This means although the admin user is expected to be users/2, instead it got users/3

users_features_spec 48:

it 'prevents user from viewing user show page and redirects to home page if not logged in' do
    create_standard_user
    visit '/users/1'
    expect(current_path).to eq('/')
    expect(page).to have_content("Sign Up")
  end

The previous test requires creating a user to also log them in, but now this test doesn't log them out before visiting '/users/1', even though it is testing what happens if a user is logged out.

The solution user_login tells capybara to fill in a field on a from:
fill_in("user[name]", :with => "Mindy")

Whereas the master branch user_login say to select the name from the drop-down menu:
select 'Mindy',from:'user_name'

This confused a student, b/c the solution for 'sessions/new view' doesn't have code for a drop-down menu, like the test expects and the demo example shows.

According to params the only way to make these tests pass is if the password fields are written as such for these two methods

def user_login
select 'Mindy',from:'user_name'
fill_in("user[password]", :with => "password")
click_button('Sign In')
end

def admin_login
select 'Walt Disney',from:'user_name'
fill_in("user[password]", :with => "password")
click_button('Sign In')
end