Confirmed users
3,727
edits
QA/BrowserID/TestPlan: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 117: | Line 117: | ||
* Browser restart after creation of identity | * Browser restart after creation of identity | ||
* Always logging out from sites vs. never logging out from sites | * Always logging out from sites vs. never logging out from sites | ||
* Email and Password character compatibility | |||
* Valid vs. invalid email formats | |||
* Different accounts using same email/password combos | |||
* Shared access to same computer or profiles or accounts | |||
== UI == | == UI == | ||
| Line 126: | Line 130: | ||
* Add a new email address | * Add a new email address | ||
* This is not me | * This is not me | ||
* Stay logged in vs. always log out | * Stay logged in vs. always log out | ||
* Account management: https://www.browserid.org/manage | * Account management: https://www.browserid.org/manage | ||
| Line 155: | Line 158: | ||
* Add new emails while still logged into client | * Add new emails while still logged into client | ||
* Various UI scenarios and walkthroughs not covered above... | * Various UI scenarios and walkthroughs not covered above... | ||
* General ease of use | |||
== Bug Regression == | == Bug Regression == | ||
| Line 171: | Line 175: | ||
== Client-side Testing == | == Client-side Testing == | ||
FireFox example: | QA will need the local storage information per browser in order to verify accurate creation/update/use/removal of BrowserID data. | ||
Possible FireFox example: | |||
Users > USER-NAME > Library > Application Support > Firefox > Profiles > PROFILE.default | Users > USER-NAME > Library > Application Support > Firefox > Profiles > PROFILE.default | ||
Where is the local storage for BrowserID? | Where is the local storage for BrowserID? | ||
| Line 181: | Line 186: | ||
== Server-side Testing == | == Server-side Testing == | ||
Need the list of server and services or components that describe the BrowserID architecture to accurately focus on server-side testing. | |||
* Verify some UI elements and actions only found on the server: | * Verify some UI elements and actions only found on the server: | ||
** Manage Accounts page: https://www.browserid.org/manage | ** Manage Accounts page: https://www.browserid.org/manage | ||
| Line 188: | Line 194: | ||
** Verify content of BrowserID logs | ** Verify content of BrowserID logs | ||
* What other server-specific tests are required? | * What other server-specific tests are required? | ||
* See also the Areas Not Covered section below for security and end-to-end (flows). | |||
* | |||
| Line 228: | Line 229: | ||
For Firefox users with the addon, the addon flow needs tested. | For Firefox users with the addon, the addon flow needs tested. | ||
Test design: TBD | Test design: TBD | ||
== Internationalization, Localization == | |||
Localization (L10n) | |||
Internationalization (i10n) | |||
| Line 244: | Line 249: | ||
2. How does this site/technology fit in? Or is it not applicable to our weekly testing? | 2. How does this site/technology fit in? Or is it not applicable to our weekly testing? | ||
http://people.mozilla.com/~faaborg/files/projects/firefoxAccount/index.html | http://people.mozilla.com/~faaborg/files/projects/firefoxAccount/index.html | ||
3. Is there any benefit to testing/comparing BrowserID with OpenID or any other ID mechanism? | |||
4. Where is local storage for BrowserID? What data is stored per browser/profile/account/user? | |||
5. What is the best way to approach security and privacy testing? Through the UI? through the API? Or, by setting up some unsecure environment or hackable instance? | |||
6. Is it possible to have multiple accounts referencing the same email(s)? | |||
7. What about multiple accounts per user (for work/prof/public emails vs. private/personal emails)? | |||
8. Do we need to test/verify deviations from the standard VEC? | |||