TestEngineering/UI/AMO/Testday/09012010: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "Hello there, and welcome to the AMO test day! Thanks for volunteering your time and energy to help us improve addons.mozilla.org! Below, you'll find the setup information and som...")
 
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Hello there, and welcome to the AMO test day! Thanks for volunteering your time and energy to help us improve addons.mozilla.org! Below, you'll find the setup information and some use-cases to help guide you in your testing; feel free, though, to go off on your own and just ad-hoc test!  
Hello there, and welcome to the AMO test day! Thanks for volunteering your time and energy to help us improve addons.mozilla.org! Below, you'll find the setup information and some use-cases to help guide you in your testing; feel free, though, to go off on your own and just ad-hoc test!  


Staging server: [https://preview.addons.mozilla.org/en-US/firefox/ https://preview.addons.mozilla.org/en-US/firefox/]  
Staging server: [https://next.addons.mozilla.org/en-US/firefox/ https://next.addons.mozilla.org/en-US/firefox/]  


'''<u> What are we testing></u>'''
'''<u>What are we testing?</u>'''  


The focus for this testday is the new
The focus for this testday are the changes for 5.11.9 which includes-
[https://preview.addons.mozilla.org/en-US/firefox/faq#collections Collections].


So, here are a few things you could check for:<br>
*The new [https://next.addons.mozilla.org/en-US/firefox/collections/ Collections] pages.
*View/[https://next.addons.mozilla.org/en-US/firefox/users/edit Edit Profile] pages
*[https://next.addons.mozilla.org/en-US/firefox/users/pwreset Password reset] page
*User Registration and Verification


* Layout Issues
'''<u>What are Collections?</u>'''
* Functionality works as expected
* Security/Privacy issues
* Localization
* Usability issues


'''Pages/features to be tested'''
Collections are groups of related add-ons created by users to share.  
* [https://preview.addons.mozilla.org/en-US/firefox/collections Collection landing page]
* [https://preview.addons.mozilla.org/en-US/firefox/collections/add Collection Creation]
* Edit/Delete Collection
* Privacy setting for Collections
* Multiple Install for collections
* Transferring  Owners


Litmus test-run for new Collections:
'''<u>What to test?</u>'''


Here are a few things you could check for:<br>


You can also help us do end-to- end testing by running the testruns listed below:
*Functionality - a Feature does what it is supposed to do.<br>
*Layout issues<br>
*Usability (does something not make sense? seem hard to use?)<br>
*[https://wiki.mozilla.org/WebAppSec/Secure_Coding_QA_Checklist Security] - XSS,encoding/escaping issues, etc.<br>
*Error handling - System fails gracefully and displays useful and appropriate user/error messages<br>
 
'''<u>Pages/features to be tested</u>'''
 
*[https://next.addons.mozilla.org/en-US/firefox/collections Collection landing page]
*[https://next.addons.mozilla.org/en-US/firefox/collections/add Collection Creation]
*Edit/Delete Collection
*Privacy setting for Collections
*Multiple Install for collections
*Transferring Owners
*Collection sorts
*View Profile Page
*Edit profile page
*Registration/Verification
*Password reset page
*Collection Search
 
'''<u>Litmus test-run for new Collections:</u>'''
 
You can run our testrun for Collections [https://litmus.mozilla.org/run_tests.cgi?test_run_id=194 here]
 
You can also help us do end-to-end testing by running the testruns listed below:  


*[https://litmus.mozilla.org/run_tests.cgi?test_run_id=105 Testrun for AMO Public pages] - Includes testcases to validate user functionalities like adding add-on reviews,updating user profile etc. Don't forget to spiral around&nbsp; scenarios to check for edge-cases.<br>  
*[https://litmus.mozilla.org/run_tests.cgi?test_run_id=105 Testrun for AMO Public pages] - Includes testcases to validate user functionalities like adding add-on reviews,updating user profile etc. Don't forget to spiral around&nbsp; scenarios to check for edge-cases.<br>  
Line 37: Line 55:
<br>  
<br>  


'''<u>If you prefer to do ad-hoc testing, then:</u>'''<br>  
'''<u>What *not* to worry about?</u>'''<br>  
 
''What to test?''<br>
 


*Functionality-a Feature does what it is supposed to do.<br>*Layout-no overlap or visibility issues<br>*Usability (does something not make sense? seem hard to use?)<br>*Security-XSS,encoding/escaping issues etc<br>*Error handling- System fails gracefully and displays useful and appropriate user/error messages'''<u></u>'''<p>
*Don't worry about -261 or -203 errors when trying to install an add-on; the preview server doesn't always have the most up-to-date files synced to it from the production database
''What *not* to worry about?''<br>
* Don't worry about -261 errors when trying to install an add-on; the preview server doesn't always have the most up-to-date files synced to it from the production database


'''<u>You found a bug!</u>'''
'''<u>You found a bug!</u>'''  


Awesome! First thing you need to do is to check whether it's a known issue. You can search for existing AMO bugs [https://bugzilla.mozilla.org/query.cgi here]<br>  
Awesome! First thing you need to do is to check whether it's a known issue. You can search for existing AMO bugs [https://bugzilla.mozilla.org/query.cgi here]<br>  


If you found a new/un-reported bug, give yourself a pat on the back and then please file the bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org here] <br>  
If you found a new/un-reported bug, give yourself a pat on the back and then please file the bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org here] <br>  


If the process of filing a bug seems too daunting a task or if you are not sure whether something is a bug or not, then find someone in #testday channel on IRC to help you.<br>  
If the process of filing a bug seems too daunting a task or if you are not sure whether something is a bug or not, then find someone in [irc://irc.mozilla.org/testday #testday] channel on [http://irc.mozilla.org IRC] to help you.<br>  


Also, if you have permissions, please add [amotestday] to the status whiteboard; thanks!
Also, if you have permissions, please add [testday09012010] to the status whiteboard; thanks!  


<br>  
<br>  
Line 61: Line 73:
<u>'''You want to do more'''</u><br>  
<u>'''You want to do more'''</u><br>  


Thanks for your interest in further testing our websites here at Mozilla! For an overview and ways to engage with us, please see [https://wiki.mozilla.org/QA/Execution/Web_Testing/Contribute https://wiki.mozilla.org/QA/Execution/Web_Testing/Contribute]. If you have any questions along the way, the best way to reach the team is via IRC, in [irc://irc.mozilla.org/#mozwebqa #mozwebqa], on irc.mozilla.org. [https://wiki.mozilla.org/QA/Execution/Web_Testing#The_Team_.2F_Contact_Info Here are some instructions] for those of you new to IRC.
Thanks for your interest in further testing our websites here at Mozilla! For an overview and ways to engage with us, please see [https://wiki.mozilla.org/QA/Execution/Web_Testing/Contribute https://wiki.mozilla.org/QA/Execution/Web_Testing/Contribute]. If you have any questions along the way, the best way to reach the team is via IRC, in [irc://irc.mozilla.org/#mozwebqa #mozwebqa], on irc.mozilla.org. [https://wiki.mozilla.org/QA/Execution/Web_Testing#The_Team_.2F_Contact_Info Here are some instructions] for those of you new to IRC.  


<u>'''Contact us'''</u><br>  
<u>'''Contact us'''</u><br>  

Latest revision as of 20:33, 26 August 2016

Hello there, and welcome to the AMO test day! Thanks for volunteering your time and energy to help us improve addons.mozilla.org! Below, you'll find the setup information and some use-cases to help guide you in your testing; feel free, though, to go off on your own and just ad-hoc test!

Staging server: https://next.addons.mozilla.org/en-US/firefox/

What are we testing?

The focus for this testday are the changes for 5.11.9 which includes-

What are Collections?

Collections are groups of related add-ons created by users to share.

What to test?

Here are a few things you could check for:

  • Functionality - a Feature does what it is supposed to do.
  • Layout issues
  • Usability (does something not make sense? seem hard to use?)
  • Security - XSS,encoding/escaping issues, etc.
  • Error handling - System fails gracefully and displays useful and appropriate user/error messages

Pages/features to be tested

  • Collection landing page
  • Collection Creation
  • Edit/Delete Collection
  • Privacy setting for Collections
  • Multiple Install for collections
  • Transferring Owners
  • Collection sorts
  • View Profile Page
  • Edit profile page
  • Registration/Verification
  • Password reset page
  • Collection Search

Litmus test-run for new Collections:

You can run our testrun for Collections here

You can also help us do end-to-end testing by running the testruns listed below:

  • Testrun for AMO Public pages - Includes testcases to validate user functionalities like adding add-on reviews,updating user profile etc. Don't forget to spiral around  scenarios to check for edge-cases.
  • Testrun for AMO Search - Includes testcases to test Search functionality on AMO. Don't forget to spiral around scenarios to check for edge-cases.
  • Testrun for Add-on Collector - Includes testcases to check for the extension Add-on Collector. Learn more about Add-on Collector here
  • Testrun for AMO Tagging - Includes testcases to validate tagging add-ons. Don't forget to spiral around scenarios to check for edge-cases.
  • Testrun for Button-states - Includes testcases to test the different button-states on AMO.


What *not* to worry about?

  • Don't worry about -261 or -203 errors when trying to install an add-on; the preview server doesn't always have the most up-to-date files synced to it from the production database

You found a bug!

Awesome! First thing you need to do is to check whether it's a known issue. You can search for existing AMO bugs here

If you found a new/un-reported bug, give yourself a pat on the back and then please file the bug here

If the process of filing a bug seems too daunting a task or if you are not sure whether something is a bug or not, then find someone in #testday channel on IRC to help you.

Also, if you have permissions, please add [testday09012010] to the status whiteboard; thanks!


You want to do more

Thanks for your interest in further testing our websites here at Mozilla! For an overview and ways to engage with us, please see https://wiki.mozilla.org/QA/Execution/Web_Testing/Contribute. If you have any questions along the way, the best way to reach the team is via IRC, in #mozwebqa, on irc.mozilla.org. Here are some instructions for those of you new to IRC.

Contact us

Aakash Desai

Krupa Raj

Stephen Donner

Retrieved from "https://wiki.allizom.org/index.php?title=TestEngineering/UI/AMO/Testday/09012010&oldid=1145904"