Author Archives: builder

jQuery UI Team

jQuery UI Team Meeting – Aug 03 2016

js-reporters Team

js-reporters Team Meeting – Aug 01 2016

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
jQuery Core Team

jQuery Core Team Meeting – Aug 01 2016

Attending: timmywil, markelog, DaveMethvin, gibson042, m_gol

link 3.1.1

link Issues needing review

link PRs

link Wontfix wiki page

  • Looks good
  • Dave to add pointer from old page

link Migrate

  • Approach for deprecated APIs in 3.2? Just warn and let them pass through, or warn and fill (and run unit tests?)
    • Resolved: just warn, don't fill or move/copy unit tests from core
    • APIs removed in core 4.0 can be filled in migrate 4.0

link Consider using Gitter instead of IRC

js-reporters Team

js-reporters Team Meeting – Jul 25 2016

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.
jQuery Core Team

jQuery Core Team Meeting – Jul 25 2016

Attending: timmywil, m_gol, DaveMethvin, jbedard

link 3.1.1

link Run tests on a slim, selector-native, ready-no-deferred builds

  • Set up periodic jobs for these builds
  • Build commands: slim is built with the default, grunt custom:-sizzle, grunt custom:-deferred

link PRs

link Migrate

PEP Team

PEP Team Meeting – Jul 21 2016

js-reporters Team

js-reporters Team Meeting – Jul 18 2016

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).
jQuery Core Team

jQuery Core Team Meeting – Jul 18 2016

Attending: timmywil, gibson042, jbedard, m_gol, DaveMethvin, markelog

link 3.1.1 > 3.2.0

  • Should we wait with merging PRs targeted at 3.2.0 while we wait for 3.1.1?
    • Yes, if they can’t go in 3.1.1 instead
  • Mark all PRs with the appropriate milestone. Do not merge PRs that are not for the upcoming milestone.

link Run tests on a slim, selector-native, ready-no-deferred builds

  • Set up periodic jobs for these builds
  • Build commands: slim is built with the default, grunt custom:-sizzle, grunt custom:-deferred

link Deprecations, let's decide on them all

link Slim & deprecated.js

link PRs

PEP Team

PEP Team Meeting – Jul 14 2016

js-reporters Team

js-reporters Team Meeting – Jul 11 2016

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