Confirmed users
3,727
edits
QA/BrowserID/TestPlan: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 121: | Line 121: | ||
* Different accounts using same email/password combos | * Different accounts using same email/password combos | ||
* Shared access to same computer or profiles or accounts | * Shared access to same computer or profiles or accounts | ||
* Browser settings and preferences, esp. pop-ups, security, privacy | |||
* FireFox about:config, similar, if any, for other browsers | |||
== UI == | == UI == | ||
| Line 157: | Line 160: | ||
** A logout link: http://myfavoritebeer.org/ | ** A logout link: http://myfavoritebeer.org/ | ||
* Add new emails while still logged into client | * Add new emails while still logged into client | ||
* Logout links on server side (if they exist) | |||
* Various UI scenarios and walkthroughs not covered above... | * Various UI scenarios and walkthroughs not covered above... | ||
* General ease of use | * General ease of use | ||
| Line 164: | Line 168: | ||
Ideally, this would be in the form of a quick automated test/script to check key fixes/changes/updates. | Ideally, this would be in the form of a quick automated test/script to check key fixes/changes/updates. | ||
QA to work with Dev and PM to come up with a list of bugs/issues candidates to from the test cases for manual and automated testing. | QA to work with Dev and PM to come up with a list of bugs/issues candidates to from the test cases for manual and automated testing. | ||
REF: https://github.com/mozilla/browserid/issues | |||
REF: https://github.com/mozilla/browserid/issues/milestones | |||
== OS/Browser integration == | == OS/Browser integration == | ||
| Line 173: | Line 179: | ||
* Browser preferences, esp for privacy/security | * Browser preferences, esp for privacy/security | ||
* Browser synchronization - same platform, across platforms | * Browser synchronization - same platform, across platforms | ||
== Mobile Testing == | |||
Milestone is completed, so some Mobile specific tests should be added: TBD | |||
Sanity/Acceptance | |||
Functional/UI | |||
OS/Browser | |||
== Client-side Testing == | == Client-side Testing == | ||
| Line 189: | Line 201: | ||
* 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 | ||
** Users: https://browserid.org/users, as in https://browserid.org/users/<insert_mail_adress_registered>.xml | |||
** https://browserid.org/verify | |||
* Log inspection to verify accurate information | * Log inspection to verify accurate information | ||
** Verify content of web server access logs | ** Verify content of web server access logs | ||
| Line 210: | Line 224: | ||
QA could use some help from Dev and PM on testable use cases. | QA could use some help from Dev and PM on testable use cases. | ||
Valid/invalid public key | Valid/invalid public key | ||
Tracking public and private key usage | |||
Security/Crypto checks | Security/Crypto checks | ||
Damaged/Stolen/Compromised accounts, emails, keys | |||
Testing validity period for specific certificates | |||
Snooping email providers | |||
REF: | REF: | ||
https://wiki.mozilla.org/Identity/Verified_Email_Protocol (is this the more current link?) | https://wiki.mozilla.org/Identity/Verified_Email_Protocol (is this the more current link?) | ||
https://wiki.mozilla.org/Labs/Identity/VerifiedEmailProtocol | https://wiki.mozilla.org/Labs/Identity/VerifiedEmailProtocol | ||
https://wiki.mozilla.org/Security/Reviews/Identity/browserid | |||
== Flows/End-To-End == | == Flows/End-To-End == | ||
| Line 245: | Line 264: | ||
* Do we have other tested (re: reliable) methods for creating test/dummy email accounts? | * Do we have other tested (re: reliable) methods for creating test/dummy email accounts? | ||
= Open Questions/Issues = | |||
= Open Questions/Issues for QA, Dev, and PM = | |||
# How do we verify this statement: "Unlike other sign-in systems, BrowserID does not leak information back to any server (not even to the BrowserID servers) about which sites a user visits." Could use some help from Dev and PM on testable use cases. | # How do we verify this statement: "Unlike other sign-in systems, BrowserID does not leak information back to any server (not even to the BrowserID servers) about which sites a user visits." Could use some help from Dev and PM on testable use cases. | ||
# How does this site/technology fit in? Or is it not applicable to our weekly testing? | # How does this site/technology fit in? Or is it not applicable to our weekly testing? | ||