QA/Hello

From MozillaWiki
< QA
Jump to: navigation, search

Hello with screen sharing

Ownership

Developer contacts: Mark Banner, :standard8 on IRC; Mike de Boer, :mikedeboer on IRC;

QA Lead: Bogdan Maris mail , :bogdan_maris on IRC

Status

Overview

[LANDED] Nightly 47: first landed

[TBD] Aurora 46: n/a

[TBD] Beta 45: n/a

[TBD] Release 45: n/a

Risk analysis

Draft

Event Probability Impact Current situation Mitigation steps
Layout issues caused by Context probable high Hello panel, Conversation menu and StandaloneUI will suffer some layout issues due to Context Some issues were found that introduced some layout issues: bug query
Failed to show Context improbable high Context might be missing from Hello panel, Conversation menu and StandaloneUI Periodical regression testing covers this area
Unable to edit Context improbable medium Context might not be able to be edited using the edit button Periodical regression testing covers this area

Summary

Context

Hello lets you show web pages on your computer screen to friends during a call. It makes it easier to plan trips together, give a presentation or get feedback on an idea.

See mozilla support on how to use Hello.

Enabling the feature

  • Enabled by default in Nightly:
    • Build from 2015-11-30 bug


Enable feature with e10s

To test Hello with e10s, user has to set loop.remote.autostart to true (otherwise Hello refuses to let you use it with e10s).

Requirements for testing

Environments

Testing will be performed on following OSes:

  • Windows 7
  • Windows 10
  • Ubuntu 14.04/15.04
  • Mac OS X 10

References

Test cases

  • [DONE] Test cases gdoc.

Builds

This section should contain links for builds with the feature -


Bug work

Tracking bug

meta: Bug 1226706 - [META] add-on / loop-test status tracking bug


Meta bug for Hello with e10s enabled: Bug 1154273

Bug triage +/- for verification (qe-verify+)
Bug fix verification

Verified bugs - bugzilla query

Logged bugs

Logged bugs - bugzilla query

Sign off

Criteria

  • All test cases should be executed
  • All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)

Results

Aurora Sign-off - (date)

  • [ON TRACK] Aurora 46

Beta Sign-off - (date)

  • [ON TRACK] Beta 45

Release Sign-off - (2016-03-02)

  • [DONE] RC 45.0

Hello with e10s enable

Nightly Sign-off

  • [IN PROGRESS] Nightly 48 - full test suite - link


Checklist

Exit Criteria Status Notes/Details
Testing Prerequisites (specs, use cases) [DONE]
Testing Infrastructure setup [DONE]
Test Plan Creation [DONE]
Test Cases Creation [DONE]
Full Functional Tests Execution [DONE]
Automation Coverage
Performance Testing
All Defects Logged [DONE]
Critical/Blockers Fixed and Verified [IN PROGRESS]
Daily Status Report (email/etherpad statuses/ gdoc with results) [DONE]
Metrics/Telemetry N/A
QA Signoff - Nightly Release [DONE] Email to be sent
QA Signoff - Aurora Release [DONE] Aurora 46
QA Signoff - Beta Release [DONE]| Beta 45
QA Signoff - Firefox Release [DONE]| Email send on 2016-03-02 (RC 45.0)
QA Nightly with e10s enabled - Full Testing [IN PROGRESS] Nightly 48