microsoft-authentication-library-for-android icon indicating copy to clipboard operation
microsoft-authentication-library-for-android copied to clipboard

First batch of Native Auth E2E tests

Open Yuki-YuXin opened this issue 1 year ago • 0 comments

Has a dependency on the configuration parameters work

Company PR: https://github.com/AzureAD/microsoft-authentication-library-common-for-android/pull/2438 The previous E2E test PR for sign in cases https://github.com/AzureAD/microsoft-authentication-library-for-android/pull/2123

SignIn username + code:

  • User is not registered with given email (use case 2.2.2) - Test case 31 ✔
  • Invalid OTP (use case 2.2.7) - Test case 35 ✔
  • Use email and OTP to get token and sign in (hero scenario 6, use case 2.2.1) - Test case 30 ✔

SignIn username + password:

  • Password is incorrect (1.2.3) - Test case 39 ✔
  • Use email and password to get token (hero scenario 15, use case 1.2.1) - test case 37 ✔
  • User is not registered with given email (use case 1.2.2) - test case 38 ✔

SignUp username + code:

  • Verify email address using email OTP and sign up (hero scenario 1, use case 2.1.1) - Test case 1 ✔
  • Signup user with custom attributes with verify OTP as last step (hero scenario 2, use case 2.1.2) - Test case 2 ✔
  • Verify email OTP first and then collect custom attributes (hero scenario 3, use case 2.1.3) - Test case 3 ✔
  • Verify email OTP first and then collect custom attributes on multiple screens (hero scenario 4, use case 2.1.4) - Test case 4 ✔

SignUp username + password:

  • Set email and password and then verify email OOB as last step (hero scenario 9, use case 1.1.1) - Test case 13 ✔
  • Sign up user with custom attributes and verify email as last step (hero scenario 10, use case 1.1.3) - Test case 15 ✔
  • Verify email address using email OTP and then set password (use case 1.1.4) - Test case 16 ✔
  • Sign up with verify email OOB as first step, then set password & custom attributes at end (hero scenario 12, use case 1.1.6) - Test case 28 ✔
  • Sign up with verify email OOB as first step, then set password & custom attributes at end over multiple screens/API calls (hero scenario 13) - Test case 29 ✔

SSPR:

  • Verify email with email OTP first and then reset password (hero scenario 8 & 17, use case 3.1.1) - Test case 46 ✔

Yuki-YuXin avatar Jun 14 '24 10:06 Yuki-YuXin