Skip to content

Commit

Permalink
chore: enable OV sign in flow test
Browse files Browse the repository at this point in the history
OKTA-509199
<<<Jenkins Check-In of Tested SHA: 0ca5d66 for [email protected]>>>
Artifact: okta-auth-js
Files changed count: 2
PR Link: #1250
  • Loading branch information
oleksandrpravosudko-okta authored and eng-prod-CI-bot-okta committed Jul 4, 2022
1 parent 3b0a43e commit 8c25774
Show file tree
Hide file tree
Showing 2 changed files with 43 additions and 42 deletions.
80 changes: 39 additions & 41 deletions samples/test/features/totp-okta-verify-signin.feature
Original file line number Diff line number Diff line change
Expand Up @@ -31,56 +31,54 @@ Feature: TOTP Support (Okta Verify) Sign In
# And the cell for the value of "email" is shown and contains her "email"
# And the cell for the value of "name" is shown and contains her "first name and last name"

# TODO - Enable after OKTA-509199 is fixed
# Scenario: Mary signs in to an account and enrolls in Password and Okta Verify by clicking a link in a text message
# When she clicks the "login" button
# Then she is redirected to the "Login" page
# When she has inserted her username
# And she has inserted her password
# And her password is correct
# When she submits the form
# Then she is redirected to the "Select Authenticator" page
# When she selects the "Okta Verify" factor
# And she submits the form
# Then she is redirected to the "Enroll Okta Verify" page
# And she sees a QR Code on the screen
# And she selects "Enroll with another method"
# When she selects the "SMS" enrollment method
# And she submits the form
# When she inputs a valid phone number for Okta Verify
# And she submits the form
# Then the screen changes to a waiting screen saying "We sent an SMS to {phone_number} with an Okta Verify setup link. To continue, open the link on your mobile device."
# Then she receives a "SMS" with a link to enroll in Okta Verify
Scenario: Mary signs in to an account and enrolls in Password and Okta Verify by clicking a link in a text message
When she clicks the "login" button
Then she is redirected to the "Login" page
When she has inserted her username
And she has inserted her password
And her password is correct
When she submits the form
Then she is redirected to the "Select Authenticator" page
When she selects the "Okta Verify" factor
And she submits the form
Then she is redirected to the "Enroll Okta Verify" page
And she sees a QR Code on the screen
And she selects "Enroll with another method"
When she selects the "SMS" enrollment method
And she submits the form
When she inputs a valid phone number for Okta Verify
And she submits the form
Then the screen changes to a waiting screen saying "We sent an SMS to {phone_number} with an Okta Verify setup link. To continue, open the link on your mobile device."
Then she receives a "SMS" with a link to enroll in Okta Verify
## Steps below can't be automated without device push support
# When she clicks the link in her text message from her phone
# Then she is redirected to the "Root" page
# And she sees a table with her profile info
# And the cell for the value of "email" is shown and contains her "email"
# And the cell for the value of "name" is shown and contains her "first name and last name"

# TODO - Enable after OKTA-509199 is fixed
# Scenario: Mary signs in to an account and enrolls in Password and Okta Verify by clicking a link in a text message
# When she clicks the "login" button
# Then she is redirected to the "Login" page
# When she has inserted her username
# And she has inserted her password
# And her password is correct
# When she submits the form
# Then she is redirected to the "Select Authenticator" page
# When she selects the "Okta Verify" factor
# And she submits the form
# Then she is redirected to the "Enroll Okta Verify" page
# And she sees a QR Code on the screen
# And she selects "Enroll with another method"
# When she selects the "Email" enrollment method
# And she submits the form
# When she inputs a valid email for Okta Verify
# And she submits the form
# Then she receives a "Email" with a link to enroll in Okta Verify
# Then the screen changes to a waiting screen saying "We sent an Email to {email_address} with an Okta Verify setup link. To continue, open the link in your email."
Scenario: Mary signs in to an account and enrolls in Password and Okta Verify by clicking a link in a text message
When she clicks the "login" button
Then she is redirected to the "Login" page
When she has inserted her username
And she has inserted her password
And her password is correct
When she submits the form
Then she is redirected to the "Select Authenticator" page
When she selects the "Okta Verify" factor
And she submits the form
Then she is redirected to the "Enroll Okta Verify" page
And she sees a QR Code on the screen
And she selects "Enroll with another method"
When she selects the "Email" enrollment method
And she submits the form
When she inputs a valid email for Okta Verify
And she submits the form
Then she receives a "Email" with a link to enroll in Okta Verify
Then the screen changes to a waiting screen saying "We sent an Email to {email_address} with an Okta Verify setup link. To continue, open the link in your email."
## Steps below can't be automated without device push support
# When she clicks the link in her email
# Then she is redirected to the "Root" page
# And she sees a table with her profile info
# And the cell for the value of "email" is shown and contains her "email"
# And the cell for the value of "name" is shown and contains her "first name and last name"
# And the cell for the value of "name" is shown and contains her "first name and last name"
5 changes: 4 additions & 1 deletion samples/test/steps/then.ts
Original file line number Diff line number Diff line change
Expand Up @@ -354,7 +354,10 @@ Then(
} else if (type === 'Email') {
enrollLink = await this.a18nClient.getOktaVerifyEnrollLinkFromEmail(this.credentials.profileId);
}
expect(enrollLink).toContain('/auth/push/link');
const currentUrl = await browser.getUrl();
await browser.url(enrollLink);
expect(await browser.getUrl()).toContain('/auth/push/link');
await browser.url(currentUrl);
}
);

Expand Down

0 comments on commit 8c25774

Please sign in to comment.