Overview

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

Feature Status

Status

Feature Page

• https://wiki.mozilla.org/DevTools/Features/CodeEditor
• http://mozilla.github.com/devtools/status/index.html#codeeditor

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
  • November 25th
• Testing division between:
  • Manual testing:
    • Basic and full functional testing
    • Exploratory work on feature
  • Automated testing:
    • Acceptance testing
    • Automation of test-cases written for 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
• Automate most of the Litmus test-cases

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 660784 - Add the Orion source code editor to the browser
• Resolved Fixed bugs query
• Unconfirmed Bugs query

Schedule/milestones

• Land in Firefox 10

New testcases added

• Started creating testcases for CodeEditor here

Automated testcases