Skip to content
This repository has been archived by the owner on May 13, 2019. It is now read-only.

Node.js Testing WG Meeting 2016-Jan-15 #1

Closed
Trott opened this issue Jan 9, 2016 · 4 comments
Closed

Node.js Testing WG Meeting 2016-Jan-15 #1

Trott opened this issue Jan 9, 2016 · 4 comments

Comments

@Trott
Copy link
Member

Trott commented Jan 9, 2016

Will take place at:

  • UTC: Friday, January 15, 2016 at 6:00:00 PM
  • Pacific Time (San Francisco): Friday, January 15, 2016 at 10:00:00 AM
  • Eastern Time (Pittsburgh): Friday, January 15, 2016 at 1:00:00 PM
  • Central European Time (Madrid): Friday, January 15, 2016 at 7:00:00 PM
  • Western European Time (Lisbon): Friday, January 15, 2016 at 6:00:00 PM

Hangout link: https://plus.google.com/events/ctbjov1nq2pntfhvje4e7mpktd4

More to come....

@Trott
Copy link
Member Author

Trott commented Jan 10, 2016

Agenda-ish:

Stuff to think about:

  • Unit tests (which might enable easier code coverage metrics)
  • Guidelines around tests: For example, when should a file containing multiple tests be split into multiple files?
  • Any current opportunities for collaboration with the Build WG?
  • Porting the Python test harness to JavaScript
  • Smoke testing/CITGM: What remains to be done? Should we check to see where things are with the SmokeTest WG? Does that WG officially exist? Should it be subsumed here?
  • Review of existing tests: Standardize some things? Lint rules? Document how things like pummel do/don't work?
  • Modularize common.js: Make it less of a junk drawer
  • Benchmarking: Do we have anything automated? How do we get there? Would this overlap with the Benchmark WG or would it be distinct from their work? Does that WG still effectively exist?
  • pummel and debugger seem to have a lot of not-working stuff and aren't part of CI. How can we fix that?

Administratia:

  • I can't create labels and do other things in this repo that perhaps everyone in the WG should be able to do. Who can change that?

@Trott
Copy link
Member Author

Trott commented Jan 15, 2016

@orangemocha
Copy link
Contributor

@Trott I think we need a different link. After you start the hangout, you can copy & paste the URL of the hangout window.

@Trott
Copy link
Member Author

Trott commented Jan 15, 2016

Oh, right, ugh! Beginner mistakes. Here, try this: https://plus.google.com/hangouts/_/hoaevent/AP36tYfNs71kiy_WrS0M_uLyD4dCQo6tPEApNQEiY944mPAcrr8y4A

@Trott Trott closed this as completed Jan 19, 2016
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants