Loop/QA/Meetings:2014-07-24

Links

• Private docs can be linked from https://intranet.mozilla.org/QA/Loop#Docs
• Public docs can be linked from your section in https://wiki.mozilla.org/Loop/QA
• Feature/Milestone development - https://wiki.mozilla.org/Media/webrtc#Visuals

Notices

• Meeting to be cancelled next week due to QA work week

Discussion

Target Milestones (add your questions/concerns below)

• understanding when features are landing and complete
• trying to align server & client dependencies for testing
• making sure everyone is on the same API version when testing
• milestones:
  • B2G - in "beta" august 11, in marketplace sept 30 for "testing"
  • Desktop - iteration #1 is a subset of features for MVP intended to be a "dry run" -- end of August to determine if it goes to Beta -- possible to ship in Fx33 but only if its feature complete and passes QA in Beta otherwise pref off and ship in Fx34 -- contacts in client targeted Fx34
  • Services aligned to B2G milestones
  • Scalability aligned to Desktop milestones
• Moztrap
  • Shell will needinfo Anthony on bugs needing Moztrap coverage
• Automation
  • Nils is in direct contact with DMose
• Paul Silaghi (softvision) is running through feature completeness testing in Fx33 and filing bugs for missing features
• We need to have better information on how to debug where an error is happening in a chain of events
• We need to make sure we are testing against the correct server

Notes from Shell Escalante:

• mobile
  • Jira test cases at Tef. Tef runs, then exports working scenarios. Mozilla imports new scenarios into Moztrap and runs
    • moztrap is manual test case manager
  • test client from fernando
  • firefox accounts stable for testing
  • Tef Loop client development schedule shared in a Test folder: https://drive.google.com/a/mozilla.com/folderview?id=0B1KBl68pRmhsdTJkMDZDV2FHeHc&usp=sharing
  • automation is a future - after manual tests scenarios matured
• desktop
  • To update moztrap for when we complete bug that adds a new scenario, needinfo anthony hughes to add to moztrap
  • Automation - dMose lets Nils know for integration with softvision
  • Soft vision - going through Darrin’s original designs next week for Fx33 Gap analysis.
    • 2 lists - missing in Fx33, and bugs filed for what will still be missing after Fx34 list
  • Schedule: Iteration 1 of Loop is on Fx33 Aurora with features to validate. MVP target is Fx34 - with a plan that it will ride the trains to release.
• services
  • gap until API’s are locked- breaking issues with updating.
    • close to locking and then API versioning for changes
  • stand-alone loop client tests being run
  • MSISDN verifier fernando wrote
  • working with dose when desktop client automated tests come in for pre-release tests
  • landing schedule - dMose and ckarloff discussing, broader group soon
• communications: is Tokbox on #devmedia (Moz and Tef are)
• how to debug? action item how to debug the server side, which layer did it happen on
  • about::webRTC documentation wiki, which server should be on

Detailed Project Status

Please list work completed and work blocked

Platform

H264

Owner: Jason Smith (CAF testing)

• https://bugzilla.mozilla.org/show_bug.cgi?id=1039596 Loop client does not work on certain networks 1040702 has comments
  • Originally we believed the Loop client could not use Web Sockets as they call establishment protocol was not working, and that protocol was based in Web Sockets. However, as Adam pointed out in 1040702 it seems WebSockets are indeed working in the same network as they are used to talk to TokBox infrastructure. That means that we should focus our effort in seeing if Loop Server configuration has some issues that make Web Sockets not work in some networks.
• Deep into E2E testing

MSISDN

Owner: Martijn Wargers

• currently blocked in USA/Can: https://bugzilla.mozilla.org/show_bug.cgi?id=1042866
• verifier-test
  • https://github.com/ferjm/msisdn-verifier-client
  • Fernando will give me a list of areas that could use more automated testing
  • Gai UI test app

Performance

Owner: Geo Mealer (FxOS)

Privileged API

Owner: Jason Smith

• No updates

Tokbox

Owner: Nils Ohlmeier

Desktop

Owner: Anthony Hughes

• Testing is blocked by http://bugzil.la/1043458 Desktop Fx Loop client and PROD (0.5) are on different API versions -- prevents generation of share URL
  • can we come up with a proposal to minimize these types of downtimes?

Firefox OS

Owner: Jason Smith (TEF testing)

• US/Canada testing heavily blocked by https://bugzilla.mozilla.org/show_bug.cgi?id=1042866
• TEF in Spain has no test blockers, but is in the middle of filing a bunch of bugs against the loop mobile testing bugs (https://bugzilla.mozilla.org/show_bug.cgi?id=1036490)
• 1039188 Firefox OS PeerConnection is not successfully established if devices are in different networks
  • DNS resolution: https://bugzilla.mozilla.org/show_bug.cgi?id=1042345

Server

• created loop server diagram
• Desktop Loop has API test (standalone loop client)
• https://wiki.mozilla.org/Loop/Try_Loop
• Current status of end 2 end: https://etherpad.mozilla.org/loopserver-status

Scalability

Owner: James Bonacci

• Loop-Client Stage is up and live
• Loop-Server Stage is up and live, but there were some issues
• Loop-Client Prod is still throwing 502s
• Loop-Server Prod is still throwing 502s
• This all of course is blocking client testing...
• Current client version: 0.2.0
• Current server version: 0.9.2

API

Owner: Peter deHaan

• working on getting standalone client pointing at PROD/STAGE for deploy testing

Services

Firefox Accounts Integration

Owner: Richard Pappalardo

• no updates