Loop/QA/Meetings/2014-06-05

https://wiki.mozilla.org/Loop/QA

Attendees

• Nils Ohlmeier, Richard Pappalardo, Geo, Marc, Jason, Edwin, Syd, Peter,

Notices

• Anthony Hughes is out today due to a family matter, will be out next week for TRIBE
  • Nils is leading this meeting in his absence

High-level Project Status

• 11 FxOS 2.0 platform bugs remain as dependencies for the Mobile client
• Attention screen design is moving forward (bug 988212) -- depends on bug 1007066, bug 853711, bug 1016277
• H264 latency target is 10-30ms, currently 100ms -- this has been escalated via bug 989945
• Flame call quality issue has been escalated to OEM via bug 1012936
• getUserMedia permissions is close to landing, pending resolution of automated test failures
• MLP has landed in Elm and is planned to move to Nightly by end-of-week -- depends on deploying a production Loop server via bug 1018866
• Roadmap/Marketing kick-off happening in SF on June 5th
• Branding work is ongoing -- Contact integration mockup -- PR/Marketing is working on how best to handle branding since Contacts code is planned to land on June 9th (much sooner than Branding will be ready) -- see also bug 1017756
• Added this to get us started: https://wiki.mozilla.org/Services/Loop/Try_Loop

Detailed Project Status

Please list the status for each section including any outstanding blockers, concerns, or questions that need to be addressed.

Platform

H264

Owner: Jason (CAF doing testing)

• CAF is going to lead testing of H264 WebRTC support
  • CAF has the tools to test, Moz does not
  • jsmith will be Moz representative
• Draft test plan built by CAF - sent out via email (~16 or so test cases for call workflows)

MSISDN

Owner: Martijn Wargers

• No updates here - need to followup with mwargers to get working on this
• Server: Peter/Jbo

Performance

Owner: Geo Mealer (FxOS)

• FxOS performance strategy still needs definition. Some ideas have been raised in an initial roadmap meeting, but we haven't narrowed down to what we can actually feasibly do in near-term.
• Have planning meeting w/ FxOS Performance team manager to determine what level of involvement the FxOS perf team intends to take, both prior to having a testable client and after.
• May initially want to focus on some of the system-level metrics (connection, SNR, delay, etc.) that were brought up in the kickoff as they will primarily involve the WebRTC team and not rely on also coordinating w/ the perf team.
• Per jsmith, need extremely customized FxOS/KitKat build to have anything near representative performance. Availability might be a blocker.
• Also, need to determine owners for performance of other parts of the system. Geo has FxOS Performance, but probably can't support the entire perf strategy solo.

Privileged API

Owner: Jason Smith

• Draft brainstorm of test cases for Audio Channel Privileged support
• Need to work on test cases for other areas

Tokbox

Owner: Nils Ohlmeier

• Moz Dev wants automated tests running through TokBox infrastructure
• Email introduction to TokBox QA has been made and we are trying to setup an initial meeting
• TokBox agreed that we can run basic automated test on their production systems

Desktop

Owner: Anthony Hughes

• Question[edwong]: When should we log bugs? Team: Let's coordinate with Dev before we unleash a flood of bugs.

Firefox OS

Owner: Jason Smith

• TEF has a draft test plan of the mobile client (~550 test cases) for each user story
• See H264, MSISDN, and Privileged API for further updates
• Actively working with TEF to build test plans for Loop OS dependencies in Comm Apps
• Need to chase mwargers down on MSISDN
• Working on privileged API test plan
• Question[edwong]: will fxOS2.0 ship with this app? does it use Settings level account?
  • Loop mobile client app will only ship as a marketplace app - not part of the operating system or a customization

Server

Scalability

Owner: James Bonacci Loop-Server stage environment deployed just this week. This is a very basic deployment to start some load testing. There still needs to be some logging and other OPs changes that will need to happen soon. Size/Scale for AWS will not start happening till at least next week. Load testing is in progress this week and will continue next week. TokBox infrastructure testing may start next week (tied into our Stage environment and load test tool). Loop-Server prod environment is a WIP but should be available for the Nightly requirements.

• Question[edwong]: How is TokBox involved? Team: initial handshakes go through tokBox, at which, a decision will be made to use peer to peer or TokBox Proxy/Tunnel.

API

Owner: Peter deHaan

• Submitted a few PRs against loop-client and loop-server
• Looking into l10n (currently looks like "en" and "fr" are supported)
• Looking into testing server API directly using cURL with valid/invalid values

Services

Firefox Accounts Integration

Owner: Richard Pappalardo

• Plan is to leverage and adapt existing marionette JS testcase(s) for FMD, Settings, etc. that validate authentication on B2G
• Testcases to cover additional features related to auth will be added as needed

Private Build/Repository

Who owns this?

• Devs working on desktop client working from private repository due to Tokbox requirements
• #media, dmose
  • "soon" - target is for 32
  • Something else being used instead of Simple Push temporarily
  • Simple Push target is for Fx34
  • Fx33 something else being used as temporary solution

Discussion

<add your discussion items below>

Action Items

• Anthony is working on getting an email alias set up for easier communication
• Everyone please update the wiki with their project status
• Ask Maire about submitting bug reports once landed in Nightly
  • Maire's answer: Yes, please go ahead and start filling bug - note: so far only the account less mode works
• Ask TokBox about staging vs. production
• Setup meeting with Adam and Edwin