QA/Activity Stream
Revision History
This section describes the modifications that have been made to this wiki page. A new row has been completed each time the content of this document is updated (small corrections for typographical errors do not need to be recorded). The description of the modification contains the differences from the prior version, in terms of what sections were updated and to what extent.
| Date | Version | Author | Description |
|---|---|---|---|
| 01/25/2016 | 1.0 | Paul Oiegas | Created first draft |
Overview
Purpose
Detail the purpose of this document. For example:
- The test scope, focus areas and objectives
- The test responsibilities
- The test strategy for the levels and types of test for this release
- The entry and exit criteria
- The basis of the test estimates
- Any risks, issues, assumptions and test dependencies
- The test schedule and major milestones
- The test deliverables
Scope
This wiki details the testing that will be performed for Activity Stream project. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:
- What will be tested
- How testing will be performed
Ownership
Developer contacts: Edwin Wong
QA:
Rares Bologa - PM for QA team
Paul Oiegas - leading QA efforts
Ciprian Muresan, QA
Cosmin Muntean, QA
Vlad Bacia, QA
Testing summary
Scope of Testing
In Scope
Detail what is in scope from a testing perspective for the project team.
Out of Scope
-
Requirements for testing
Environments
Testing will be performed on following OSes (both x86 & x64 infrastructures):
- Bulleted list item
- Windows XP
- Windows Vista
- Windows 7
- Windows 8
- Windows 8.1
- Windows 10
- Ubuntu 14.04
- Ubuntu 15.04
- Mac OS X 10.9
- Mac OS X 10.10
- Mac OS X 10.11
Test Strategy
Test Objectives
This section details the progression test objectives that will be covered. Please note that this is at a high level. For large projects, a suite of test cases would be created which would reference directly back to this master. This could be documented in bullet form or in a table similar to the one below.
| Ref | Function | Test Objective | Evaluation Criteria | Test Type | Owners |
|---|---|---|---|---|---|
| 1 | - | - | - | - | - |
Builds
This section should contain links for builds with the feature -
- Nightly builds with the fix are available to the the link
- Links for Aurora builds
- Links for Beta builds
Test Execution Schedule
The following table identifies the anticipated testing period available for test execution.
| Project phase | Start Date | End Date |
|---|---|---|
| Start project | - | |
| Study documentation/specs received from developers | - | |
| QA - Test plan creation | 01/25/2016 | |
| QA - Test cases/Env preparation | - | |
| QA - Nightly Testing | - | |
| QA - Aurora Testing | - | |
| QA - Beta Testing | - | |
| Release Date | - |
Testing Tools
Detail the tools to be used for testing, for example see the following table:
| Process | Tool |
|---|---|
| Test plan creation | Mozilla wiki |
| Test case creation | Google docs |
| Test case execution | Google docs |
| Bugs management | Bugzilla |
Status
Overview
Track the dates and build number where feature was released to Nightly Track the dates and build number where feature was merged to Aurora Track the dates and build number where feature was merged to Release/Beta
Risk analysis
- Lack of the documentation - for this kind of feature we should receive a Release Notes document, summing up at least a basic description of what is to be expected from the feature in that release.
References
- List and links for specs - no documents with specs was received.
Testcases
Overview
Summary of testing scenarios
Test Areas
| Test Areas | Covered | Details |
|---|---|---|
| Private Window | - | |
| Multi-Process Enabled | - | |
| Multi-process Disabled | - | |
| Theme (high contrast) | - | |
| UI | ||
| Mouse-only operation | - | |
| Keyboard-only operation | - | |
| Display (HiDPI) | - | |
| Interraction (scroll, zoom) | - | |
| Usable with a screen reader | - | e.g. with NVDA |
| Usability and/or discoverability testing | - | Is this feature user friendly |
| Help/Support | ||
| Help/support interface required | - | Make sure link to support/help page exist and is easy reachable. |
| Support documents planned(written) | - | Make sure support documents are written and are correct. |
| Install/Upgrade | ||
| Feature upgrades/downgrades data as expected | - | |
| Does sync work across upgrades | - | |
| Requires install testing | - | separate feature/application installation needed (not only Firefox) |
| Affects first-run or onboarding | - | Florin/Lawrence are investigating if there is a dedicated QA for this, or we should test? Should be an yes/no and if is yes should add in detail column the team/person assigned. |
| Does this affect partner builds? Partner build testing | - | yes/no options, add comment with details about who will lead testing |
| Enterprise | Raise up the topic to developers to see if they are expecting to work different on ESR builds | |
| Enterprise administration | - | |
| Network proxies/autoconfig | - | |
| ESR behavior changes | - | |
| Locked preferences | - | |
| Data Monitoring | ||
| Temporary or permanent telemetry monitoring | - | List of error conditions to monitor |
| Telemetry correctness testing | - | |
| Server integration testing | - | |
| Offline and server failure testing | - | |
| Load testing | - | |
| Add-ons | If add-ons are available for testing feature, or is current feature will affect some add-ons, then API testing should be done for the add-on. | |
| Addon API required? | - | |
| Comprehensive API testing | - | |
| Permissions | - | |
| Testing with existing/popular addons | - | |
| Security | Security is in charge of Matt Wobensmith. We should contact his team to see if security testing is necessary for current feature. | |
| 3rd-party security review | - | |
| Privilege escalation testing | - | |
| Fuzzing | - | |
| Web Compatibility | depends on the feature | |
| Testing against target sites | - | |
| Survey of many sites for compatibility | - | |
| Interoperability | depends on the feature | |
| Common protocol/data format with other software: specification available. Interop testing with other common clients or servers. | - | |
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | - | |
| Interaction of this feature with other browser features | - |
Test suite
Full Test suite - Smoke Test suite - Regression Test suite -
Bug Work
Tracking bug – meta bug
Bug fix verification
| Bug No | Summary | Status | Firefox Verion |
|---|---|---|---|
| - | - | - | - |
Logged bugs
-
Sign off
Criteria
Check list
- All test cases should be executed
- Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
- All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)
Results
Nightly testing
List of OSes that will be covered by testing
- Link for the tests run
- Daily Smoke suite -
- Full Test suite -
- Regression Test suite, if needed/available
Merge to Aurora Sign-off
List of OSes that will be covered by testing
- Link for the tests run -
- Full Test suite -
Checklist
| Exit Criteria | Status | Notes/Details |
|---|---|---|
| Testing Prerequisites (specs, use cases) | ||
| Testing Infrastructure setup | ||
| Test Plan Creation | ||
| Test Cases Creation | ||
| Full Functional Tests Execution | ||
| Automation Coverage | ||
| Performance Testing | ||
| All Defects Logged | ||
| Critical/Blockers Fixed and Verified | ||
| Daily Status Report (email/etherpad statuses/ gdoc with results) | ||
| Metrics/Telemetry | ||
| QA Signoff - Nightly Release | Email to be sent | |
| QA Aurora - Full Testing | ||
| QA Signoff - Aurora Release | Email to be sent | |
| QA Beta - Full Testing | ||
| QA Signoff - Beta Release | Email to be sent |