Identity/DDT Smoke Test

From MozillaWiki
Jump to: navigation, search

This document is taken from content on QA BrowserID TestPlan - https://wiki.mozilla.org/QA/BrowserID/TestPlan

Purpose

As BrowserID grows and the product becomes increasingly complex, it is a difficult task to introduce new features without also introducing bugs. To help reduce the number of bugs that make it to prod as well as to ease some of the pain on our own QA team, we are introducing a WWE move - the DDT. DDT (developer driven testing) is like jumping off the top rope to smash bugs before they have a chance to cause pain.

QA has a well defined set of tests they perform before qualifying any release as "ready for production." We are going to use a very slimmed down version of the Sanity/Acceptance/Smoke tests.

Tests should be performed against both dev and staging. 123done.org will be the RP of choice once it is set up to handle all environments. 123done.org currently only supports staging. Until 123done.org is ready, testing will take place using myfavoritebeer.org as the RP.

dev: http://dev.myfavoritebeer.org/ staging: http://beta.myfavoritebeer.org/

Basic Developer Driven Tests

Dialog

  • Create a "secondary" address based account.
    • Create a new account using a "secondary" email address.
    • Add a secondary address to the account.
    • Add a primary address to the account.
    • Log out and sign back in using both primary and secondary addresses.
  • Forgot Password
    • Sign out of dialog, enter known secondary address, and click "forgot password". User needs to enter new password and verify email. No other emails are associated with account.
  • Create a "primary" address based account.
    • Create a new account using a "primary" email address.
    • Add a different primary address
    • Add a "secondary" address - user is required to set password.
    • Log out and sign back in using both primary and secondary addresses.
  • Assertion/Password Authentication Levels.
    • Sign out of dialog, enter known "primary" address. Verify with IdP if needed. Open dialog again, select "secondary" address. User should now have to enter password.

Main Site

  • All Pages
    • Check formatting
  • Sign Up/Sign In/Forgot Password
    • Sign up using a "secondary" address.
    • Sign in using a "secondary" address.
    • Forgot password for a "secondary" address.
    • Sign up using a "primary" address.
    • Sign in using a "primary" address.
    • Sign Out
  • Management page
    • Remove Address
    • Change password
    • Remove Account