- QUnit team does not have a good relationship with Colin. Can we fix that? Otherwise any collaboration on Intern is pretty much impossible.
- If we can get out of the way, we could look at the technical issues.
- What are we going to do with it? Keep standalone as CLI client? Or integrate into qunitjs directly?
- Should at least merge version range for qunitjs package and make a new release, along with fixing whatever else breaks when updating from 1.10 to 1.20: https://github.com/kof/node-qunit/pull/118
- Does it make sense to adopt js-reporters in QUnit if no one else adopts it? Yes, since its a good interface.
- Update QUnit EventEmitter PR with the proper details and remove old details from the new events, keep them only on old events.
- js-reporter compatible implementation blocker for QUnit 2.0/
- Can we create a TAP adapter to use existing TAP reporters, to produce js-reporter output?
- Is TAP as or more comprehensive than js-reporters? If so, we don’t really need js-reporters and should just use TAP. If not, we can still generate TAP from js-reporters.
- We could add a tap property to the runEnd event, to support TAP output along with the regular interface. Orthogonal to everything else discussed here.
- Reviewed https://github.com/js-reporters/js-reporters/issues/30 to add missing data types and missing details for errors. Leo to create pull request to add those to the spec.
- link to 2.x migration guide, need to extend that for the event emitter
- QUnit 1.x should do single warnings for all uses of deprecated methods
- QUnit 2.0 helpfully breaks
- QUnit 2.1 unhelpfully breaks
- Tickets triage
- 39 open issues, 2 new, 1 new already closed
- 3 open pull requests, 1 new, 5 new already closed
- For the jQuery Summit we did a triage closing some issues.
- 2 new PRs from the jQuery Summit already merged. Thanks @rdugue and @arghgr!
- We started using waffle.io, seems fine so far: https://waffle.io/jquery/qunit
- @gibson042 is now a team member. Welcome!
- Waiting his update on qunitjs.com/about to announce on twitter.
- @leobalter will finish the work on the logging interface at jquery/qunit#644
- We will investigate how to bring LoDash's _.isEqual to replace deepEqual, probably bundling QUnit using webpack or browserify. That opens the path to use other methods like _.create. Ref jquery/qunit#865 and jquery/qunit#869
- Fixed a build process.
- no more updates
- Ticket triage
- 50 issues total
- 5 pull requests
- Nested modules and QUnit.config.collapse are ready and will be landed with a new release for them
- Leo is writing a blog post about the nested modules.
- 2.0 Milestone is one step away (standard reporter interface for js-reporters)
- Leo will work on a follow up for James' Event emitter PR (docs needed as well) based on js-reporters specs.
- With the event emitters we will be able to test js-reporters along.
QUnit.reporteris better than a
- We've got a few bugs on the way. (#870 is a recent regression).
QUnit.onlyis not a blocker for the 2.0 Milestone (it does not break anything).
- We need more collaborators.
- Bringing it to the jQuery Foundation might help.
- We should also bring js-reporters to other test frameworks.
link JS Reporters GSoC Project
July 17th - July 30th, 2015 author: Franziska Carstens
Done Last Week
To Be Discussed
- #20 (see discussion there)
- #21 do we need a build script?
- remove test.skipped
- implement start Events with suite and test objects
- try to add QUnit to the test script
- complete #21 (either build script or sed.js)
- complete #20, #22
July 16th - July 22th, 2015 author: Franziska Carstens
Done Last Week
- finished pull request
- added JasmineAdapter
- added ConsoleReporter
- added table for start events
To Be Discussed
- Do we want to include an extra skipped attribute or not?
- Data for runStart and suiteStart (Where do we get the data from?)
- finish PR fpr JasmineAdapter and ConsoleReporter
- set up test infrastructure
- implement Start Events
- Core module split is done, needs another review
- Updating CI config to opt-into new container infrastructure
- PR to add Map and Set support to deepEqual, needs another review, also check CLA issue
- js-reporters (Franziska)
- Done Last Week
- included esperanto to bundle the modules
- put the event summary of all test frameworks on GitHub to give a base for discussions
- restructurd the project to get a clear overview of the code
- moved the existing code in the js-reporters Repo
- updated the testEnd event for the QUnit adapter/reporter based on the results of the event summary of all test frameworks
- added eslint to the project
- Next Steps
- Finish PR
- Start Events
- Done Last Week
- Did a triage of all tickets, closed ~10 stale/outdated issues
- Franziska is going to start next week, first on jsreporter event data
- Leo to finish his PRs, node reporter is close to land
- Intern collaboration is making a bit progress through GSoC student: PR to add QUnit interface to Intern and branch for Globalize to use Intern with the QUnit interface
- Still lots of timeouts, making the CI results unreliable, if not useless. Try to escalate that.
- Added AMD support
- Released 1.18, including AMD support and improved diff module
- Leo focusing on open PRs, should be able to address all of them in more 1.x releases
- 2.x should be pretty trivial, just replacing some functions with deprecation errors
- Added QUnit/AMD support
- Still working on improved stability. Random errors on their end cause tests to time out eventually
- Leo and Jörn working on multiple PRs, mostly contributions from GSoC students
- Timo has limited availability, mostly for advising, maybe code reviews.
- James also limited, focus on js-reporters
- Works decent for QUnit, still getting a few timeouts, reported to BrowserStack
- Leo prototyping to test ES6 features via Goiabada: https://github.com/leobalter/goiabada
- babel works well for transpiling ES6, but to output browser-compatible code we need another step; browserify doesn’t support UMD, still need to solve that
- alternative: disable babel’s es6.modules transform, then use esperanto to transform to UMD
- Scott to put together a test
- Moved to new server, seems to work fine
- Enabled browserstack-runner for Travis, including PRs, for QUnit repo
- Will do the same for Globalize once requirejs load issues are resolved
- jQuery UI takes 5+ minutes to run everything, times out before finishing