QA/Browser Technologies/Services/Releases/BrowserID 03012012

From MozillaWiki
Jump to: navigation, search

Areas for QA Focus

  • [QA] Suggested areas of focus for QA:
    • normal stuff
    • disable cookies, ensure good error messaging - all devices/browsers
    • abuse mysql (SIGSTOP, restart, shutdown, route TCP packets to the bitbucket) - ensure you see reasonable error messages but that the service stays up
    • mobile firefox nightlies
    • stop the keysigner, ensure that the service stays up and you see reasonable error messages (log out, try to log into a site in this state)
  • In addition, QA needs to spend time on the following:
    • Testing all FF channels on desktop and Android: Beta, Aurora, Nightly
    • Testing across all browsers with standard cookies and third-party cookies enabled/disabled
    • Test the new locales: lt: Lithuanian, pt_BR: Brazilian (Portuguese), rm: Romansh, uk: Ukrainian
    • Verify the following locales have been removed: fy: Frisian, af: Afrikaans

Information

  • Train 22: 03-01-2012

Links

Deployment Ticket

  • bug 732142 - QA and deploy BrowserID train-2012.03.01 to production
  • RPM:

OPs Ticket and ChangeWindow

  • Services Maintenance/Change Window
    • TBD

Hot Fixes and Other Deployments

ChangeLog

Versions

  • Dev: https://dev.diresworb.org/ver.txt
    • 76b0777 Merge branch 'dev' of github.com:mozilla/browserid into dev
  • Prod: https://browserid.org/ver.txt
    • 8d24766 more rpm fixes: instead of pulling in all config/, just l10n-all.json
    • locale svn r102380
  • Stage: https://diresworb.org/ver.txt
    • Orig: unknown
    • HotFix 1
      • 52a367c bump version number and document hotfix for issue #1235
      • locale svn r102416
    • HotFix 2
      • 7558d69 document db conn monitoring hotfix and bump version
      • locale svn r102380
    • Roll to 2012-03-01:
      • e327804 document db conn monitoring hotfix and bump version
      • locale svn r102598

Heartbeat

Processes

  • webheads
    • /usr/bin/node bin/browserid
    • /usr/bin/node bin/verifier
    • /usr/bin/node /opt/browserid/lib/verifier/verifier-compute.js
    • /usr/bin/node /opt/browserid/lib/bcrypt-compute.js
  • secure webheads
    • /usr/bin/node bin/dbwriter
    • /usr/bin/node /opt/browserid/lib/bcrypt-compute.js
  • keysigners
    • /usr/bin/node bin/keysigner
    • /usr/bin/node /opt/browserid/lib/keysigner/keysigner-compute.js
  • databases: various mysql processes
  • zeus: various zeus processes

Logs

  • webheads: /var/log/browserid/
    • browserid.log
    • browserid-metrics.json
    • verifier.log
    • verifier-metrics.json
    • verifier-compute.log
  • secure webheads: /var/log/browserid/
    • dbwriter.log
  • keysigners have /var/log/browserid/
    • keysigner.log
    • keysigner-compute.log
  • databases: n/a
  • zeus: various logs

Local Install - Unit Tests

  • Front-End Unit Tests
    • PASS
      • Tests completed in 59326 milliseconds.
      • 983 tests of 983 passed, 0 failed.
  • Back-End Unit Tests
    • PASS, except for test_mysql (known issue)
node.js:201
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
database not ready.  did you call open()?
CANNOT TEST 'test_mysql' ENVIRONMENT: can't connect to the database
  • Headless Front-End Unit Tests
    • PASS
      • Tests completed in 62396 milliseconds.
      • 983 tests of 983 passed, 0 failed.

Local Install - Load Test

  • Term1: CREATE_TEST_USERS=2000 BROWSERID_FAKE_VERIFICATION=1 NODE_ENV=test_mysql npm start
  • Term2: bin/load_gen -u 1/50 -m 50000 -o -s http://127.0.0.1:10002

Stage: Load Tests

Sample Bug and Issue

New/Updated OPs Tickets and Issues

New/Updated Security Tickets and Issues

  • None

New/Updated APPs Tickets and Issues

  • bug 725502 - window.open with dialog=yes argument in it causes weird issue
  • bug 701424 - Switch authentication to BrowserID for etherpad.mozilla.org

New/Updated Labs Tickets and Issues

  • None

New/Updated Localization Tickets and Issues

Resolved/Closed Bugs and Issues

Reopened or Updated : Server

  • bug 725502 - window.open with dialog=yes argument in it causes weird issue
  • bug 730015 - BrowserID: No longer able to Sign In using FF 12 (Aurora) or FF 13 (Nightly)
  • [BrowserID issue 536] : need log rotation for keysigner
  • [BrowserID issue 995] : Dev: Locale: input fields appear to be "translated" as well to right-justified
  • [BrowserID issue 1055] : Local install generates warnings against locale files
  • [BrowserID issue 1105] : Locale: [ca] Sign in screen shows issues with various strings and links.
  • [BrowserID issue 1133] : iOS - must click on radio button to select email address.
  • [BrowserID issue 1167] : The new "requires cookies" message needs improvement.
  • [BrowserID issue 1168] : Locale: Provide localized strings for new "requires cookies" message
  • [BrowserID issue 1176] : Mobile: No longer able to Sign In using FF 12 (Aurora) or FF 13 (Nightly)
  • [BrowserID issue 1201] : The diresworb.org home page displayed both the Account Manager and "Connect with BrowserID..." sections when all the cookies are disabled
  • [BrowserID issue 1204] : Include.js returns a 304 even though it takes a while to load
  • [BrowserID issue 1217] : Privacy and TOS links on Sign In page open to the same browser window/tab.
  • [BrowserID issue 1218] : Privacy and TOS links do not work correctly with older Android and stock browser
  • [BrowserID issue 1246] : Backend unit tests failing to connect to mysql

Reopened or Updated : Client

Opened Bugs/Issues For This Week: Server

Opened Bugs/Issues For This Week: Client

  • None

Other Open Bugs

Notes

  • List of supported locales for this release
    • "ca", "cs", "da", "de", "el", "en-US", "es", "et", "eu", "fi", "fr",
    • "ga", "hr", "it", "lij", "lt", "nl", "pa", "pl", "pt-BR", "rm",
    • "ru", "sk", "sl", "sq", "sr", "sv", "tr", "uk", "zh-CN", "zh-TW"
  • New locales:
    • lt: Lithuanian (100%)
    • pt_BR: Brazilian (Portuguese) (100%)
    • rm: Romansh (100%)
    • uk: Ukrainian (100%)
  • Locales removed:
    • fy: Frisian
    • af: Afrikaans
  • QA completed testing of this train, but it was not released to Production
  • The decision was made to hold due to significant open issues against UI flow, mobile support, and localizations