QA/Waverley/Developer-Tools/StyleInspector/Test-plan: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
Line 16: Line 16:
**Bug verifications and bug triage  
**Bug verifications and bug triage  


*Conduct testday activities with Mozilla QA and the community  
*Conduct testday activities with Mozilla QA and the community
 
*Verify the integration with the other devtools features 
 
*


= Platform and Configurations =
= Platform and Configurations =

Revision as of 13:50, 20 July 2011

Overview

  • Guidance in testing the new StyleInspector feature present in Firefox.

Strategy

  • Creating new testcases for Litmus
  • Keep testcases up-to-date considering development cycle shifts
  • Keep up with dev team
    • Find bugs used for tracking the development process
    • Follow up with the pushlog to stay informed with the latest changes
  • Bug triage and regression searching
    • Heavy regression hunting
    • Bug verifications and bug triage
  • Conduct testday activities with Mozilla QA and the community
  • Verify the integration with the other devtools features

Platform and Configurations

  • Testing against the StyleInspector is to be performed on all platforms
    • Prioritizing
      • Windows 7, Windows XP
      • Windows 2000 spot checks when time permits
      • MAC OS X
      • LINUX

Schedule/milestones

(eg. Builds, merge, etc.)

Resources

  • Manual testing (Florin, George)
  • Automation (Florin)

Testing activities so far

(eg. the activities that where finished)

Major issues so far

(eg. Bugs lists to follow)


Covered by Florin Strugariu