testing for the browser and the server

[ghost]

Write unit tests and modules that work in both environments.

• approaches to code organization to improve testability (where to put the IO)
• shimming libraries to work both places
• code coverage
• using protocols (TAP)
• continuous integration services and ci tooling (travisify, testlingify)

[derekr]

:+1:

[JamesMGreene]

:+1:

[ghost]

and the narrative element would be related to writing tests and iterating on features for hundreds of tiny modules over a long multi-year period

[mikeal]

i usually hate talks about testing, but this actually sounds really great ;)

[cronopio]

:+1:

[brianloveswords]

:+1:

[boolpath]

:+1:

[GarrettS]

+1 for testability. A refactoring example might be good.

First, we had:

[steaming piles]

Next ...

[still stinks]

Finally ...

[testable code]

[mikeal]

This talk is accepted, you should be a collaborator on the speaker repo now. https://github.com/mikeal/jsfest-speakers

[GarrettS]

This is a different issue #3 than the issue #3 that I created.

On 12/14/13, Mikeal Rogers notifications@github.com wrote:

This talk is accepted, you should be a collaborator on the speaker repo now. https://github.com/mikeal/jsfest-speakers

---

Reply to this email directly or view it on GitHub: https://github.com/mikeal/jsfest2014-cfp/issues/3#issuecomment-30593932

Garrett @xkit ChordCycles.com garretts.github.io

[mikeal]

@GarrettS yeah, i think yours was #3 in the DHTMLConf repo

[JamesMGreene]

https://github.com/mikeal/dhtmlconf/issues/3

[GarrettS]

On 12/20/13, James M. Greene notifications@github.com wrote:

https://github.com/mikeal/dhtmlconf/issues/3

Just don't expect the actual presentation to be a copy'n'paste.

Garrett @xkit ChordCycles.com garretts.github.io