QA/Waverley/Developer-Tools/StyleEditor/TestPlan
From MozillaWiki
< QA
Contents
Overview
- Guidance in testing the new StyleEditor feature present in Firefox.
Feature Status
Please use "Edit with form" above to edit this page.
Status
Style Editor / CSS Editor | |
Stage | Landed |
Status | Complete |
Release target | Firefox 11 |
Health | OK |
Status note | ` |
Feature Page
- https://wiki.mozilla.org/DevTools/Features/CSSEditor
- http://mozilla.github.com/devtools/status/index.html#cssedit
Strategy
- Creating new testcases for Litmus
- Identify tracking bugs in Bugzilla
- Keep testcases up-to-date considering development cycle shifts
- Organize test-day to cover new feature
- Testing division between:
- Manual testing:
- Basic and full functional testing
- Exploratory work on feature
- Manual testing:
Scope of Planned Testing
- Keep track of logged issues in order to maintain up-to-date Litmus testcases and possible regressions
- Discover new issues through exploratory work
Platform and Configurations
- All Operating Systems (Win7, WinXP, Ubuntu 11.04, Mac 10.6, Mac 10.7) and hardware configurations (32 and 64 bit versions)
Major Test Areas
- Add test-cases considering the new filled bugs that are marked with special "in-litmus?" flag
- Tests performed around Litmus test-cases
- Exploratory work
Bugs
- Tracking Bug
- bug 583401 - Style Editor integration
- Fixed bugs query
- Unconfirmed Bugs query
- Bugs waiting for approval-mozilla-aurora
- Bugs that got approval-mozilla-aurora
Schedule/milestones
- Land in Firefox 11
New testcases added
- Started creating summary test cases for Style Editor
- Created Litmus BFT's in the Aurora Testrun