QA/Firefox 4/Test Plan/NPAPI:CocoaEventModel
Contents
- 1 NPAPI:CocoaEventModel
- 2 Feature Release Readiness Assessment
- 3 Feature Documentation
- 4 Feature Bug Management
- 5 Feature Test Items
- 6 Feature Tests
- 7 Community Test Events
- 8 Feature Documentation Details
- 9 Feature Release Readiness Assessment Details
- 10 Feature Bug Management Details
- 11 Feature Test Items Details
- 12 Feature Tests Details
- 13 Community Test Events Details
NPAPI:CocoaEventModel
| Area | Details |
|---|---|
| Development Status: | In progress |
| Feature Testing: | In progress |
| Team: | Developer: josh (Josh Aas), QA: marcia (marcia) |
| Tracking Bugs | Bug bug 435041 - implement Cocoa NPAPI event model for Mac OS X |
Feature Description
The Cocoa event model is an alternative event model for 32-bit Mac OS X plugins and the default event model for 64-bit Mac OS X plugins.
From Josh, the developer: The only major consumers for the Cocoa event model are JavaPlugin2 and Flash 10.1 on Mac OS X 10.6, so testing the Cocoa event model essentially means testing those plugins and reporting bugs. Some bugs might not be our fault, but we can figure that out. Flash is known to have a major problem with keyboard input, it is not our fault and we are working that out with Adobe.
Feature Release Readiness Assessment
The table below provides a top level go/no go assessment of whether the feature is release ready for the given milestone.
| Milestone | Assessment |
|---|---|
| #Beta1 | N/A |
| #Beta2 | N/A |
| #Beta3 | N/A |
Feature Documentation
| Item | Description | Status |
|---|---|---|
| #Project_Wiki | Wiki Links to all feature related entries | |
| #Developer_Links (blogs) | Developer links to feature related sites | |
| #Other_Docs | Web links to feature related sites | |
| #Developer_QA_Review | Details from developer and qa discussions regarding feature test strategies and issues. |
Feature Bug Management
| Item | Description | Status |
|---|---|---|
| #Bug_Tracking | Top level bugs tracking feature | |
| #Bug_Verification | Feature bugs that need verification | |
| #Bug_Triage | Links triage bug tasks |
Feature Test Items
The table below provides a breakdown of all feature items that should be covered and how they will be tested. Not all items will be covered by internal QA team members. It is important to list what should be covered. If it is not covered, list it as not covered.
Note: not all items listed below will apply for a given feature
| Test Item | Description | Covered By | Status |
|---|---|---|---|
| Flash 10.1 | Plugin | End user testing/Beta tester exposure | |
| JavaPlugin2 | Plugin | End user testing/Beta tester exposure | |
| #Localization | Feature localization | ||
| #Accessibility | Feature accessibility | ||
| #Plugins | Plugins compatibility | ||
| #Addons | Addons compatibility | ||
| #Topsites | Top internet sites compatibilities |
Feature Tests
Automated Tests
| Item | Description | Status |
|---|---|---|
| #Developer_Tests | Links to automated developer tests | |
| #Mozmill_Tests | Links to automated mozmill feature test cases |
Manual Tests
| Item | Description | Status |
|---|---|---|
| #Smoke_Tests | link to smoke tests | |
| #Regression_Tests | link to BFT and/or regression tests | |
| #Functional_Tests | link to FFT and/or complete functional tests |
Community Test Events
| Item | Description | Status |
|---|---|---|
| #Testdays | Links to test day event results for feature | |
| #Bugdays | Links to bug day event results for feature | |
| #Meetups | Links to Meetup events for feature |
Feature Documentation Details
Project Wiki
Developer Links
- Provide links to all feature related developer links to blogs and other internet sites
Other Docs
- Provide links to all feature related developer links to blogs and other internet sites
Developer QA Review
The QA person responsible for the feature should hold a formal interview with the lead developer or feature champion. Below are questions that should be asked in the interview:
- Do we have automated tests for the feature?
- What do they cover?
- What do they not cover?
- How well do they cover the feature?
- What are the important areas we should focus on?
- What are the dependencies?
- What is our comfort level with this feature in its current state?
- What feedback would you like from QA?
Feature Release Readiness Assessment Details
Beta1
Beta2
Beta3
Feature Bug Management Details
Bug Tracking
- Top level bugs tracking feature. Include any relevant bug queries that are helpful for tracking feature status.
| Query Name | Description |
|---|---|
| bugzilla query url link | query description |
Bug Verification
Bug Triage
- Bug triage information
Feature Test Items Details
Localization
- Details of feature localization test requirements
Accessibility
- Details of feature accessibility test requirements
Plugins
- Flash 10.1
- JavaPlugin2
Addons
- Details of addons compatibility
Topsites
- Details of top internet sites test requirements
Feature Tests Details
Automated Tests Details
Developer Tests
- We do have automated tests for the Cocoa event model, they execute on 64-bit tinderboxes. The automated tests are not enabled for 32-bit builds. They cover most things, but most significantly they do not cover keyboard input very well.
Mozmill Tests
If a particular feature needs manual tests which should also be covered by Mozmill tests please add the "[mozmill-test-needed]" whiteboard entry to the feature implementation or regression bug.
List of Mozmill Tests:
- Links to automated mozmill feature test cases
Manual Tests Details
Smoke_Tests
- links to litmus smoke tests or description
Regression_Tests
- links to litmus BFT and/or regression tests description
Functional_Tests
- links to litmus FFT and/or complete functional tests description
Community Test Events Details
Testdays
- Links to test day event results for feature
Bugdays
- Links to bug day event results for feature
Meetups
- Links to Meetup events for feature
