QA/IAM/TestPlan: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
Line 10: Line 10:
*auth0 will replace persona
*auth0 will replace persona
== Scope of Testing ==  
== Scope of Testing ==  
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.
*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.
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.
*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.
 
== General Test Information ==
== General Test Information ==
=== Links and Documentation ===  
=== Links and Documentation ===  

Revision as of 08:40, 5 October 2016

Overview

This test plan covers the general weekly testing that will happen against 'Identity and Access Management' product in the Stage Test environment. The goal is to ensure a defined and consistent amount of quality and usability in the server side and client side.

Strategy

Identity and Access Management work:

  • aligned with IT on a common plan
  • identified replacement for persona
  • outlined future integration of LDAP with mozillians.org
  • auth0 will replace persona

Scope of Testing

  • 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.
  • 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.

General Test Information

Links and Documentation

Weekly Test Schedules

  • Unknown yet

Weekly Meetings

  • Participation Systems Standup: every Tuesday, Thursday from 5pm to 5:15pm in Pierros's Vydio
  • Sprint Review / Retro / Planning: every Monday from 3pm to 5:30pm in Henrik's Vidyo

Email and IRC

  • Post to this email List:
    • parsys@mozilla.com
  • Or post to the Google Group:
  • Post to IRC:
      1. parsys
  • Team:
    • Henrik Mitsch: hmitsch
    • Arielle:currently not on the team, will be back 01 JAN 2017
    • John Giannelos
      • development on reps.mozilla.org, mozillians.org and supporting the infrastructure
      • nemo-yiannis
    • Nikos Roussos
      • front-end
      • nikos
    • Pierros Papadeas
      • pierros
      • eng management for the team
    • Anastasios Katsoulas
      • web dev on mozillians
      • tasos
    • Yousef Alam
      • yalam96
      • new infrastructure + community websites
    • Teodora Vermesan
      • TeoVermesan
      • QA Engineer
    • Ioana Chiorean - Release QA Mobile Team Lead
    • Florin Mezei - Project Manager (Release QA, WebQA, BuildDuty)
      • Ioana and Florin will provide support to Teodora as we define the testing needed on the project

Bugs and Open Issues

  • Bugzilla: mozillians & reps
  • Github: mozmoderator

==Client and Server Test Environments

Supported OS and Browsers

  • All information about supported platforms, operating systems, browsers, mobile devices will be kept in a Google doc spreadsheet

Major Test Areas

QA Sign-Off for Stage

  • Requirements and procedures:
    • 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.

QA Testing for Production

QA Sign-Off for Production