Compatibility/Lessons Learned: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎What went well:: added item)
(→‎What needs improvement:: Edited title, added items)
 
Line 13: Line 13:
* weekly status emails
* weekly status emails


==== What needs improvement: ====
==== What can go better: ====


* in depth understanding of the “Non-Compat” philosophy
* in depth understanding of the “Non-Compat” philosophy
Line 19: Line 19:
* understanding of HTML/CSS/JS
* understanding of HTML/CSS/JS
* getting more familiar with HTML debugging
* getting more familiar with HTML debugging
* labeling the issues (e.g firefox-mobile)
* ask for help when needed
* add resolution of the used device for testing (e.g Android 6.0.1 - Resolution 1080 x 1920 pixels (~445 ppi pixel density))


==== Items not tested: ====
==== Items not tested: ====

Latest revision as of 06:43, 28 April 2017

Lessons Learned

We’ve worked on structuring some relevant items counted as Lessons Learned during the testing cycle performed on the First 100 EN web sites.

Here are the testing team’s conclusions:

What went well:

  • understanding the ways of working
  • good testing progress on the first 100 EN sites
  • good contribution on clarifying the logged issues
  • good collaboration with the team
  • weekly status emails

What can go better:

  • in depth understanding of the “Non-Compat” philosophy
  • gathering items to be tested (continuous process)
  • understanding of HTML/CSS/JS
  • getting more familiar with HTML debugging
  • labeling the issues (e.g firefox-mobile)
  • ask for help when needed
  • add resolution of the used device for testing (e.g Android 6.0.1 - Resolution 1080 x 1920 pixels (~445 ppi pixel density))

Items not tested:

  • UI issues reproducible on all Browsers (e.g. Firefox vs Chrome)
  • broken functionality reproducible on all Browsers
  • crashes
  • web sites with no mobile support
  • mobile web sites redirect to desktop pages
  • services available only through a dedicated application

Types of issues encountered:

  • mostly UI issues on all web-sites
  • few plugin issues (e.g. video doesn’t play)

Notes:

We’ve encountered several web sites that we were not able to perform in-depth testing due to:


1) Web sites that need Special accounts (Banking, Insurance):

www.capitalone.com

www.wellsfargo.com

www.bankofamerica.com

www.chase.com

www.citi.com


2) Web sites that need special information for account creation (US address, US phone number, SSN, Private/Public institution account)

www.xfinity.com

www.microsoftonline.com


3) Desktop site only

www.salesforce.com

www.stackexchange.com

www.irs.gov


4) Inaccessibility

www.ndt.tv