Commit 315cee0d41fc4057f7e09c48a18842cf7210b1a0

Authored by Rafael Manzo
Committed by Eduardo Silva Araújo
1 parent 69b1aeab
Exists in colab

[Colab] RemoteUser acceptance test modified accordingly to the actual behaviour …

…of Rack, Warden and omniauth-remote-user
features/step_definitions/user_steps.rb
... ... @@ -41,8 +41,6 @@ Given(/^I am logged in as a Colab user$/) do
41 41 'name': colab_user.name,
42 42 'email': colab_user.email
43 43 }.to_json)
44   -
45   - visit(user_omniauth_authorize_path(provider: 'RemoteUser')) # Authenticate the user (remove this if you want just to set the headers)
46 44 end
47 45  
48 46 Then(/^I should be at the Home page$/) do
... ...
features/users/omniauth.feature
... ... @@ -3,13 +3,7 @@ Feature: Omniauth authentication
3 3 As a regular user
4 4 I want to authenticate with an external provider
5 5  
6   - #FIXME: For some reason. just for cucumber tests, if you set the HTTP headers, it ignores all the path you visit and goes straight to the omniauth controller action
7   - @javascript
8 6 Scenario: through Colab
9 7 Given I am logged in as a Colab user
10   - #And I am at the homepage
11   - #And I take a picture of the page
12   - #And I click the Sign In link
13   - #When I click the Sign in with Remote User link
14   - Then I should be at the Home page
15   - And I should be logged in
16 8 \ No newline at end of file
  9 + Given I am at the homepage
  10 + And I should be logged in
... ...