https://wiki.mozilla.org/api.php?action=feedcontributions&user=Teodora.Vermesan&feedformat=atomMozillaWiki - User contributions [en]2024-03-29T13:37:02ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150317QA/IAM/TestPlan2016-10-05T15:16:13Z<p>Teodora.Vermesan: adding results</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post to:<br />
**email List: parsys@mozilla.com<br />
**Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
**IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch) - owns Community Analytics and Volunteer Management Systems<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and owns infrastructure fortification<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team and owns the IAM packages B and C<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians and owns technical debt reduction<br />
**Yousef Alam(:yalam96) - owns Participation Infrastructure<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
==Supported OS and Browsers==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*different mobile devices<br />
==OS/Browser integration==<br />
==Desktop==<br />
*Verify compatibility/stability/functionality across different OS and browsers<br />
**smoke/sanity/acceptance section<br />
**Basic Functional and UI tests<br />
**Click, zoom, scroll, multi-window<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
==Mobile==<br />
*Berify compatibility/stability/functionality across Android and iOS tablets and phones<br />
**smoke/sanity/acceptance section on phone/tablet<br />
**Basic Functional and UI tests on phone/tablet<br />
**Panning, zooming, scrolling, tab access and flow between tabs<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
<br />
==Network/Internet==<br />
*Verify the impact of various ways to access the internet: timing, communication, messaging, outages, errors, traffic<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
<br />
=Major Areas Focus=<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
===UI===<br />
*Sign Up:<br />
**'SIGN UP' button<br />
**'Email' field<br />
**'Password' field<br />
**'Submit' and 'Cancel'(x) buttons<br />
**'SIGN UP WITH other apps' option<br />
*Confirm your Email UI<br />
**verifying accurate "prove" link<br />
**confirm email verification from client-side and server-side<br />
*Login:<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**'Login with other apps' option is present<br />
*Logout<br />
**'Log out' button<br />
===Full Functional===<br />
*Sign Up:<br />
**Verify that clicking submit button after entering all the required fields, submits the data<br />
**Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
**Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
**Verify that sign up with other apps works as expected<br />
**Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
**Verify sign-up with:<br />
***valid email, invalid password<br />
***valid email, valid password<br />
***invalid email, invalid password <br />
***invalid email, valid password<br />
**Verify email strings and all legal combinations of characters<br />
**Copy/Pasting emails from other sources<br />
**Auto-completion of emails<br />
**Verify minimum/maximum sizes of emails (length)<br />
**Verify password strings and all legal combinations of characters<br />
**Copy/Pasting passwords from other sources<br />
**Verify minimum/maximum sizes of passwords (length)<br />
**Verify that passwords are stored if "remember password" option is chosen<br />
**Verify that passwords are not stored if "never remember password" option is chosen <br />
**Verify browser restart after creation of account or access of an account<br />
*Login<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
***Verify email strings and all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
***Verify password strings and ll legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress<br />
<br />
==Localization==<br />
*Verify the UI flow with specific focus on localization, all text-based content <br />
*Quick verification of localized headers <br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases should be executed<br />
**All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150307QA/IAM/TestPlan2016-10-05T14:59:48Z<p>Teodora.Vermesan: adding results</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch) - owns Community Analytics and Volunteer Management Systems<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and owns infrastructure fortification<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team and owns the IAM packages B and C<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians and owns technical debt reduction<br />
**Yousef Alam(:yalam96) - owns Participation Infrastructure<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*different mobile devices<br />
==OS/Browser integration==<br />
==Desktop==<br />
*Verify compatibility/stability/functionality across different OS and browsers<br />
**smoke/sanity/acceptance section<br />
**Basic Functional and UI tests<br />
**Click, zoom, scroll, multi-window<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
==Mobile==<br />
*Berify compatibility/stability/functionality across Android and iOS tablets and phones<br />
**smoke/sanity/acceptance section on phone/tablet<br />
**Basic Functional and UI tests on phone/tablet<br />
**Panning, zooming, scrolling, tab access and flow between tabs<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
<br />
==Network/Internet==<br />
*Verify the impact of various ways to access the internet: timing, communication, messaging, outages, errors, traffic<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
<br />
=Major Areas Focus=<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
===UI===<br />
*Sign Up:<br />
**'SIGN UP' button<br />
**'Email' field<br />
**'Password' field<br />
**'Submit' and 'Cancel'(x) buttons<br />
**'SIGN UP WITH other apps' option<br />
*Confirm your Email UI<br />
**verifying accurate "prove" link<br />
**confirm email verification from client-side and server-side<br />
*Login:<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**'Login with other apps' option is present<br />
*Logout<br />
**'Log out' button<br />
===Full Functional===<br />
*Sign Up:<br />
**Verify that clicking submit button after entering all the required fields, submits the data<br />
**Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
**Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
**Verify that sign up with other apps works as expected<br />
**Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
**Verify sign-up with:<br />
***valid email, invalid password<br />
***valid email, valid password<br />
***invalid email, invalid password <br />
***invalid email, valid password<br />
**Verify email strings and all legal combinations of characters<br />
**Copy/Pasting emails from other sources<br />
**Auto-completion of emails<br />
**Verify minimum/maximum sizes of emails (length)<br />
**Verify password strings and all legal combinations of characters<br />
**Copy/Pasting passwords from other sources<br />
**Verify minimum/maximum sizes of passwords (length)<br />
**Verify that passwords are stored if "remember password" option is chosen<br />
**Verify that passwords are not stored if "never remember password" option is chosen <br />
**Verify browser restart after creation of account or access of an account<br />
*Login<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
***Verify email strings and all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
***Verify password strings and ll legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress<br />
<br />
==Localization==<br />
*Verify the UI flow with specific focus on localization, all text-based content <br />
*Quick verification of localized headers <br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases should be executed<br />
**All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150306QA/IAM/TestPlan2016-10-05T14:42:44Z<p>Teodora.Vermesan: /* Non-Functional testing */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch) - owns Community Analytics and Volunteer Management Systems<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and owns infrastructure fortification<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team and owns the IAM packages B and C<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians and owns technical debt reduction<br />
**Yousef Alam(:yalam96) - owns Participation Infrastructure<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
==OS/Browser integration==<br />
==Desktop==<br />
*Desktop-specific tests should be added to verify compatibility/stability/functionality across different OS and browsers<br />
*Verify access and use (account creation/update/deletion, password reset etc) on:<br />
**browsers on same OS, different OS<br />
**across OS platforms, same browser, different browser<br />
<br />
==Mobile Testing==<br />
*Mobile-specific tests should be added to verify compatibility/stability/functionality across Android and iOS tablets and phones<br />
**smoke/sanity/acceptance section on phone/tablet<br />
**Basic Functional and UI tests on phone/tablet<br />
**Panning, zooming, scrolling, tab access and flow between tabs<br />
**OS/Browser interaction using Firefox and stock browser on Android phones and tablets<br />
**OS/Browser interaction using Safari browser on iPhones and iPads<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
**Verify compatibility and functionality when working with Android/iOS Settings and with browser app-specific settings.<br />
<br />
==Network/Internet==<br />
*Verify the impact of various ways to access the internet: timing, communication, messaging, outages, errors, traffic<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
<br />
=Major Areas Focus=<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
===UI===<br />
*Sign Up:<br />
**'SIGN UP' button<br />
**'Email' field<br />
**'Password' field<br />
**'Submit' and 'Cancel'(x) buttons<br />
**'SIGN UP WITH other apps' option<br />
*Login:<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**'Login with other apps' option is present<br />
*Logout<br />
**'Log out' button<br />
===Full Functional===<br />
*Sign Up:<br />
**Verify that clicking submit button after entering all the required fields, submits the data<br />
**Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
**Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
**Verify that sign up with other apps works as expected<br />
**Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
**Verify sign-up with:<br />
***valid email, invalid password<br />
***valid email, valid password<br />
***invalid email, invalid password <br />
***invalid email, valid password<br />
**Verify email strings and all legal combinations of characters<br />
**Copy/Pasting emails from other sources<br />
**Auto-completion of emails<br />
**Verify minimum/maximum sizes of emails (length)<br />
**Verify password strings and ll legal combinations of characters<br />
**Copy/Pasting passwords from other sources<br />
**Verify minimum/maximum sizes of passwords (length)<br />
**Verify that passwords are stored if "remember password" option is chosen<br />
**Verify that passwords are not stored if "never remember password" option is chosen <br />
*Login<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
***Verify email strings and all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
***Verify password strings and ll legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress<br />
<br />
==Localization==<br />
*Verify the UI flow with specific focus on localization, all text-based content <br />
*Quick verification of localized headers <br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases should be executed<br />
**All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150305QA/IAM/TestPlan2016-10-05T14:39:34Z<p>Teodora.Vermesan: /* Exit criteria */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch) - owns Community Analytics and Volunteer Management Systems<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and owns infrastructure fortification<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team and owns the IAM packages B and C<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians and owns technical debt reduction<br />
**Yousef Alam(:yalam96) - owns Participation Infrastructure<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
==OS/Browser integration==<br />
==Desktop==<br />
*Desktop-specific tests should be added to verify compatibility/stability/functionality across different OS and browsers<br />
*Verify access and use (account creation/update/deletion, password reset etc) on:<br />
**browsers on same OS, different OS<br />
**across OS platforms, same browser, different browser<br />
<br />
==Mobile Testing==<br />
*Mobile-specific tests should be added to verify compatibility/stability/functionality across Android and iOS tablets and phones<br />
**smoke/sanity/acceptance section on phone/tablet<br />
**Basic Functional and UI tests on phone/tablet<br />
**Panning, zooming, scrolling, tab access and flow between tabs<br />
**OS/Browser interaction using Firefox and stock browser on Android phones and tablets<br />
**OS/Browser interaction using Safari browser on iPhones and iPads<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
**Verify compatibility and functionality when working with Android/iOS Settings and with browser app-specific settings.<br />
<br />
==Network/Internet==<br />
*Verify the impact of various ways to access the internet: timing, communication, messaging, outages, errors, traffic<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
<br />
=Major Areas Focus=<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
===UI===<br />
*Sign Up:<br />
**'SIGN UP' button<br />
**'Email' field<br />
**'Password' field<br />
**'Submit' and 'Cancel'(x) buttons<br />
**'SIGN UP WITH other apps' option<br />
*Login:<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**'Login with other apps' option is present<br />
*Logout<br />
**'Log out' button<br />
===Full Functional===<br />
*Sign Up:<br />
**Verify that clicking submit button after entering all the required fields, submits the data<br />
**Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
**Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
**Verify that sign up with other apps works as expected<br />
**Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
**Verify sign-up with:<br />
***valid email, invalid password<br />
***valid email, valid password<br />
***invalid email, invalid password <br />
***invalid email, valid password<br />
**Verify email strings and all legal combinations of characters<br />
**Copy/Pasting emails from other sources<br />
**Auto-completion of emails<br />
**Verify minimum/maximum sizes of emails (length)<br />
**Verify password strings and ll legal combinations of characters<br />
**Copy/Pasting passwords from other sources<br />
**Verify minimum/maximum sizes of passwords (length)<br />
**Verify that passwords are stored if "remember password" option is chosen<br />
**Verify that passwords are not stored if "never remember password" option is chosen <br />
*Login<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
***Verify email strings and all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
***Verify password strings and ll legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
==Localization==<br />
*Verify the UI flow with specific focus on localization, all text-based content <br />
*Quick verification of localized headers <br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases should be executed<br />
**All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150304QA/IAM/TestPlan2016-10-05T14:37:22Z<p>Teodora.Vermesan: /* OS/Browser integration */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch) - owns Community Analytics and Volunteer Management Systems<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and owns infrastructure fortification<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team and owns the IAM packages B and C<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians and owns technical debt reduction<br />
**Yousef Alam(:yalam96) - owns Participation Infrastructure<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
==OS/Browser integration==<br />
==Desktop==<br />
*Desktop-specific tests should be added to verify compatibility/stability/functionality across different OS and browsers<br />
*Verify access and use (account creation/update/deletion, password reset etc) on:<br />
**browsers on same OS, different OS<br />
**across OS platforms, same browser, different browser<br />
<br />
==Mobile Testing==<br />
*Mobile-specific tests should be added to verify compatibility/stability/functionality across Android and iOS tablets and phones<br />
**smoke/sanity/acceptance section on phone/tablet<br />
**Basic Functional and UI tests on phone/tablet<br />
**Panning, zooming, scrolling, tab access and flow between tabs<br />
**OS/Browser interaction using Firefox and stock browser on Android phones and tablets<br />
**OS/Browser interaction using Safari browser on iPhones and iPads<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
**Verify compatibility and functionality when working with Android/iOS Settings and with browser app-specific settings.<br />
<br />
==Network/Internet==<br />
*Verify the impact of various ways to access the internet: timing, communication, messaging, outages, errors, traffic<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
<br />
=Major Areas Focus=<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
===UI===<br />
*Sign Up:<br />
**'SIGN UP' button<br />
**'Email' field<br />
**'Password' field<br />
**'Submit' and 'Cancel'(x) buttons<br />
**'SIGN UP WITH other apps' option<br />
*Login:<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**'Login with other apps' option is present<br />
*Logout<br />
**'Log out' button<br />
===Full Functional===<br />
*Sign Up:<br />
**Verify that clicking submit button after entering all the required fields, submits the data<br />
**Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
**Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
**Verify that sign up with other apps works as expected<br />
**Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
**Verify sign-up with:<br />
***valid email, invalid password<br />
***valid email, valid password<br />
***invalid email, invalid password <br />
***invalid email, valid password<br />
**Verify email strings and all legal combinations of characters<br />
**Copy/Pasting emails from other sources<br />
**Auto-completion of emails<br />
**Verify minimum/maximum sizes of emails (length)<br />
**Verify password strings and ll legal combinations of characters<br />
**Copy/Pasting passwords from other sources<br />
**Verify minimum/maximum sizes of passwords (length)<br />
**Verify that passwords are stored if "remember password" option is chosen<br />
**Verify that passwords are not stored if "never remember password" option is chosen <br />
*Login<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
***Verify email strings and all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
***Verify password strings and ll legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
==Localization==<br />
*Verify the UI flow with specific focus on localization, all text-based content <br />
*Quick verification of localized headers <br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150303QA/IAM/TestPlan2016-10-05T14:34:47Z<p>Teodora.Vermesan: /* Network/Internet */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch) - owns Community Analytics and Volunteer Management Systems<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and owns infrastructure fortification<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team and owns the IAM packages B and C<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians and owns technical debt reduction<br />
**Yousef Alam(:yalam96) - owns Participation Infrastructure<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
==OS/Browser integration==<br />
*Verify access and use across browsers on same OS, different OS<br />
*Verify access and use across OS platforms, same browser, different browser<br />
*Browser preferences, esp for privacy/security<br />
*Browser synchronization - same platform, across platforms<br />
*Verify door hanger information (per browser, desktop and mobile)<br />
==Mobile Testing==<br />
*Mobile-specific tests should be added to verify compatibility/stability/functionality across Android and iOS tablets and phones<br />
**smoke/sanity/acceptance section on phone/tablet<br />
**Basic Functional and UI tests on phone/tablet<br />
**Panning, zooming, scrolling, tab access and flow between tabs<br />
**OS/Browser interaction using Firefox and stock browser on Android phones and tablets<br />
**OS/Browser interaction using Safari browser on iPhones and iPads<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
**Verify compatibility and functionality when working with Android/iOS Settings and with browser app-specific settings.<br />
<br />
==Network/Internet==<br />
*Verify the impact of various ways to access the internet: timing, communication, messaging, outages, errors, traffic<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
<br />
=Major Areas Focus=<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
===UI===<br />
*Sign Up:<br />
**'SIGN UP' button<br />
**'Email' field<br />
**'Password' field<br />
**'Submit' and 'Cancel'(x) buttons<br />
**'SIGN UP WITH other apps' option<br />
*Login:<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**'Login with other apps' option is present<br />
*Logout<br />
**'Log out' button<br />
===Full Functional===<br />
*Sign Up:<br />
**Verify that clicking submit button after entering all the required fields, submits the data<br />
**Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
**Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
**Verify that sign up with other apps works as expected<br />
**Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
**Verify sign-up with:<br />
***valid email, invalid password<br />
***valid email, valid password<br />
***invalid email, invalid password <br />
***invalid email, valid password<br />
**Verify email strings and all legal combinations of characters<br />
**Copy/Pasting emails from other sources<br />
**Auto-completion of emails<br />
**Verify minimum/maximum sizes of emails (length)<br />
**Verify password strings and ll legal combinations of characters<br />
**Copy/Pasting passwords from other sources<br />
**Verify minimum/maximum sizes of passwords (length)<br />
**Verify that passwords are stored if "remember password" option is chosen<br />
**Verify that passwords are not stored if "never remember password" option is chosen <br />
*Login<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
***Verify email strings and all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
***Verify password strings and ll legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
==Localization==<br />
*Verify the UI flow with specific focus on localization, all text-based content <br />
*Quick verification of localized headers <br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150302QA/IAM/TestPlan2016-10-05T14:31:01Z<p>Teodora.Vermesan: /* Mobile Testing */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch) - owns Community Analytics and Volunteer Management Systems<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and owns infrastructure fortification<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team and owns the IAM packages B and C<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians and owns technical debt reduction<br />
**Yousef Alam(:yalam96) - owns Participation Infrastructure<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
==OS/Browser integration==<br />
*Verify access and use across browsers on same OS, different OS<br />
*Verify access and use across OS platforms, same browser, different browser<br />
*Browser preferences, esp for privacy/security<br />
*Browser synchronization - same platform, across platforms<br />
*Verify door hanger information (per browser, desktop and mobile)<br />
==Mobile Testing==<br />
*Mobile-specific tests should be added to verify compatibility/stability/functionality across Android and iOS tablets and phones<br />
**smoke/sanity/acceptance section on phone/tablet<br />
**Basic Functional and UI tests on phone/tablet<br />
**Panning, zooming, scrolling, tab access and flow between tabs<br />
**OS/Browser interaction using Firefox and stock browser on Android phones and tablets<br />
**OS/Browser interaction using Safari browser on iPhones and iPads<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
**Verify compatibility and functionality when working with Android/iOS Settings and with browser app-specific settings.<br />
<br />
==Network/Internet==<br />
*Verify the impact of various ways to access the internet: timing, communication, messaging, outages, errors, traffic, etc.<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
=Major Areas Focus=<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
===UI===<br />
*Sign Up:<br />
**'SIGN UP' button<br />
**'Email' field<br />
**'Password' field<br />
**'Submit' and 'Cancel'(x) buttons<br />
**'SIGN UP WITH other apps' option<br />
*Login:<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**'Login with other apps' option is present<br />
*Logout<br />
**'Log out' button<br />
===Full Functional===<br />
*Sign Up:<br />
**Verify that clicking submit button after entering all the required fields, submits the data<br />
**Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
**Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
**Verify that sign up with other apps works as expected<br />
**Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
**Verify sign-up with:<br />
***valid email, invalid password<br />
***valid email, valid password<br />
***invalid email, invalid password <br />
***invalid email, valid password<br />
**Verify email strings and all legal combinations of characters<br />
**Copy/Pasting emails from other sources<br />
**Auto-completion of emails<br />
**Verify minimum/maximum sizes of emails (length)<br />
**Verify password strings and ll legal combinations of characters<br />
**Copy/Pasting passwords from other sources<br />
**Verify minimum/maximum sizes of passwords (length)<br />
**Verify that passwords are stored if "remember password" option is chosen<br />
**Verify that passwords are not stored if "never remember password" option is chosen <br />
*Login<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
***Verify email strings and all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
***Verify password strings and ll legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
==Localization==<br />
*Verify the UI flow with specific focus on localization, all text-based content <br />
*Quick verification of localized headers <br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150297QA/IAM/TestPlan2016-10-05T14:09:21Z<p>Teodora.Vermesan: /* Email and IRC */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch) - owns Community Analytics and Volunteer Management Systems<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and owns infrastructure fortification<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team and owns the IAM packages B and C<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians and owns technical debt reduction<br />
**Yousef Alam(:yalam96) - owns Participation Infrastructure<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
==OS/Browser integration==<br />
*Verify access and use across browsers on same OS, different OS<br />
*Verify access and use across OS platforms, same browser, different browser<br />
*Browser preferences, esp for privacy/security<br />
*Browser synchronization - same platform, across platforms<br />
*Verify door hanger information (per browser, desktop and mobile)<br />
==Mobile Testing==<br />
*Mobile-specific tests should be added to verify compatibility/stability/functionality across Android and iOS tablets and phones<br />
**Complete the smoke/sanity/acceptance section on phone/tablet<br />
**Complete the Basic Functional and UI sections on phone/tablet<br />
**Panning, zooming, scrolling, tab access and flow between tabs<br />
**OS/Browser interaction using FireFox and stock browser on Android phones and tablets<br />
**OS/Browser interaction using Safari browser on iPhones and iPads<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
**Verify compatibility and functionality when working with Android/iOS Settings and with browser app-specific settings.<br />
==Network/Internet==<br />
*Verify the impact of various ways to access the internet: timing, communication, messaging, outages, errors, traffic, etc.<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
=Major Areas Focus=<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
===UI===<br />
*Sign Up:<br />
**'SIGN UP' button<br />
**'Email' field<br />
**'Password' field<br />
**'Submit' and 'Cancel'(x) buttons<br />
**'SIGN UP WITH other apps' option<br />
*Login:<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**'Login with other apps' option is present<br />
*Logout<br />
**'Log out' button<br />
===Full Functional===<br />
*Sign Up:<br />
**Verify that clicking submit button after entering all the required fields, submits the data<br />
**Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
**Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
**Verify that sign up with other apps works as expected<br />
**Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
**Verify sign-up with:<br />
***valid email, invalid password<br />
***valid email, valid password<br />
***invalid email, invalid password <br />
***invalid email, valid password<br />
**Verify email strings and all legal combinations of characters<br />
**Copy/Pasting emails from other sources<br />
**Auto-completion of emails<br />
**Verify minimum/maximum sizes of emails (length)<br />
**Verify password strings and ll legal combinations of characters<br />
**Copy/Pasting passwords from other sources<br />
**Verify minimum/maximum sizes of passwords (length)<br />
**Verify that passwords are stored if "remember password" option is chosen<br />
**Verify that passwords are not stored if "never remember password" option is chosen <br />
*Login<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
***Verify email strings and all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
***Verify password strings and ll legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
==Localization==<br />
*Verify the UI flow with specific focus on localization, all text-based content <br />
*Quick verification of localized headers <br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150296QA/IAM/TestPlan2016-10-05T14:02:50Z<p>Teodora.Vermesan: adding results</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
==OS/Browser integration==<br />
*Verify access and use across browsers on same OS, different OS<br />
*Verify access and use across OS platforms, same browser, different browser<br />
*Browser preferences, esp for privacy/security<br />
*Browser synchronization - same platform, across platforms<br />
*Verify door hanger information (per browser, desktop and mobile)<br />
==Mobile Testing==<br />
*Mobile-specific tests should be added to verify compatibility/stability/functionality across Android and iOS tablets and phones<br />
**Complete the smoke/sanity/acceptance section on phone/tablet<br />
**Complete the Basic Functional and UI sections on phone/tablet<br />
**Panning, zooming, scrolling, tab access and flow between tabs<br />
**OS/Browser interaction using FireFox and stock browser on Android phones and tablets<br />
**OS/Browser interaction using Safari browser on iPhones and iPads<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
**Verify compatibility and functionality when working with Android/iOS Settings and with browser app-specific settings.<br />
==Network/Internet==<br />
*Verify the impact of various ways to access the internet: timing, communication, messaging, outages, errors, traffic, etc.<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
=Major Areas Focus=<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
===UI===<br />
*Sign Up:<br />
**'SIGN UP' button<br />
**'Email' field<br />
**'Password' field<br />
**'Submit' and 'Cancel'(x) buttons<br />
**'SIGN UP WITH other apps' option<br />
*Login:<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**'Login with other apps' option is present<br />
*Logout<br />
**'Log out' button<br />
===Full Functional===<br />
*Sign Up:<br />
**Verify that clicking submit button after entering all the required fields, submits the data<br />
**Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
**Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
**Verify that sign up with other apps works as expected<br />
**Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
**Verify sign-up with:<br />
***valid email, invalid password<br />
***valid email, valid password<br />
***invalid email, invalid password <br />
***invalid email, valid password<br />
**Verify email strings and all legal combinations of characters<br />
**Copy/Pasting emails from other sources<br />
**Auto-completion of emails<br />
**Verify minimum/maximum sizes of emails (length)<br />
**Verify password strings and ll legal combinations of characters<br />
**Copy/Pasting passwords from other sources<br />
**Verify minimum/maximum sizes of passwords (length)<br />
**Verify that passwords are stored if "remember password" option is chosen<br />
**Verify that passwords are not stored if "never remember password" option is chosen <br />
*Login<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
***Verify email strings and all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
***Verify password strings and ll legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
==Localization==<br />
*Verify the UI flow with specific focus on localization, all text-based content <br />
*Quick verification of localized headers <br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150288QA/IAM/TestPlan2016-10-05T13:41:13Z<p>Teodora.Vermesan: /* Scope of Testing */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
==Mobile Testing==<br />
*Mobile-specific tests should be added to verify compatibility/stability/functionality across Android and iOS tablets and phones<br />
**Complete the smoke/sanity/acceptance section on phone/tablet<br />
**Complete the Basic Functional and UI sections on phone/tablet<br />
**Panning, zooming, scrolling, tab access and flow between tabs<br />
**OS/Browser interaction using FireFox and stock browser on Android phones and tablets<br />
**OS/Browser interaction using Safari browser on iPhones and iPads<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
**Verify compatibility and functionality when working with Android/iOS Settings and with browser app-specific settings.<br />
==Network/Internet==<br />
*Verify the impact of various ways to access the internet: timing, communication, messaging, outages, errors, traffic, etc.<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150287QA/IAM/TestPlan2016-10-05T13:39:43Z<p>Teodora.Vermesan: /* Requirements for test */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
==Mobile Testing==<br />
*Mobile-specific tests should be added to verify compatibility/stability/functionality across Android and iOS tablets and phones<br />
**Complete the smoke/sanity/acceptance section on phone/tablet<br />
**Complete the Basic Functional and UI sections on phone/tablet<br />
**Panning, zooming, scrolling, tab access and flow between tabs<br />
**OS/Browser interaction using FireFox and stock browser on Android phones and tablets<br />
**OS/Browser interaction using Safari browser on iPhones and iPads<br />
**Compatibility - review actions and processes that are unique to mobile devices<br />
**Verify compatibility and functionality when working with Android/iOS Settings and with browser app-specific settings.<br />
==Network/Internet==<br />
*Verify the impact of various ways to access the internet: timing, communication, messaging, outages, errors, traffic, etc.<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150278QA/IAM/TestPlan2016-10-05T13:04:25Z<p>Teodora.Vermesan: /* Background */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150277QA/IAM/TestPlan2016-10-05T13:03:22Z<p>Teodora.Vermesan: adding results</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information, see this guide to migrating your site away from Persona: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test=<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150276QA/IAM/TestPlan2016-10-05T13:01:53Z<p>Teodora.Vermesan: /* Re-testing */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information, see this guide to migrating your site away from Persona: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test==<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150275QA/IAM/TestPlan2016-10-05T13:01:12Z<p>Teodora.Vermesan: /* Functional testing */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information, see this guide to migrating your site away from Persona: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance and Regression<br />
<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the Full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test==<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150274QA/IAM/TestPlan2016-10-05T12:59:49Z<p>Teodora.Vermesan: /* Scope of Testing */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information, see this guide to migrating your site away from Persona: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature, and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product, and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance, and Regression<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the Full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test==<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150273QA/IAM/TestPlan2016-10-05T12:58:28Z<p>Teodora.Vermesan: /* Background */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. <br />
*The operational and security support of the persona.org services is provided until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information, see this guide to migrating your site away from Persona: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature, and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product, and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance, and Regression<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the Full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test==<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150272QA/IAM/TestPlan2016-10-05T12:57:27Z<p>Teodora.Vermesan: /* Background */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, that's easy to use and easy to deploy, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. *Mozilla has committed to operational and security support of the persona.org services until November 30th, 2016, when Mozilla will shut down the persona.org services (Persona.org and related domains will be taken offline)<br />
*For more information, see this guide to migrating your site away from Persona: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature, and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product, and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance, and Regression<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the Full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test==<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150271QA/IAM/TestPlan2016-10-05T12:56:21Z<p>Teodora.Vermesan: /* Background */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, that's easy to use and easy to deploy, working on all major browsers<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozill. *Mozilla has committed to operational and security support of the persona.org services until November 30th, 2016<br />
*On November 30th, 2016, Mozilla will shut down the persona.org services(Persona.org and related domains will be taken offline)<br />
*For more information, see this guide to migrating your site away from Persona: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature, and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product, and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance, and Regression<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the Full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test==<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150270QA/IAM/TestPlan2016-10-05T12:55:10Z<p>Teodora.Vermesan: /* Strategy */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, that's easy to use and easy to deploy, working on all major browsers.<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. *Mozilla has committed to operational and security support of the persona.org services until November 30th, 2016.<br />
*On November 30th, 2016, Mozilla will shut down the persona.org services(Persona.org and related domains will be taken offline)<br />
*For more information, see this guide to migrating your site away from Persona: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the builds<br />
*The focus needs to be on quality, but also on providing accurate feedback on successes and issues to the team, so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature, and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product, and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance, and Regression<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the Full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test==<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150269QA/IAM/TestPlan2016-10-05T12:53:41Z<p>Teodora.Vermesan: /* Background */</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, that's easy to use and easy to deploy, working on all major browsers.<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. *Mozilla has committed to operational and security support of the persona.org services until November 30th, 2016.<br />
*On November 30th, 2016, Mozilla will shut down the persona.org services(Persona.org and related domains will be taken offline)<br />
*For more information, see this guide to migrating your site away from Persona: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the weekly builds and deployments IAM. The focus needs to be on quality, but also on providing accurate feedback on successes and issues to Dev and PM so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature, and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product, and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance, and Regression<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the Full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test==<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150268QA/IAM/TestPlan2016-10-05T12:52:24Z<p>Teodora.Vermesan: adding results</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, that's easy to use and easy to deploy. It works on all major browsers.<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. *Mozilla has committed to operational and security support of the persona.org services until November 30th, 2016.<br />
*On November 30th, 2016, Mozilla will shut down the persona.org services(Persona.org and related domains will be taken offline)<br />
*For more information, see this guide to migrating your site away from Persona: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the weekly builds and deployments IAM. The focus needs to be on quality, but also on providing accurate feedback on successes and issues to Dev and PM so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature, and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product, and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance, and Regression<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the Full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing==<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test==<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150267QA/IAM/TestPlan2016-10-05T12:50:37Z<p>Teodora.Vermesan: adding results</p>
<hr />
<div>=Overview=<br />
*This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
=Background=<br />
*Mozilla Persona is a cross-browser login system for the Web, that's easy to use and easy to deploy. It works on all major browsers.<br />
*Because the metrics shown that usage of persona.org is low and has not grown over the last two years, persona will no longer actively developed by Mozilla. *Mozilla has committed to operational and security support of the persona.org services until November 30th, 2016.<br />
*On November 30th, 2016, Mozilla will shut down the persona.org services(Persona.org and related domains will be taken offline)<br />
*For more information, see this guide to migrating your site away from Persona: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers<br />
=Objective=<br />
*Identity and Access Management work provides an identified replacement for persona which outlines a future integration of LDAP with mozillians.org<br />
*Auth0 will replace persona, which offers single sign-on services, abstracting various login and identity services into a single API including public APIs like Facebook Connect and public or private instances of Active Directory and LDAP.<br />
=Strategy=<br />
*Create a consistent and repeatable set of tests for qualifying and releasing the weekly builds and deployments IAM. The focus needs to be on quality, but also on providing accurate feedback on successes and issues to Dev and PM so that the Production releases provide a useful product for the Mozilla and development communities. <br />
**Exploratory testing on the client and server side<br />
**Create useful client-side and server-side test cases<br />
**Put accent on security and privacy issues that might come up across OS, browsers, accounts(emails and passwords)<br />
**Identifying and tracking issues in GitHub and Bugzilla.<br />
**Provide useful metrics<br />
=Scope of Testing=<br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
==Functional testing==<br />
*Will cover:<br />
**full UI and functionality of the application <br />
**both basic and edge, positive and negative cases<br />
**connectivity (Offline behavior, functionality on cellular networks) <br />
*Functional tests will be written in Test Rail, providing detailed test steps, expected and actual results for each test case<br />
*Manual functional testing will be applied at two levels:<br />
**Component testing – covers a specific feature, and aims at validating its implementation and providing a list of issues affecting that specific component<br />
**End-to-End testing – aims at delivering a clear view on the overall quality of the product, and at providing a comprehensive list of issues affecting the application<br />
*The full set of tests will also serve as a base to derive other test sets like: Smoke, Acceptance, and Regression<br />
==Re-testing==<br />
*Will be done as needed, in parallel with Regression Testing, by re-executing previously failed tests, to make sure fixes are properly verified and the Full test set is properly updated according to the latest fixes, to provide a more accurate insight on the overall quality of the product<br />
==Smoke testing==<br />
*Will cover only the most basic functionality<br />
*Will be performed on intermediary builds, to confirm that the build is testable and stable<br />
==Exploratory testing==<br />
*Examples of exploratory testing cover: investigating a certain area suspected of being more prone to issues, looking for bugs at a very early stage, investigating freshly implemented features to provide quick feedback to developers and the rest of the team<br />
==Regression testing==<br />
*Will cover basic cases and areas that are most affected by issues<br />
*Its purpose is to identify potential regression caused by bug fixes and/or new features<br />
==Acceptance testing==<br />
*Will cover basic and critical functionality of the application <br />
*It is aimed to prove that Release Candidate builds quality is acceptable for release<br />
==Automated testing==<br />
*TBD<br />
==API testing==<br />
*Will be performed with the purpose of verifying the sanity of the server (issues with the API will be identified early on, thus allowing the team to be informed and take necessary action)<br />
==Non-Functional testing=<br />
*Non-functional testing will be done at different stages in the product lifecycle, and will evaluate product/feature non-functional attributes including (but not limited to):<br />
**Efficiency – Performance, Load, Stress <br />
**Portability<br />
=Target Readership=<br />
*This document is written for the following readership:<br />
**Since this is a public-facing product, we need to make sure that the Mozilla community can access, test, and develop around a solid product<br />
**Development team<br />
**Engineering group<br />
**Management<br />
=General Test Information=<br />
==Links and Documentation== <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
==Weekly Test Schedules==<br />
*Unknown yet<br />
==Weekly Meetings==<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
==Email and IRC==<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
==Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
=Requirements for test==<br />
==Environmental needs==<br />
*target mostly desktop PC / laptop<br />
*mobile devices<br />
<br />
=Major Areas Focus=<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
<br />
<br />
=Entry criteria=<br />
*Testing will begin when the following criteria are met:<br />
**Development team delivers a feature complete build to the QA<br />
**The application is successfully deployed on the appropriate environment (including integrated components, depending on environment scope)<br />
**Test cases, estimations and schedule has been reviewed and approved <br />
<br />
=Exit criteria=<br />
*Testing will complete when:<br />
**All test cases have been executed<br />
**All non-closed defects are reviewed by the team and marked as follows for subsequent releases:Fixed, Regressed, Closed, Deferred<br />
**Summary test report is published</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150245QA/IAM/TestPlan2016-10-05T10:19:43Z<p>Teodora.Vermesan: /* Overview */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Areas Focus ==<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
==QA Sign-Off for Stage==<br />
*TBD<br />
*Complete all required testing for the current weekly train<br />
<br />
== QA Sign-Off for Production ==<br />
*TBD<br />
*Complete all required testing for the current weekly train</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150244QA/IAM/TestPlan2016-10-05T10:18:50Z<p>Teodora.Vermesan: /* Overview */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Areas Focus ==<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
==QA Sign-Off for Stage==<br />
*TBD<br />
*Complete all required testing for the current weekly train<br />
<br />
== QA Sign-Off for Production ==<br />
*TBD<br />
*Complete all required testing for the current weekly train</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150242QA/IAM/TestPlan2016-10-05T10:07:33Z<p>Teodora.Vermesan: adding results</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians.org & reps.mozilla.org<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Areas Focus ==<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
==QA Sign-Off for Stage==<br />
*TBD<br />
*Complete all required testing for the current weekly train<br />
<br />
== QA Sign-Off for Production ==<br />
*TBD<br />
*Complete all required testing for the current weekly train</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150238QA/IAM/TestPlan2016-10-05T09:58:30Z<p>Teodora.Vermesan: /* Major Areas Focus */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Areas Focus ==<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
==QA Sign-Off for Stage==<br />
*Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150237QA/IAM/TestPlan2016-10-05T09:57:22Z<p>Teodora.Vermesan: /* Major Areas Focus */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Areas Focus ==<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'SIGN UP' button<br />
***Verify the page has an 'Email' field<br />
***Verify the page has a 'Password' field<br />
***Verify the page has both 'Submit' and 'Cancel'(x) buttons<br />
***Verify the page has 'SIGN UP WITH other apps' option<br />
<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error: "Can't be blank"<br />
***Verify that sign up with other apps works as expected<br />
***Verify that sign up with an already verified email will lead to an error message: "The user already exists"<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password <br />
****invalid email, valid password<br />
**Email Field:<br />
***Verify email strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Verify password strings<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify that passwords are not stored if "never remember password" option is chosen <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify that 'email field, 'password' field, "Not your account?" link, "Don't remember your password?" link are present<br />
**Verify that if the user was already logged in with an account he can changed the account using the "Not your account" option or login with the previous one<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same account<br />
***with different emails in the same browser/different browser<br />
***an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
==QA Sign-Off for Stage==<br />
*Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150234QA/IAM/TestPlan2016-10-05T09:39:37Z<p>Teodora.Vermesan: /* Major Areas Focus */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Areas Focus ==<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'sign up' button<br />
***Verify the page has 'email' and 'password' field<br />
***Verify the page has both 'submit' and 'cancel'(x) buttons<br />
***Verify the page has 'Sign Up with other apps' option<br />
***Verify that the required/mandatory fields are marked with * against the field<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data to the server<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error <br />
***Verify that not filling the optional fields and clicking submit button will still send data to server without any validation error<br />
***Verify that sign up with other apps works as expected<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password<br />
****invalid email, valid password<br />
****different accounts using same email and password combos<br />
****a password email already in use<br />
****an email already in use<br />
**Email Field:<br />
***Email strings/types<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
**Password field:<br />
***Password strings/types<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify whether or not passwords are stored client-side <br />
***Verify whether or not passwords are stored on the server <br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider with proper email account listed, live verification link, etc.<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
*Login<br />
**Verify: Email field, Password field, "Not your account?", "Don't remember your password?"<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same email, then log out from one of the two browsers<br />
***with different emails for different clients in the same browser/different browser<br />
***with the same email for different clients in the same browser, then log out from one of the browsers<br />
**Verify that the user cannot log in with an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that there is reset button to clear the field's text <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify application clears the session for the user after logout<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
==QA Sign-Off for Stage==<br />
*Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150233QA/IAM/TestPlan2016-10-05T09:39:06Z<p>Teodora.Vermesan: /* Major Test Areas */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Areas Focus ==<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'sign up' button<br />
***Verify the page has 'email' and 'password' field<br />
***Verify the page has both 'submit' and 'cancel'(x) buttons<br />
***Verify the page has 'Sign Up with other apps' option<br />
***Verify that the required/mandatory fields are marked with * against the field<br />
<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data to the server<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error <br />
***Verify that not filling the optional fields and clicking submit button will still send data to server without any validation error<br />
***Verify that sign up with other apps works as expected<br />
***Verify sign-up with:<br />
****valid email, invalid password<br />
****valid email, valid password<br />
****invalid email, invalid password<br />
****invalid email, valid password<br />
****different accounts using same email and password combos<br />
****a password email already in use<br />
****an email already in use<br />
<br />
**Email Field:<br />
***Email strings/types<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
<br />
**Password field:<br />
***Password strings/types<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are stored if "remember password" option is chosen<br />
***Verify whether or not passwords are stored client-side <br />
***Verify whether or not passwords are stored on the server <br />
<br />
**Email notification:<br />
***Email notification for new accounts: verification email through email provider with proper email account listed, live verification link, etc.<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
<br />
*Login<br />
**Verify: Email field, Password field, "Not your account?", "Don't remember your password?"<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same email, then log out from one of the two browsers<br />
***with different emails for different clients in the same browser/different browser<br />
***with the same email for different clients in the same browser, then log out from one of the browsers<br />
**Verify that the user cannot log in with an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that there is reset button to clear the field's text <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
<br />
*Logout<br />
**Verify application allows single sign off from all the devices.<br />
**Verify application let’s you sign off for multiple accounts.<br />
**Verify application clears the session for the user after logout<br />
**Verify if application takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
<br />
*Other:<br />
**Login to the application with multiple accounts at the same time <br />
**Check if everything works as expected in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
==QA Sign-Off for Stage==<br />
*Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150231QA/IAM/TestPlan2016-10-05T09:26:51Z<p>Teodora.Vermesan: /* Major Test Areas */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Test Areas ==<br />
*Sign Up:<br />
**Buttons:<br />
***Verify the page has a 'sign up' button<br />
***Verify the page has 'email' and 'password' field<br />
***Verify the page has both 'submit' and 'cancel'(x) buttons<br />
***Verify the page has "Sign Up with other apps"<br />
***Verify that the required/mandatory fields are marked with * against the field<br />
<br />
**Form fields:<br />
***Verify that clicking submit button after entering all the required fields, submits the data to the server<br />
***Verify that clicking cancel button after entering all the required fields, cancels the submit request and resets all the fields<br />
***Verify that not filling the mandatory fields and clicking submit button will lead to validation error <br />
***Verify that not filling the optional fields and clicking submit button will still send data to server without any validation error<br />
***Verify that entering blank spaces on mandatory fields lead to validation error <br />
***Verify that sign up with other apps works as expected<br />
***Verify sign-up with:<br />
****valid email, invalid passwords<br />
****valid email, valid passwords<br />
****invalid email, invalid password<br />
****invalid email, valid password<br />
****different accounts using same email/password combos<br />
****a password and/or email already in use<br />
<br />
**Email Field:<br />
***Email strings/types/limits<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting emails (names) from other sources<br />
***Auto-completion of emails<br />
***Verify minimum/maximum sizes of emails (length)<br />
<br />
**Password field:<br />
***Password strings/types/limits<br />
***Verify all legal combinations of characters<br />
***Copy/Pasting passwords from other sources<br />
***Auto-completion of passwords<br />
***Verify minimum/maximum sizes of passwords (length)<br />
***Verify that passwords are never stored in LocalStore on the user machine<br />
***Verify whether or not passwords are stored client-side <br />
***Verify whether or not passwords are stored on the server <br />
<br />
**Email notification:<br />
***Confirm Email verification UI<br />
***Email notification for new accounts: verification email through email provider with proper email account listed, live verification link, etc.<br />
***Check functionality when the user can not verify by email (email provider is down or user can not access email account for some reason)<br />
***Check functionality when the user does not verify by email (skips, forgets)<br />
<br />
*Login<br />
**Verify : Email field, Password field, "Not your account?", "Don't remember your password?"<br />
**Login with:<br />
***valid email, valid password<br />
***valid email, invalid password<br />
***invalid email ,invalid password<br />
***valid email and password <br />
***with other apps<br />
***simultaneously in two different browsers with the same email, then log out from one of the two browsers<br />
***with different emails for different clients in the same browser/different browser<br />
***with the same email for different clients in the same browser, then log out from one of the browsers<br />
**Verify that the user cannot log in with an email if he did not confirm the used email<br />
**Verify that the log in is kept when restoring a session after a browser crash <br />
**Verify that a message gets displayed in case user leaves email or password field as blank <br />
**Verify that a message is displayed in case user exceeds the character limit of the user name and password fields <br />
**Verify that there is reset button to clear the field's text <br />
**Verify that the password is in encrypted form when entered <br />
**Verify that there is limit on the total number of unsuccessful attempts <br />
**Verify that in case of incorrect credentials a message is displayed "incorrect username or password" <br />
**Verify if the password can be copy-pasted or not <br />
**Verify that once logged in, clicking back button doesn't logout user<br />
<br />
*Logout<br />
**Verify app allows single sign off from all the devices.<br />
**Verify app let’s you sign off for multiple accounts.<br />
**Verify app clears cookies after logout<br />
**Verify app clears the session for the user after logout<br />
**Verify if app takes more time for logout at different connection speeds<br />
**Verify the logout page redirects to the page where it allows login or homepage<br />
**Verify the logout button or link works on all devices<br />
<br />
*Network: Verify the impact of various ways to access the internet<br />
**Ethernet - personal vs. office, with and without VPN<br />
**Public WiFi<br />
**Private WiFi and other home setups<br />
**3g, 4g<br />
<br />
*Other:<br />
**login to the application with multiple user accounts at the same time and capture latency of authentication <br />
**Check if everything works in different browsers <br />
**Page crash should not reveal application or server info. Error page should be displayed for this<br />
**Error messages should not reveal any sensitive information<br />
<br />
==QA Sign-Off for Stage==<br />
*Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150219QA/IAM/TestPlan2016-10-05T08:48:16Z<p>Teodora.Vermesan: /* QA Sign-Off for Stage */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Test Areas ==<br />
*TBD<br />
<br />
==QA Sign-Off for Stage==<br />
*Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150218QA/IAM/TestPlan2016-10-05T08:47:51Z<p>Teodora.Vermesan: /* Major Test Areas */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Test Areas ==<br />
*TBD<br />
<br />
==QA Sign-Off for Stage==<br />
*Requirements and procedures:<br />
**Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150217QA/IAM/TestPlan2016-10-05T08:47:24Z<p>Teodora.Vermesan: /* Bugs and Open Issues */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments==<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Test Areas == <br />
==QA Sign-Off for Stage==<br />
*Requirements and procedures:<br />
**Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150216QA/IAM/TestPlan2016-10-05T08:47:01Z<p>Teodora.Vermesan: /* Email and IRC */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch(:hmitsch)<br />
**Arielle - currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos(:nemo-yiannis) - development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
**Nikos Roussos(:nikos) - front-end<br />
**Pierros Papadeas(:pierros) - eng management for the team<br />
**Anastasios Katsoulas(:tasos) - web dev on mozillians<br />
**Yousef Alam(:yalam96) -new infrastructure + community websites<br />
**Teodora Vermesan(:TeoVermesan) - QA Engineer<br />
**Ioana Chiorean (:ioanachiorean) - Release QA Mobile Team Lead <br />
**Florin Mezei ((:florinmezei) - Project Manager (Release QA, WebQA, BuildDuty)<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Test Areas == <br />
==QA Sign-Off for Stage==<br />
*Requirements and procedures:<br />
**Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150213QA/IAM/TestPlan2016-10-05T08:41:53Z<p>Teodora.Vermesan: /* Email and IRC */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post <br />
*email List: parsys@mozilla.com<br />
*Google Group: https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*IRC: #parsys <br />
*Team:<br />
**Henrik Mitsch: hmitsch<br />
**Arielle:currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos<br />
***development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
***nemo-yiannis<br />
**Nikos Roussos<br />
***front-end<br />
***nikos<br />
**Pierros Papadeas<br />
***pierros<br />
***eng management for the team<br />
**Anastasios Katsoulas<br />
***web dev on mozillians<br />
***tasos<br />
**Yousef Alam<br />
***yalam96<br />
***new infrastructure + community websites<br />
**Teodora Vermesan<br />
***TeoVermesan<br />
***QA Engineer<br />
**Ioana Chiorean - Release QA Mobile Team Lead <br />
**Florin Mezei - Project Manager (Release QA, WebQA, BuildDuty)<br />
***Ioana and Florin will provide support to Teodora as we define the testing needed on the project<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Test Areas == <br />
==QA Sign-Off for Stage==<br />
*Requirements and procedures:<br />
**Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150212QA/IAM/TestPlan2016-10-05T08:40:26Z<p>Teodora.Vermesan: /* Scope of Testing */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
*Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
*Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post to this email List: <br />
**parsys@mozilla.com<br />
*Or post to the Google Group: <br />
**https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*Post to IRC: <br />
**#parsys <br />
*Team:<br />
**Henrik Mitsch: hmitsch<br />
**Arielle:currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos<br />
***development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
***nemo-yiannis<br />
**Nikos Roussos<br />
***front-end<br />
***nikos<br />
**Pierros Papadeas<br />
***pierros<br />
***eng management for the team<br />
**Anastasios Katsoulas<br />
***web dev on mozillians<br />
***tasos<br />
**Yousef Alam<br />
***yalam96<br />
***new infrastructure + community websites<br />
**Teodora Vermesan<br />
***TeoVermesan<br />
***QA Engineer<br />
**Ioana Chiorean - Release QA Mobile Team Lead <br />
**Florin Mezei - Project Manager (Release QA, WebQA, BuildDuty)<br />
***Ioana and Florin will provide support to Teodora as we define the testing needed on the project<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Test Areas == <br />
==QA Sign-Off for Stage==<br />
*Requirements and procedures:<br />
**Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150211QA/IAM/TestPlan2016-10-05T08:39:54Z<p>Teodora.Vermesan: /* Overview */</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.<br />
<br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post to this email List: <br />
**parsys@mozilla.com<br />
*Or post to the Google Group: <br />
**https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*Post to IRC: <br />
**#parsys <br />
*Team:<br />
**Henrik Mitsch: hmitsch<br />
**Arielle:currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos<br />
***development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
***nemo-yiannis<br />
**Nikos Roussos<br />
***front-end<br />
***nikos<br />
**Pierros Papadeas<br />
***pierros<br />
***eng management for the team<br />
**Anastasios Katsoulas<br />
***web dev on mozillians<br />
***tasos<br />
**Yousef Alam<br />
***yalam96<br />
***new infrastructure + community websites<br />
**Teodora Vermesan<br />
***TeoVermesan<br />
***QA Engineer<br />
**Ioana Chiorean - Release QA Mobile Team Lead <br />
**Florin Mezei - Project Manager (Release QA, WebQA, BuildDuty)<br />
***Ioana and Florin will provide support to Teodora as we define the testing needed on the project<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Test Areas == <br />
==QA Sign-Off for Stage==<br />
*Requirements and procedures:<br />
**Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/IAM/TestPlan&diff=1150210QA/IAM/TestPlan2016-10-05T08:38:49Z<p>Teodora.Vermesan: adding results</p>
<hr />
<div>== Overview ==<br />
This test plan covers the general weekly testing that will happen against Identity and Access Management product in the Stage Test environment. <br />
The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side. <br />
== Strategy ==<br />
Identity and Access Management work:<br />
*aligned with IT on a common plan<br />
*identified replacement for persona<br />
*outlined future integration of LDAP with mozillians.org<br />
*auth0 will replace persona<br />
== Scope of Testing == <br />
Client-side testing will cover the following areas: basic functionality and UI, accounts and emails, interaction with the Server, security and privacy, usability and compatibility across OS and browsers.<br />
Server-side testing will cover the following areas: basic functionality, support for multiple client sites, user security and privacy, information handling and storage, information persistence across deployments, and logging.<br />
<br />
== General Test Information ==<br />
=== Links and Documentation === <br />
*Auth0 Implementation Roadmap:<br />
**https://docs.google.com/presentation/d/1Cd_UDM-ncdiVDGrwuBSOl0d8YhiYTXE1QuXifTsj4zA/edit#slide=id.g1655979439_0_0<br />
*Tracking work:<br />
**https://tree.taiga.io/project/pierros-mozilla-particiaption-systems/kanban<br />
=== Weekly Test Schedules ===<br />
*Unknown yet<br />
=== Weekly Meetings ===<br />
*Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio<br />
*Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo<br />
=== Email and IRC===<br />
*Post to this email List: <br />
**parsys@mozilla.com<br />
*Or post to the Google Group: <br />
**https://groups.google.com/a/mozilla.com/forum/#!forum/parsys<br />
*Post to IRC: <br />
**#parsys <br />
*Team:<br />
**Henrik Mitsch: hmitsch<br />
**Arielle:currently not on the team, will be back 01 JAN 2017<br />
**John Giannelos<br />
***development on reps.mozilla.org, mozillians.org and supporting the infrastructure<br />
***nemo-yiannis<br />
**Nikos Roussos<br />
***front-end<br />
***nikos<br />
**Pierros Papadeas<br />
***pierros<br />
***eng management for the team<br />
**Anastasios Katsoulas<br />
***web dev on mozillians<br />
***tasos<br />
**Yousef Alam<br />
***yalam96<br />
***new infrastructure + community websites<br />
**Teodora Vermesan<br />
***TeoVermesan<br />
***QA Engineer<br />
**Ioana Chiorean - Release QA Mobile Team Lead <br />
**Florin Mezei - Project Manager (Release QA, WebQA, BuildDuty)<br />
***Ioana and Florin will provide support to Teodora as we define the testing needed on the project<br />
<br />
== Bugs and Open Issues ==<br />
*Bugzilla: mozillians & reps<br />
*Github: mozmoderator<br />
<br />
==Client and Server Test Environments<br />
*development: http://mozillians-dev.allizom.org<br />
*staging: http://mozillians.allizom.org<br />
*production: http://mozillians.org<br />
<br />
== Supported OS and Browsers ==<br />
*All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet <br />
<br />
== Major Test Areas == <br />
==QA Sign-Off for Stage==<br />
*Requirements and procedures:<br />
**Complete all required testing for the current weekly train: resolved/closed issues, suggested areas for QA focus, specific features and areas of test coverage, automation, etc.<br />
<br />
== QA Testing for Production ==<br />
<br />
<br />
== QA Sign-Off for Production ==</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/Fennec/First_time_reader_view_prompt_evaluation&diff=1149645QA/Fennec/First time reader view prompt evaluation2016-09-29T12:27:30Z<p>Teodora.Vermesan: /* Still issues */</p>
<hr />
<div>= Overview =<br />
== Purpose ==<br />
The purpose of this wiki is to serve as a general test plan for verifying that always a prompt is shown the first time a user enters reader view, regardless of whether another prompt is shown.<br />
<br />
== Ownership ==<br />
Developer contact: [mailto:ahunt@mozilla.com Anthony Lam (:antlam)], [mailto:s.kaspari@gmail.com Sebastian Kaspari (:sebastian)] <br />
<br />
QA: [mailto:teodora.vermesan@softvision. Teodora Vermesan (:TeoVermesan)]<br />
<br />
== Overall Status ==<br />
<br />
<small>'''<font color="green">[ON TRACK]</font>'''</small> Nightly 52: <br />
<br />
<small>'''<font color="red">[AT RISK]</font>'''</small> Aurora 51:<br />
<br />
<small>'''<font color="greene">[ON TRACK]</font>'''</small> Beta 50<br />
<br />
= Testing Summary = <br />
<br />
== Scope of testing ==<br />
The testing will be focus on<br />
* verifying that always a prompt is shown the first time a user enters reader view, regardless of whether another prompt is shown. <br />
<br />
== Environments ==<br />
Testing will be performed on following devices: <br />
* Phones<br />
** 4.x<br />
** 5.x<br />
** 6.0<br />
* Tablet<br />
** 4.x<br />
** 5.x<br />
** 6.0<br />
<br />
== Specifications ==<br />
* "how to bookmark" helper UI is displayed <br />
<br />
== User stories ==<br />
*As a user, I want to be informed how to add items to reading list, after entering reader view since the "Add to RL" icon is now missing.<br />
<br />
== Acceptance Criteria==<br />
*A prompt is shown, after user hits reader view<br />
<br />
= Testing details =<br />
==Date:05-09-2016==<br />
- [https://bugzilla.mozilla.org/show_bug.cgi?id=1300532 Bug 1300532] Contextual hint about offline bookmarks is displayed in normal view instead of reader view<br />
*[[File:reader view.png|600px|thumb|center| Prompt]]<br />
==Date:19-09-2016==<br />
*Device: One A2001(Android 6.0)<br />
*Build: Firefox for Android 52.0a1 (2016-09-19)<br />
*Load an article from news.google.com and tap the reader view icon from the URL Bar<br />
**the page enters reader view and a prompt is displayed: "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks"<br />
*Tap the "Add to Bookmarks" button.<br />
**the second prompt is displayed: "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks".<br />
==Date:21-09-2016==<br />
*Device: One A2001 (Android 6.0)<br />
*Build: Firefox for Android 50 Beta 1<br />
*After tapping the reader view icon from the URL Bar, the page enters reader view and a prompt is displayed: "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks"<br />
Tapping the "Add to Bookmarks" button, the second prompt is displayed: "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks".<br />
==Date:22-09-2016==<br />
*Device: One A2001 (Android 6.0)<br />
*Build: Firefox for Android 51.0a2 (2016-09-21)<br />
*After tapping the reader view icon from the URL Bar, the page enters reader view, but no prompt is displayed. If I open the menu and tap the bookmark icon, then "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks" prompt is displayed. But the prompt "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks" is never displayed.<br />
<br />
=Bug Work=<br />
==Tracking bugs==<br />
* bugs to track the feature<br />
ex:<br />
<onlyinclude><br />
<bugzilla><br />
{<br />
"id": "1275784, migrate-RL, 1234314, 1300532"<br />
}<br />
</bugzilla><br />
</onlyinclude><br />
<br />
==Still issues==<br />
<font color="red">'''[NEW]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1306271 Bug 1306271] - Contextual hint about offline bookmarks is not displayed in Aurora <br/><br />
<br />
===Bug fixed ===<br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1270880 Bug 1270880] - Update "how to bookmark" helper UI to "first time" instead of "third time" <br/><br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1275784 Bug 1275784] - Enable reader view bookmark hint up to beta <br/><br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1300532 Bug 1300532] - Contextual hint about offline bookmarks is displayed in normal view instead of reader view <br/><br />
<br />
=Signoff=<br />
== Criteria ==<br />
* All test cases should be executed<br />
* All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed<br />
<br />
== Results ==<br />
'''Nightly testing'''<br />
-Contextual hint about offline bookmarks is displayed.<br />
<br />
'''Aurora testing'''<br />
-Contextual hint about offline bookmarks is not displayed.<br />
<br />
'''Beta testing'''<br />
-Contextual hint about offline bookmarks is displayed.</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/Fennec/First_time_reader_view_prompt_evaluation&diff=1149644QA/Fennec/First time reader view prompt evaluation2016-09-29T12:22:42Z<p>Teodora.Vermesan: /* Overall Status */</p>
<hr />
<div>= Overview =<br />
== Purpose ==<br />
The purpose of this wiki is to serve as a general test plan for verifying that always a prompt is shown the first time a user enters reader view, regardless of whether another prompt is shown.<br />
<br />
== Ownership ==<br />
Developer contact: [mailto:ahunt@mozilla.com Anthony Lam (:antlam)], [mailto:s.kaspari@gmail.com Sebastian Kaspari (:sebastian)] <br />
<br />
QA: [mailto:teodora.vermesan@softvision. Teodora Vermesan (:TeoVermesan)]<br />
<br />
== Overall Status ==<br />
<br />
<small>'''<font color="green">[ON TRACK]</font>'''</small> Nightly 52: <br />
<br />
<small>'''<font color="red">[AT RISK]</font>'''</small> Aurora 51:<br />
<br />
<small>'''<font color="greene">[ON TRACK]</font>'''</small> Beta 50<br />
<br />
= Testing Summary = <br />
<br />
== Scope of testing ==<br />
The testing will be focus on<br />
* verifying that always a prompt is shown the first time a user enters reader view, regardless of whether another prompt is shown. <br />
<br />
== Environments ==<br />
Testing will be performed on following devices: <br />
* Phones<br />
** 4.x<br />
** 5.x<br />
** 6.0<br />
* Tablet<br />
** 4.x<br />
** 5.x<br />
** 6.0<br />
<br />
== Specifications ==<br />
* "how to bookmark" helper UI is displayed <br />
<br />
== User stories ==<br />
*As a user, I want to be informed how to add items to reading list, after entering reader view since the "Add to RL" icon is now missing.<br />
<br />
== Acceptance Criteria==<br />
*A prompt is shown, after user hits reader view<br />
<br />
= Testing details =<br />
==Date:05-09-2016==<br />
- [https://bugzilla.mozilla.org/show_bug.cgi?id=1300532 Bug 1300532] Contextual hint about offline bookmarks is displayed in normal view instead of reader view<br />
*[[File:reader view.png|600px|thumb|center| Prompt]]<br />
==Date:19-09-2016==<br />
*Device: One A2001(Android 6.0)<br />
*Build: Firefox for Android 52.0a1 (2016-09-19)<br />
*Load an article from news.google.com and tap the reader view icon from the URL Bar<br />
**the page enters reader view and a prompt is displayed: "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks"<br />
*Tap the "Add to Bookmarks" button.<br />
**the second prompt is displayed: "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks".<br />
==Date:21-09-2016==<br />
*Device: One A2001 (Android 6.0)<br />
*Build: Firefox for Android 50 Beta 1<br />
*After tapping the reader view icon from the URL Bar, the page enters reader view and a prompt is displayed: "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks"<br />
Tapping the "Add to Bookmarks" button, the second prompt is displayed: "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks".<br />
==Date:22-09-2016==<br />
*Device: One A2001 (Android 6.0)<br />
*Build: Firefox for Android 51.0a2 (2016-09-21)<br />
*After tapping the reader view icon from the URL Bar, the page enters reader view, but no prompt is displayed. If I open the menu and tap the bookmark icon, then "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks" prompt is displayed. But the prompt "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks" is never displayed.<br />
<br />
=Bug Work=<br />
==Tracking bugs==<br />
* bugs to track the feature<br />
ex:<br />
<onlyinclude><br />
<bugzilla><br />
{<br />
"id": "1275784, migrate-RL, 1234314, 1300532"<br />
}<br />
</bugzilla><br />
</onlyinclude><br />
<br />
==Still issues==<br />
<font color="red">'''[NEW]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id= Bug ] - Contextual hint about offline bookmarks is not displayed in Aurora <br/><br />
<br />
===Bug fixed ===<br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1270880 Bug 1270880] - Update "how to bookmark" helper UI to "first time" instead of "third time" <br/><br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1275784 Bug 1275784] - Enable reader view bookmark hint up to beta <br/><br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1300532 Bug 1300532] - Contextual hint about offline bookmarks is displayed in normal view instead of reader view <br/><br />
<br />
<br />
<br />
=Signoff=<br />
== Criteria ==<br />
* All test cases should be executed<br />
* All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed<br />
<br />
== Results ==<br />
'''Nightly testing'''<br />
-Contextual hint about offline bookmarks is displayed.<br />
<br />
'''Aurora testing'''<br />
-Contextual hint about offline bookmarks is not displayed.<br />
<br />
'''Beta testing'''<br />
-Contextual hint about offline bookmarks is displayed.</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/Fennec/First_time_reader_view_prompt_evaluation&diff=1149641QA/Fennec/First time reader view prompt evaluation2016-09-29T12:06:45Z<p>Teodora.Vermesan: /* Results */</p>
<hr />
<div>= Overview =<br />
== Purpose ==<br />
The purpose of this wiki is to serve as a general test plan for verifying that always a prompt is shown the first time a user enters reader view, regardless of whether another prompt is shown.<br />
<br />
== Ownership ==<br />
Developer contact: [mailto:ahunt@mozilla.com Anthony Lam (:antlam)], [mailto:s.kaspari@gmail.com Sebastian Kaspari (:sebastian)] <br />
<br />
QA: [mailto:teodora.vermesan@softvision. Teodora Vermesan (:TeoVermesan)]<br />
<br />
== Overall Status ==<br />
<br />
<small>'''<font color="green">[ON TRACK]</font>'''</small> Nightly 52: <br />
<br />
<small>'''<font color="red">[AT RISK]</font>'''</small> Aurora 51: 2016-09-13<br />
<br />
<small>'''<font color="greene">[ON TRACK]</font>'''</small> Beta 50<br />
<br />
= Testing Summary = <br />
<br />
== Scope of testing ==<br />
The testing will be focus on<br />
* verifying that always a prompt is shown the first time a user enters reader view, regardless of whether another prompt is shown. <br />
<br />
== Environments ==<br />
Testing will be performed on following devices: <br />
* Phones<br />
** 4.x<br />
** 5.x<br />
** 6.0<br />
* Tablet<br />
** 4.x<br />
** 5.x<br />
** 6.0<br />
<br />
== Specifications ==<br />
* "how to bookmark" helper UI is displayed <br />
<br />
== User stories ==<br />
*As a user, I want to be informed how to add items to reading list, after entering reader view since the "Add to RL" icon is now missing.<br />
<br />
== Acceptance Criteria==<br />
*A prompt is shown, after user hits reader view<br />
<br />
= Testing details =<br />
==Date:05-09-2016==<br />
- [https://bugzilla.mozilla.org/show_bug.cgi?id=1300532 Bug 1300532] Contextual hint about offline bookmarks is displayed in normal view instead of reader view<br />
*[[File:reader view.png|600px|thumb|center| Prompt]]<br />
==Date:19-09-2016==<br />
*Device: One A2001(Android 6.0)<br />
*Build: Firefox for Android 52.0a1 (2016-09-19)<br />
*Load an article from news.google.com and tap the reader view icon from the URL Bar<br />
**the page enters reader view and a prompt is displayed: "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks"<br />
*Tap the "Add to Bookmarks" button.<br />
**the second prompt is displayed: "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks".<br />
==Date:21-09-2016==<br />
*Device: One A2001 (Android 6.0)<br />
*Build: Firefox for Android 50 Beta 1<br />
*After tapping the reader view icon from the URL Bar, the page enters reader view and a prompt is displayed: "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks"<br />
Tapping the "Add to Bookmarks" button, the second prompt is displayed: "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks".<br />
==Date:22-09-2016==<br />
*Device: One A2001 (Android 6.0)<br />
*Build: Firefox for Android 51.0a2 (2016-09-21)<br />
*After tapping the reader view icon from the URL Bar, the page enters reader view, but no prompt is displayed. If I open the menu and tap the bookmark icon, then "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks" prompt is displayed. But the prompt "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks" is never displayed.<br />
<br />
=Bug Work=<br />
==Tracking bugs==<br />
* bugs to track the feature<br />
ex:<br />
<onlyinclude><br />
<bugzilla><br />
{<br />
"id": "1275784, migrate-RL, 1234314, 1300532"<br />
}<br />
</bugzilla><br />
</onlyinclude><br />
<br />
==Still issues==<br />
<font color="red">'''[NEW]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id= Bug ] - Contextual hint about offline bookmarks is not displayed in Aurora <br/><br />
<br />
===Bug fixed ===<br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1270880 Bug 1270880] - Update "how to bookmark" helper UI to "first time" instead of "third time" <br/><br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1275784 Bug 1275784] - Enable reader view bookmark hint up to beta <br/><br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1300532 Bug 1300532] - Contextual hint about offline bookmarks is displayed in normal view instead of reader view <br/><br />
<br />
<br />
<br />
=Signoff=<br />
== Criteria ==<br />
* All test cases should be executed<br />
* All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed<br />
<br />
== Results ==<br />
'''Nightly testing'''<br />
-Contextual hint about offline bookmarks is displayed.<br />
<br />
'''Aurora testing'''<br />
-Contextual hint about offline bookmarks is not displayed.<br />
<br />
'''Beta testing'''<br />
-Contextual hint about offline bookmarks is displayed.</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/Fennec/First_time_reader_view_prompt_evaluation&diff=1149640QA/Fennec/First time reader view prompt evaluation2016-09-29T12:02:15Z<p>Teodora.Vermesan: adding results</p>
<hr />
<div>= Overview =<br />
== Purpose ==<br />
The purpose of this wiki is to serve as a general test plan for verifying that always a prompt is shown the first time a user enters reader view, regardless of whether another prompt is shown.<br />
<br />
== Ownership ==<br />
Developer contact: [mailto:ahunt@mozilla.com Anthony Lam (:antlam)], [mailto:s.kaspari@gmail.com Sebastian Kaspari (:sebastian)] <br />
<br />
QA: [mailto:teodora.vermesan@softvision. Teodora Vermesan (:TeoVermesan)]<br />
<br />
== Overall Status ==<br />
<br />
<small>'''<font color="green">[ON TRACK]</font>'''</small> Nightly 52: <br />
<br />
<small>'''<font color="red">[AT RISK]</font>'''</small> Aurora 51: 2016-09-13<br />
<br />
<small>'''<font color="greene">[ON TRACK]</font>'''</small> Beta 50<br />
<br />
= Testing Summary = <br />
<br />
== Scope of testing ==<br />
The testing will be focus on<br />
* verifying that always a prompt is shown the first time a user enters reader view, regardless of whether another prompt is shown. <br />
<br />
== Environments ==<br />
Testing will be performed on following devices: <br />
* Phones<br />
** 4.x<br />
** 5.x<br />
** 6.0<br />
* Tablet<br />
** 4.x<br />
** 5.x<br />
** 6.0<br />
<br />
== Specifications ==<br />
* "how to bookmark" helper UI is displayed <br />
<br />
== User stories ==<br />
*As a user, I want to be informed how to add items to reading list, after entering reader view since the "Add to RL" icon is now missing.<br />
<br />
== Acceptance Criteria==<br />
*A prompt is shown, after user hits reader view<br />
<br />
= Testing details =<br />
==Date:05-09-2016==<br />
- [https://bugzilla.mozilla.org/show_bug.cgi?id=1300532 Bug 1300532] Contextual hint about offline bookmarks is displayed in normal view instead of reader view<br />
*[[File:reader view.png|600px|thumb|center| Prompt]]<br />
==Date:19-09-2016==<br />
*Device: One A2001(Android 6.0)<br />
*Build: Firefox for Android 52.0a1 (2016-09-19)<br />
*Load an article from news.google.com and tap the reader view icon from the URL Bar<br />
**the page enters reader view and a prompt is displayed: "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks"<br />
*Tap the "Add to Bookmarks" button.<br />
**the second prompt is displayed: "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks".<br />
==Date:21-09-2016==<br />
*Device: One A2001 (Android 6.0)<br />
*Build: Firefox for Android 50 Beta 1<br />
*After tapping the reader view icon from the URL Bar, the page enters reader view and a prompt is displayed: "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks"<br />
Tapping the "Add to Bookmarks" button, the second prompt is displayed: "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks".<br />
==Date:22-09-2016==<br />
*Device: One A2001 (Android 6.0)<br />
*Build: Firefox for Android 51.0a2 (2016-09-21)<br />
*After tapping the reader view icon from the URL Bar, the page enters reader view, but no prompt is displayed. If I open the menu and tap the bookmark icon, then "Read offline. Find your Reader View items in Bookmarks, even offline. Go to Bookmarks" prompt is displayed. But the prompt "Available offline. Bookmark Reader View items to read them offline. Add to Bookmarks" is never displayed.<br />
<br />
=Bug Work=<br />
==Tracking bugs==<br />
* bugs to track the feature<br />
ex:<br />
<onlyinclude><br />
<bugzilla><br />
{<br />
"id": "1275784, migrate-RL, 1234314, 1300532"<br />
}<br />
</bugzilla><br />
</onlyinclude><br />
<br />
==Still issues==<br />
<font color="red">'''[NEW]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id= Bug ] - Contextual hint about offline bookmarks is not displayed in Aurora <br/><br />
<br />
===Bug fixed ===<br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1270880 Bug 1270880] - Update "how to bookmark" helper UI to "first time" instead of "third time" <br/><br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1275784 Bug 1275784] - Enable reader view bookmark hint up to beta <br/><br />
<font color="green">'''[RESOLVED FIXED]'''</font> [https://bugzilla.mozilla.org/show_bug.cgi?id=1300532 Bug 1300532] - Contextual hint about offline bookmarks is displayed in normal view instead of reader view <br/><br />
<br />
<br />
<br />
=Signoff=<br />
== Criteria ==<br />
* All test cases should be executed<br />
* All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed<br />
<br />
== Results ==<br />
'''Nightly testing'''<br />
-Contextual hint about offline bookmarks is not displayed.<br />
<br />
'''Aurora testing'''<br />
-Contextual hint about offline bookmarks is not displayed.<br />
<br />
'''Beta testing'''<br />
-Contextual hint about offline bookmarks is not displayed.</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/Fennec/49&diff=1149504QA/Fennec/492016-09-28T12:01:22Z<p>Teodora.Vermesan: /* Features Status */</p>
<hr />
<div>{{LastUpdated}}<br />
{{TOC_limit|3}}<br />
<br />
=== Schedule ===<br />
* '''[[Mobile/Roadmap | Tracking Fx49]]'''<br />
* Nightly: <br />
* Aurora: <br />
* Beta: <br />
* Release: <br />
<br />
=== Features Status ===<br />
<br />
{| class="wikitable" width=100%<br />
! Feature<br />
! QA Owner<br />
! Tracking Bug<br />
! Documentation/Test Plan<br />
! Feature Health Nightly<br />
! Feature Health Aurora<br />
! Feature Health Beta<br />
|-<br />
| Contextual hint about offline bookmarks first time user enters reader view<br />
| Teodora Vermesan<br />
| {{Bug|1275784}} <br />
| [https://wiki.mozilla.org/QA/Fennec/First_time_reader_view_prompt_evaluation Testplan]<br />
| {{mok}}<br />
| {{mrisk}}<br />
| {{mok}}<br />
|- <br />
| Reading List smart folder should indicate # of items inside<br />
| Teodora Vermesan<br />
| {{Bug|1269001}} <br />
| [https://wiki.mozilla.org/QA/Fennec/Reading_List_smart_folder_should_indicate_number_of_items_inside Testplan]<br />
| {{mok}}<br />
| {{mok}}<br />
| {{mok}}<br />
|- <br />
| Add Amazon product search suggestions to Awesome Screen<br />
| Mihai Ninu<br />
| {{Bug|851969}} <br />
| [https://wiki.mozilla.org/QA/Fennec/Add_Amazon_product_search_suggestions_to_Awesome_Screen Testplan]<br />
| {{mok}}<br />
| {{mok}}<br />
| {{mok}}<br />
|- <br />
| Control media content when switching between apps<br />
| Sorina Florean<br />
| {{Bug|1240423}} <br />
| [https://wiki.mozilla.org/QA/Fennec/Control_media_content_when_switching_between_apps Testplan]<br />
| {{mok}}<br />
| {{mok}}<br />
| NA<br />
|-<br />
| Feature-focused first-run experiment<br />
| Sorina Florean<br />
| {{Bug|1268641}} <br />
| [https://wiki.mozilla.org/QA/Fennec/Feature-focused_first-run_experiment Testplan]<br />
| {{mok}}<br />
| {{mok}}<br />
| {{mok}}<br />
|-<br />
| <s> Exclude Desktop-only history from Top Sites </><br />
| Mihai Ninu<br />
| {{Bug|1046709}}<br />
| [https://wiki.mozilla.org/QA/Fennec/Prioritizatization_of_mobile_browsing_history_over_synced_desktop_history Testplan]<br />
| {{mok}}<br />
| {{mok}}<br />
| NA<br />
|-<br />
| Show cached pages if available offline<br />
| Teodora Vermesan<br />
| {{Bug|935190}}<br />
| [https://wiki.mozilla.org/QA/Fennec/Add_option_to_load_cached_pages_when_offline Testplan]<br />
| {{mok}} <br />
| {{mok}} <br />
| {{mok}}<br />
|-<br />
| Attempt to re-upload Telemetry documents that failed to upload<br />
| NA<br />
| {{Bug|1243585}} <br />
| NA<br />
| NA<br />
| NA<br />
| NA<br />
|- <br />
| Core ping to include time spent<br />
| Mihai Pop<br />
| {{Bug|1243595}} <br />
| [https://wiki.mozilla.org/QA/Fennec/Core_pings Testplan]<br />
| {{mok}} <br />
| {{mok}} <br />
| {{mok}}<br />
|- <br />
| Core ping to include search counts<br />
| Mihai Pop<br />
| {{Bug|1253319}} <br />
| [https://wiki.mozilla.org/QA/Fennec/Core_pings Testplan]<br />
| {{mok}} <br />
| {{mok}} <br />
| {{mok}}<br />
|-<br />
| Updated default favicons<br />
| Sorina Florean<br />
| {{Bug|1265712}} <br />
| [https://wiki.mozilla.org/QA/Fennec/Improve_website_icon_quality Testplan]<br />
| {{mok}}<br />
| {{mok}}<br />
| {{mok}}<br />
|-<br />
| Added locale(s): Georgian (ka),Lao (lo)<br />
| Ioana Chiorean<br />
| {{Bug|1256674}}{{Bug|1213064}}<br />
| [https://wiki.mozilla.org/QA/Fennec/Locales_Georgian_Lao Testplan]<br />
| N/A<br />
| N/A<br />
| N/A<br />
|-<br />
| Push notification in Fennec<br />
| Ioana Chiorean<br />
| {{Bug|1206207}}<br />
| [https://wiki.mozilla.org/QA/Fennec/Push_notifications Testplan]<br />
| {{mok}}<br />
| {{mok}}<br />
| {{mok}}<br />
|-<br />
|}<br />
<br />
===Aurora===<br />
* [https://wiki.mozilla.org/QA/Fennec/49/Aurora/SignOff SignOff]<br />
<br />
=== Beta ===<br />
* [https://wiki.mozilla.org/QA/Fennec/49/Beta Beta Status]<br />
** [https://wiki.mozilla.org/QA/Fennec/49/Beta/1 Beta 1]<br />
** [https://wiki.mozilla.org/QA/Fennec/49/Beta/2 Beta 2]<br />
** [https://wiki.mozilla.org/QA/Fennec/49/Beta/4 Beta 4]<br />
** [https://wiki.mozilla.org/QA/Fennec/49/Beta/6 Beta 6]<br />
** [https://wiki.mozilla.org/QA/Fennec/49/Beta/8 Beta 8]<br />
** [https://wiki.mozilla.org/QA/Fennec/49/Beta/10 Beta 10]<br />
<br />
=== Release Candidate === <br />
* [https://wiki.mozilla.org/QA/Fennec/49/RC RC 1]<br />
<br />
== Meetings ==<br />
{| class="wikitable" width="100%"<br />
|-<br />
! Meeting<br />
! Purpose<br />
! When<br />
|-<br />
| [[CrashKill|Crashkill]]<br />
| Discuss urgent concerns with stability (ie. crashes)<br />
| Every Monday at 10:00 AM Pacific<br />
|-<br />
| [[Mobile/ProductPlanning|Product Planning]]<br />
| Discuss concerns about feature development and/or schedule<br />
| Every Tuesday at 9:00 AM Pacific<br />
|-<br />
| [https://etherpad.mozilla.org/channel-mtg-agenda Release Coordination]<br />
| Raise issues of utmost importance to the Release Managers<br />
| Every Tuesday & Thursday at 10:00 AM Pacific<br />
|-<br />
| [[Mobile/Notes|Development]]<br />
| Discuss concerns with development<br />
| Every Wednesday at 9:30 AM Pacific<br />
|-<br />
| [[Mobile/Triage|Mobile Triage]]<br />
| Nominate bugs to get developer attention<br />
| Every Thursday at 10:00 AM Pacific<br />
|-<br />
| [https://etherpad.mozilla.org/weekly-mobileQA-standup-q3 Quality Engineering]<br />
| Discuss concerns with the Support and Project teams<br />
| Every Thursday at 1:30 PM Pacific<br />
|-<br />
|}</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/Fennec/50/Beta/2/BugVerification&diff=1149423QA/Fennec/50/Beta/2/BugVerification2016-09-27T15:55:55Z<p>Teodora.Vermesan: /* QA Assignment */</p>
<hr />
<div>== QA Assignment ==<br />
<onlyinclude><br />
{| class="wikitable" width=100%<br />
! Assigned <br />
! Completed<br />
! Results<br />
|-<br />
| Teodora Vermesan<br />
| September 27th <br />
| '''Done'''<br />
|-<br />
|} <br />
</onlyinclude><br />
<br />
== Results ==<br />
* Bugs Verified:<br />
**{{Bug|1304052}} - The fullscreen videos are zoomable<br />
**{{Bug|1130739}} - Android crash in glGetInternalformativ on Mali-450 MP & 400 MP - could not reproduce<br />
**{{Bug|1301593}} - Firefox mispositions touch/hover and displays a black bar when urlbar is visible and Firefox is a smaller multiwindow using Samsung Touchwiz - could not reproduce<br />
**{{Bug|1288446}} - Crash in libGLESv2_POWERVR_SGX540_120.so@0x4d88 - could not reproduce</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/Fennec/50/Beta/2/BugVerification&diff=1149421QA/Fennec/50/Beta/2/BugVerification2016-09-27T15:53:05Z<p>Teodora.Vermesan: /* Results */</p>
<hr />
<div>== QA Assignment ==<br />
<onlyinclude><br />
{| class="wikitable" width=100%<br />
! Assigned <br />
! Completed<br />
! Results<br />
|-<br />
|<br />
|<br />
|<br />
|-<br />
|} <br />
</onlyinclude><br />
<br />
== Results ==<br />
* Bugs Verified:<br />
**{{Bug|1304052}} - The fullscreen videos are zoomable<br />
**{{Bug|1130739}} - Android crash in glGetInternalformativ on Mali-450 MP & 400 MP - could not reproduce<br />
**{{Bug|1301593}} - Firefox mispositions touch/hover and displays a black bar when urlbar is visible and Firefox is a smaller multiwindow using Samsung Touchwiz - could not reproduce<br />
**{{Bug|1288446}} - Crash in libGLESv2_POWERVR_SGX540_120.so@0x4d88 - could not reproduce</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/Fennec/50/Beta/2/BugVerification&diff=1149418QA/Fennec/50/Beta/2/BugVerification2016-09-27T15:44:45Z<p>Teodora.Vermesan: /* Results */</p>
<hr />
<div>== QA Assignment ==<br />
<onlyinclude><br />
{| class="wikitable" width=100%<br />
! Assigned <br />
! Completed<br />
! Results<br />
|-<br />
|<br />
|<br />
|<br />
|-<br />
|} <br />
</onlyinclude><br />
<br />
== Results ==<br />
* Bugs Verified:<br />
**{{Bug|1304052}} - The fullscreen videos are zoomable</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/Fennec/50/Beta/2/smoketests-results&diff=1149416QA/Fennec/50/Beta/2/smoketests-results2016-09-27T15:39:35Z<p>Teodora.Vermesan: /* QA Assignment */</p>
<hr />
<div>== QA Assignment ==<br />
<onlyinclude><br />
{| class="wikitable" width=100%<br />
! Assigned<br />
! API type<br />
! Device<br />
! Completed<br />
! Results<br />
|-<br />
| Sorina Florean<br />
| 15<br />
| Asus Transformer Pad (Android 4.2.1)<br />
| September 27th<br />
| '''PASS'''<br />
|-<br />
| Mihai Ninu<br />
| 15<br />
| Samsung Galaxy S6 EDGE (Android 6.0)<br />
| September 27th<br />
| '''PASS'''<br />
|-<br />
| Alex Caziuc<br />
| x86<br />
| Xiaomi mi Pad 2 (Android 5.1)<br />
| September 27th<br />
| '''PASS'''<br />
|-<br />
| Mihai Pop<br />
| 15<br />
| Nexus 6P (Android 7.0)<br />
| September 27th<br />
| '''PASS'''<br />
|-<br />
| Teodora Vermesan<br />
| 15<br />
| Moto X (Android 4.4)<br />
| September 27th<br />
| '''PASS'''<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|} <br />
</onlyinclude><br />
<br />
== Results ==<br />
===SmokeTests detailed results===<br />
* We tried an experiment today and you can see the smoke results <br />
<br />
=== Issues===<br />
*'''New'''<br />
*'''New to this Beta'''<br />
*'''Important issue:'''<br />
*'''Known Issues:'''<br />
**{{Bug|1266594}} - "Clear private data on exit" should work<br />
**{{Bug|1206620}} - Zoom out does not work at double tap action in Landscape mode on Tablet devices<br />
**{{Bug|1302414}} - Theme preview is not working on tablets</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/Fennec/51/Aurora/SignOff/bft-results&diff=1148735QA/Fennec/51/Aurora/SignOff/bft-results2016-09-22T14:07:28Z<p>Teodora.Vermesan: /* QA Assignment */</p>
<hr />
<div>== QA Assignment ==<br />
<br />
<onlyinclude><br />
{| class="wikitable" width=100%<br />
! Assigned<br />
! API type<br />
! Device<br />
! Completed<br />
! Results<br />
|-<br />
| Ioana Chiorean<br />
| API 15<br />
| Nexus 9 (Android 6.0.1)<br />
| Sept 21st<br />
| '''in progress'''<br />
|-<br />
| Sorina Florean<br />
| API 15<br />
| Asus Transformer Pad (Android 4.2.1)<br />
| Sept 21st<br />
| '''in progress'''<br />
|-<br />
| Ninu Mihai<br />
| API 15<br />
| Samsung Galaxy S6 EDGE (Android 6.0)<br />
| Sept 21st<br />
| '''in progress'''<br />
|-<br />
| Teodora Vermesan<br />
| API 15<br />
| Xiaomi mi4i (Android 5.0,2)<br />
| Sept 20th<br />
| '''PASS'''<br />
|-<br />
| Mihai Pop<br />
| API 15<br />
| Nexus 6P (Android 7.0)<br />
| Sept 20th<br />
| '''in progress'''<br />
|-<br />
| Alex Caziuc<br />
| x86<br />
| Xiaomi mi Pad 2 (Android 5.1.1)<br />
| Sept 20th<br />
| '''in progress'''<br />
|} <br />
</onlyinclude><br />
<br />
== Results ==<br />
<br />
=== Issues ===<br />
*'''Issues''':<br />
** '''New''':<br />
** '''Known issues but severe ones''':<br />
** '''Known issues''':<br />
**{{bug|443564}} - Implement window.toStaticHTML <br />
**{{bug|446344}} - Implement Origin header CSRF mitigation</div>Teodora.Vermesanhttps://wiki.mozilla.org/index.php?title=QA/Fennec/50/Beta/1/BugVerification&diff=1148590QA/Fennec/50/Beta/1/BugVerification2016-09-21T14:47:31Z<p>Teodora.Vermesan: /* Results */</p>
<hr />
<div>== QA Assignment ==<br />
<onlyinclude><br />
{| class="wikitable" width=100%<br />
! Assigned <br />
! Completed<br />
! Results<br />
|-<br />
| Teodora Vermesan<br />
| Sep 21st<br />
| '''Done'''<br />
|-<br />
|} <br />
</onlyinclude><br />
<br />
== Results ==<br />
* Bugs Verified:<br />
**{{Bug|1282410}} - Using external app to open unsupported type media<br />
**{{Bug|1293650}} - Download notification: Pause/Cancel button not working<br />
**{{Bug|1300532}} - Contextual hint about offline bookmarks is displayed in normal view instead of reader view<br />
**{{Bug|1278390}} - Fennec doesn't display Gitter.im content, after scrolling up/down</div>Teodora.Vermesan