take (some and/or all of) the hack out of tideline's testling usage

[jebeck]

In setting up tideline for automated cross-browser testing with testling, several problems were encountered, and the current solution for configuration (passing testling an html file with both vendor library and test scripts linked and checked in and/or pre-bundled and checked in in the test/ directory of tideline is not ideal.

Be aware of these challenges when using testling:

• html file doesnt handle paths correctly tape-testing/testling#68
• testling is intended for use with npm; attempts to get it to install bower and then install bower dependencies (using the "preprocess" config option) failed...hence the decision to pass a complete html file (and check in the linked vendor files) to the service

A quick fix for the fact that testling relies on bower components that are being checked into the test/ directory is to add a git hook to tideline to check for updates to any of these components before each commit and copy over the updated components if necessary.

Better/longer term solutions are welcome and may take pretty much any less-hacky shape.

[jebeck]

Closing this, as testling is broken again without a good indication of why. Given that the browsers it uses are outdated (Chrome 29.0 vs. current 34.0), giving up on it as a tool.