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

TestEngineering/UI/AMO/Testday/09012010 (view source)

Revision as of 18:24, 31 August 2010

233 bytes added , 31 August 2010

no edit summary

Krupa

Confirmed users

1,477

edits

@@ Line 3: / Line 3: @@
 Staging server: [https://preview.addons.mozilla.org/en-US/firefox/ https://preview.addons.mozilla.org/en-US/firefox/]
-'''<u> What are we testing? </u>'''
+'''<u>What are we testing?</u>'''
-The focus for this testday are the new [https://preview.addons.mozilla.org/en-US/firefox/collections/ Collections] pages.
+The focus for this testday are the changes for 5.11.9 which includes-
-'''<u>What are Collections?</u>'''
+*The new [https://preview.addons.mozilla.org/en-US/firefox/collections/ Collections] pages.
+*View/Edit Profile pages
+*Password reset page
+*User Registration and Verification
-Collections are groups of related add-ons created by users to share.
+'''<u>What are Collections?</u>'''
-'''<u>What to test?</u>'''
+Collections are groups of related add-ons created by users to share.
-Here are a few things you could check for:<br>
+'''<u>What to test?</u>'''
-*Functionality - a Feature does what it is supposed to do.<br>
+Here are a few things you could check for:<br>
-*Layout issues<br>
-*Usability (does something not make sense? seem hard to use?)<br>
+*Functionality - a Feature does what it is supposed to do.<br>
-*[https://wiki.mozilla.org/WebAppSec/Secure_Coding_QA_Checklist Security] - XSS,encoding/escaping issues, etc.<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://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
-* Collection sorts
-'''<u>Litmus test-run for new Collections:</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
-You can run our testrun for Collections [https://litmus.mozilla.org/run_tests.cgi?test_run_id=194 here]
+'''<u>Litmus test-run for new Collections:</u>'''
-You can also help us do end-to-end testing by running the testruns listed below:
+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>
@@ Line 44: / Line 55: @@
 <br>
 '''<u>What *not* to worry about?</u>'''<br>
-* 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
+*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
 '''<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>
@@ Line 55: / Line 67: @@
 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 [testday09012010] to the status whiteboard; thanks!
 <br>
@@ Line 61: / Line 73: @@
 <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>