silverstripe-framework/tests/behat/features/login.feature

@retry
Feature: Log in
  As an site owner
  I want to access to the CMS to be secure
  So that only my team can make content changes

  Scenario: Bad login
    Given I log in with "bad@example.com" and "badpassword"
    Then I should see "The provided details don't seem to be correct"

  Scenario: Valid login
    Given I am logged in with "ADMIN" permissions
    When I go to "/admin/"
    Then I should see the CMS

  Scenario: /admin/ redirect for not logged in user
    # disable automatic redirection so we can use the profiler
    When I go to "/admin/"
    And I should see a log-in form

  Scenario: Logout without token
    Given I am logged in with "ADMIN" permissions
    When I go to "/Security/logout"
    Then I should see a log-out form
    When I press the "Log out" button
    And I go to "/admin/"
    Then I should see a log-in form

  Scenario: Log in as someone else
    Given I am logged in with "ADMIN" permissions
    When I go to "/Security/login"
    Then the response should contain "Log in as someone else"

    When I press the "Log in as someone else" button
    Then I should see a log-in form
API Move createTag to HTML class ENHANCEMENT Better HTML generation behaviour for Requirements_Backend 2017-04-18 00:34:18 +02:00			`@retry`
NEW Support for Behat tests, and initial set of tests 2012-11-09 19:16:16 +01:00			`Feature: Log in`
			`As an site owner`
			`I want to access to the CMS to be secure`
			`So that only my team can make content changes`

			`Scenario: Bad login`
			`Given I log in with "bad@example.com" and "badpassword"`
Feedback from Damian. - Move the success and message to a validationresult - Fix tests for validationresult return - We need to clear the session in Test logOut method - Rename to MemberAuthenticator and CMSMemberAuthenticator for consistency. - Unify all to getCurrentUser on Security - ChangePasswordHandler removed from Security - Update SapphireTest for CMS login/logout - Get the Member ID correctly, if it's an object. - Only enable "remember me" when it's allowed. - Add flag to disable password logging - Remove Subsites coupling, give it an extension hook to disable itself - Change cascadeLogInTo to cascadeInTo for the logout method logic naming - Docblocks - Basicauth config 2017-05-30 09:42:00 +02:00			`Then I should see "The provided details don't seem to be correct"`
NEW Support for Behat tests, and initial set of tests 2012-11-09 19:16:16 +01:00
			`Scenario: Valid login`
			`Given I am logged in with "ADMIN" permissions`
			`When I go to "/admin/"`
			`Then I should see the CMS`

			`Scenario: /admin/ redirect for not logged in user`
			`# disable automatic redirection so we can use the profiler`
API Upgrade to behat 3 2017-01-20 03:57:50 +01:00			`When I go to "/admin/"`
Fixing undefined step caused by change in behat-extensio module. 2013-11-29 02:17:04 +01:00			`And I should see a log-in form`
NEW: Add CSRF token to logout action 2017-06-15 12:54:41 +02:00
			`Scenario: Logout without token`
			`Given I am logged in with "ADMIN" permissions`
			`When I go to "/Security/logout"`
			`Then I should see a log-out form`
			`When I press the "Log out" button`
			`And I go to "/admin/"`
			`Then I should see a log-in form`
FIX Log in as someone else returns user back to login screen 2017-07-18 07:15:58 +02:00
			`Scenario: Log in as someone else`
			`Given I am logged in with "ADMIN" permissions`
			`When I go to "/Security/login"`
			`Then the response should contain "Log in as someone else"`

			`When I press the "Log in as someone else" button`
			`Then I should see a log-in form`