IRC, Freenode, #jquery-meeting; attending: Jörn Zaefferer (project lead, GSoC mentor), Florentin Simion (GSoC student, working on js-reporters)

• Last week:

  • Landed getters refactor, now ES5 compatible (with es5-shim)
  • Bugfix in QUnit adapter
  • Added testCounts property to suites, in spec and adapters
  • Dealing with rollup-plugin-babel regression

• This week:

  • Finish spec update
  • Add examples to README
  • Release adapters and update browserstack-runner, with testCounts
  • Rebase QUnit implementation on top of their new ES6 modules, discuss using our TAP reporter

IRC, Freenode, #jquery-meeting; attending: Jörn Zaefferer (project lead, GSoC mentor), Florentin Simion (GSoC student, working on js-reporters)

• Last week:

  • Finished normalizing assertions propery, merged (#80)
  • Started discussing about order of emitting tests (source vs execution order) (#62)
  • Replaced getters, for IE8 compat, still requires es5-shim, e.g. in browserstack-runner

• This week:

  • Land getters-refactor
  • Update spec (#30)
  • Add examples (#27)
  • New release
  • Notify Jasmine team about progress on js-reporters

12:00 UTC (noon), IRC, Freenode, #jquery-meeting; attending: Jörn Zaefferer (project lead, GSoC mentor), Florentin Simion (GSoC student, working on js-reporters)

• Last week:

  • browserstack-runner PR got merged!
  • Christoph Hiller (@boneskull) is contributing! Interested in integrating js-reporters in Mocha. Already helped review/design assertions properties.
  • Implemented fullName prop, array with suite and test names, empty array for global suite

• This week:

  • Finish normalizing assertions (as part of #80)
  • Update spec, add details (#30)
  • Add examples to readme (#27)
  • Discuss tests emitting order (#62)
  • Will update browserstack-runner to latest js-reporters once testEnd with assertions is released. Also to fix IE8 regression.

12:00 UTC (noon), IRC, Freenode, #jquery-meeting; attending: Jörn Zaefferer (project lead, GSoC mentor), Florentin Simion (GSoC student, working on js-reporters)

• Last week:

  • Finished browserstack-runner PR, now sending “tracebacks” in the _progress event, needs some review/approval from BrowserStack
  • Released 1.0.1, fixing compat with IE10

• This week:

  • Jörn trying to contact BrowserStack about the PR (Shirish doesn’t seem to work there anymore)
  • Fix issues with nested suites and suite names
  • Contact @boneskull
  • Talk to QUnit team about js-reporters support (WIP PR).

12:00 UTC (noon), IRC, Freenode, #jquery-meeting; attending: Jörn Zaefferer (project lead, GSoC mentor), Florentin Simion (GSoC student, working on js-reporters)

• Last week:

  • Landed versions tests, for now without CI integration.
  • Update browserstack-runner integration to replace existing plugin with a single js-reporters plugin (except jasmine1).
  • Fixed Mocha adapter to keep the original reporter in place, allows browserstack-runner to still have the HTML reporter output
  • Published js-reporters 1.0 on npm

• This week:

  • Finish browserstack-runner integration: Fix loading js-reporters dist from node_modules. Fix globalSuite.runtime issue with Mocha adapter. Create PR, get it landed
  • Once that PR is ready: Fix issues with nested suites and suite names
  • Once PR landed: Reboot communication with Mocha and Jasmine

12:00 UTC (noon), IRC, Freenode, #jquery-meeting; attending: Jörn Zaefferer (project lead, GSoC mentor), Florentin Simion (GSoC student, working on js-reporters)

• First meeting!

• Since the start of the program: Created an extensive testsuite to thoroughly test all 3 adapters. Rewrote all adapters, fixing a lot of bugs in the process. Meanwhile migrated from esperanto to rollup. Update tap-reporter to TAP 13, adding tests for that as well

• Last week: Focus on getting js-reporters adapters into browserstack-runner. Discussed/reviewed issue in their existing tests. Trying to decide how to deal with older framework versions, built separate tests for those.

• This week:

  • Land versions tests, without CI. Can for now run it manually every now and then. Debug CI failure on node 6 later.
  • Fix browserstack-runner integration, create PR
  • Help searls adopt js-reporters for teenytest

• Later:

  • Address issues with nested suites and suite names
  • Reboot communication with Mocha and Jasmine
  • Implement js-reporters support in QUnit