Matti Schneider

Log frontend JS errors

1

It would be great if Watai could log frontend console messages as they come, associated to the steps that raised them.

Output in TAP format

1

http://testanything.org/wiki/

Consider adding rendering / CSS changes detection

2

https://github.com/Huddle/PhantomCSS https://github.com/HumbleSoftware/js-imagediff

Rather than fail all features, first ping the server and make sure it replies!

Catch SIGINT and quit driver

1

…or not, depending on the "quit" config key.

- For [Ruby](https://github.com/shvets/selenium) with `gem`/`bundle`. - For Node: publish own wrapper. - Others (current main): `brew`.

Considering a widget with a `fileField` element being an ``, `this.setFileField(filePath)` does not work because it fails on the `clear`, leading to the need for this workaround: ``` upload: function...

Add auto upload to dist task

2

The `dist` task creates an archive with all necessary dependencies. It should be automatically uploaded to GitHub’s “downloads” pane. See the [Downloads API](http://developer.github.com/v3/repos/downloads/).

Currently, all suite files are loaded synchronously. It would be worth switching to an async load, or at least evaluate how it performs. [`nor-fs`](https://github.com/Sendanor/nor-fs), for example, provides a Q-based promises...

http://bramp.github.io/js-sequence-diagrams http://cytoscape.github.io/cytoscape.js