QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 1: Line 1:
== Read Me First! ==
== Read Me First! ==
* Run a quick testsuite of daily browsed sites
# Run a quick testsuite of daily browsed sites
* Next, sign up to test [https://wiki.mozilla.org/QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday#Fx3.5_Feature_Testing feature testing] under the "Testers" list
# Next, sign up to test [https://wiki.mozilla.org/QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday#Fx3.5_Feature_Testing feature testing] under the "Testers" list
** Try to make a concerted effort to sign up for something you're not comfortable with
** Try to make a concerted effort to sign up for something you're not comfortable with
** People are free to "sign up" for <b>more than one feature</b> if they like
** People are free to "sign up" for <b>more than one feature</b> if they like
** The onus is on learning new features for those that haven't tried them out <b>as well as</b> using these features together to find deeper critical/blocker bugs
** The onus is on learning new features for those that haven't tried them out <b>as well as</b> using these features together to find deeper critical/blocker bugs
** Example: "aakashd" signed up for Tab testing is shown [https://wiki.mozilla.org/QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday#Fx3.5_Feature_Testing here]
** Example: "aakashd" signed up for Tab testing is shown [https://wiki.mozilla.org/QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday#Fx3.5_Feature_Testing here]
* For any bugs found, add "[MoCoTestday]" to its whiteboard
# For any bugs found, add "[MoCoTestday]" to its whiteboard
** If you're unsure it's a bug, go to the #testday channel (check out [https://wiki.mozilla.org/QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday#Communication Communication] for more info)
** If you're unsure it's a bug, go to the #testday channel (check out [https://wiki.mozilla.org/QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday#Communication Communication] for more info)
* To do more testing, take a look at: [https://wiki.mozilla.org/QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday#Addtl._Resource_Testing Addtl. Resource Testing]
# To do more testing, take a look at: [https://wiki.mozilla.org/QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday#Addtl._Resource_Testing Addtl. Resource Testing]


== Supplementary Information ==
== Supplementary Information ==

Revision as of 22:23, 8 June 2009

Read Me First!

  1. Run a quick testsuite of daily browsed sites
  2. Next, sign up to test feature testing under the "Testers" list
    • Try to make a concerted effort to sign up for something you're not comfortable with
    • People are free to "sign up" for more than one feature if they like
    • The onus is on learning new features for those that haven't tried them out as well as using these features together to find deeper critical/blocker bugs
    • Example: "aakashd" signed up for Tab testing is shown here
  1. For any bugs found, add "[MoCoTestday]" to its whiteboard
    • If you're unsure it's a bug, go to the #testday channel (check out Communication for more info)
  1. To do more testing, take a look at: Addtl. Resource Testing

Supplementary Information

When and Where?

  • date: Thursday, June 11
  • time: tba
  • location: on the #testday channel (via irc.mozilla.org) and/or in-house @ Mountain View

Communication

  • For general questions: irc: #testday channel
    • primary contacts: timr, tchung, juanb, aakashd
  • When testing on Fx3.5 features, go to their corresponding

Reference Guides

Testing

Daily Browsing Testing

Fx3.5 Feature Testing

Addtl. Resource Testing

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday&oldid=147897"