Category: Testing Team

Minutes from jQuery Testing Team meetings

Testing Team Meeting – Oct 10 2013

Location: #jquery-meeting on Freenode

Attending: Timo, James, Jörn

link QUnit

  • Timo working on source split, will rebase assert work on top of that. In the future, a build step is necessary, as in jQuery Core
  • Provide “grunt watch” to quickly rebuild “dist/qunit.js”, which unit tests will reference

link TestSwarm

link Testing infrastructure

  • Timo updated TestSwarm browsers: Firefox 21/22 to 23/24, added Opera 15, added iPad w/ iOS 5.1 and iPhone w/ iOS 6.0

Testing Team Meeting – Sep 26 2013

Location: #jquery-meeting on Freenode

Attending: James, Michał, Oleg, Jörn

link Availability

  • Jörn busy with lots of other projects, mostly jQuery UI, still working on esformatter
  • James to ramp back up in October, go back to finishing node compat
  • Timo busy with events and school, going to ramp up in October back to ~ 10h/week.

link QUnit

  • Discussion about setup/teardown logging callbacks, triggered by this PR: https://github.com/jquery/qunit/pull/471
    • We at least agree on adding a Per-test setup/teardown, defined at the page level
    • Maybe a Per-module setup/teardown, defined at the module level, for something like this
    • Syntax idea: Using QUnit.module( .. ).on(‘setup’, fn).on(‘teardown’, fn); ( or QUnit.module( .. ).on( { setup: fn, teardown: fn })
  • Maybe have Assertion, Test and Module all be EventEmitter (instead of just QUnit) and propagate from the lower-level objects to the higher ones (re-using the event name and data parameters)
  • node compat
    • James to pick up on in October
  • QUnit.Assertion and QUnit.on
    • Timo to pick up again in October

link TestSwarm

link Testing infrastructure

  • Need to add iOS 5.1, 6.1 & 7.0 for Core builds (or whatever BrowserStack can provide that’s close enough)
    • iPad 3rd 5.1, iPhone 5 6.0
  • Add a separate run for Android 2.3, for manual runs, since the Android runs are very slow
  • Looked at preview of BrowserSwarm, which runs QUnit tests through SauceLabs, has better output than grunt-saucelabs, but works more like TestSwarm
  • Timo to prototype a grunt-qunit-saucelabs plugin that makes use of SauceLabs new support for running unit tests

Testing Team Meeting – Jun 14 2013

In-person meeting in Portland, OR, after jQuery Conference.

Attending: Timo, James, Jörn

link QUnit Roadmap

  • Release 1.12 soon. Just one open ticket for that milestone.
  • Do all other deprecations in the next one or two minor releases.
  • Release 2.0 with some breaking API changes, but including a migration layer that makes it easy to find invalid usage.
  • Remove that migration layer in 2.1

link Infrastructure Roadmap

  • Improve grunt-saucelabs, potentially replacing TestSwarm
  • Until then, keep TestSwarm and Jenkins running
  • Also enable TravisCI for PR testing, though without cross-browser coverage (was already enabled for QUnit and Mobile)

Testing Team Meeting – Apr 25 2013

  • Attending: James, Timo, Scott, Corey

link QUnit

  • Fixed missing license headers in plugin repos (jquery/qunit-composite, jquery/qunit-reporter-junit). Added MIT-LICENSE.txt file to all qunit repo (was also missing in core jquery/qunit).
  • Published our qunit plugins on npm with keyword ‘qunit-plugin’ (and ‘qunit-reporter’ for reporter plugins). Scott brings up whether we should maintain a manifest for Bower users as well. To be discussed.
  • WIP: James working on Node compatibility
  • WIP: Timo working on event listener

link Jenkins/Travis

link TestSwarm

  • WIP: Timo is finishing up the last bits of the major refactoring. Expected to land within 24 hours.

Testing Team Meeting – Mar 14 2013

March 14, 2013
Location: #jquery-meeting on Freenode
Attending: James, Scott, Ghislain, Jörn, Richard, Timo

Time: 11am ET (16:00 UTC)

QUnit

Jenkins/Travis

We’d like to run `grunt` for all
PRs – Travis makes this really easy, mergatron should do it, too.

We want TestSwarm for regular
commits, this won’t work with Travis, since it can’t expose confidential
credentials to PR committers.

TODO: Add a few more projects to
Travis, gives us basic testing for PRs

  • travis.yml to init/update
    submodules, npm install -g grunt-cli
  • npm install && npm test
    is done on travis by default

We can use that at least until
mergatron can do it better.

TestSwarm

  • projects update shelved for a
    week, until higher priority issues are resolved (infrastructure,
    BrowserStack)

 

 

Testing Team Meeting – Feb 28 2013

February 28, 2013
Location: #jquery-meeting on Freenode
Attending: Timo, Dave, Scott, Jörn
Time: 11am ET (16:00 UTC)

QUnit

Starting splitting out add-ons
into separate repositories:

TestSwarm

Timo working on projects
refactoring: https://github.com/jquery/testswarm/tree/projects-4

Working with BrowserStack to fix
lost workers.

 

 

Testing Team Meeting – Jan 31 2013

January 31, 2013

Location: #jquery-meeting on Freenode

Attending: Scott, Richard, Corey, James, Jörn

Time: 11am ET (16:00 UTC)

QUnit

TestSwarm

  • Timo working on projects
    refactoring
  • Puppetized localSettings.json, no
    more edit-on-live server when we need to change our browset sets.

BrowserStack integration

  • Got BrowserStack access to our Splunk
    dashboard. Already helping to fix issues on their end.
  • Now hoping to figure out why we
    loose so many workers.

 

 

Testing Team Meeting – Jan 05 2013

January 03, 2013

Location: #jquery-meeting on Freenode

Attending: James, Jörn

Time: 11am ET (16:00 UTC)

QUnit

Survey is online: https://docs.google.com/spreadsheet/viewform?formkey=dDBzQl9TWmQzbDdXS08wMTBuLTlObXc6MQ#gid=0

Survey results: https://docs.google.com/spreadsheet/ccc?key=0ArIM4UVbwE-3dDBzQl9TWmQzbDdXS08wMTBuLTlObXc#gid=0

Updated htmlEqual PR from James: https://github.com/jquery/qunit/pull/368 – needs review

Landed https://github.com/jquery/qunit/pull/387 – more reliable throws() assertion

Landed https://github.com/jquery/qunit/pull/384 – module/test filters now work in IE7/8 with file protocol

Support for pending tests like Mocha? “tests without a function body such that they show up in the list but have a different visual representation and do not count as either a success or a failure; rather, a new "pending" count is added as well.” – still not very convincing.

Better async testing!

Mocha looks at callback signature and makes tests async when a callback argument, usually named done, is present: http://visionmedia.github.com/mocha/#asynchronous-code

Can’t do that since we introduced the assert argument

Can do something like this:

  • test(…, function(assert) { var done = assert.async(); … done(); }
  • asyncTest(…, function(assert) { assert.done(); })

Going to land the two deprecation tickets, then release 1.11

TestSwarm