Tom Seldon

Performance: Stream files vs. all-at-once linting

6

Currently, when parsing multiple files they are each piped to the Closure Linter one at a time. This was done as it seems to be the "Gulp way" of doing...

Although you wouldn't want to lint a minified file... It shouldn't crash if you do. The crash appears to be in the closure-linter itself, though may be in the closure-linter-wrapper...

Fail CI build if coverage is below threshold

2

Need to set an appropriate threshold value. Probably 90% per file.

- [ ] Create Gulp task(s) to run Protractor - [ ] Add sample feature file / steps to confirm that Protractor can run correctly Could use Jasmine or Cucumber...

- [ ] Set up Sauce Labs account for this repo - [ ] Configure Travis to run the end-to-end tests with Sauce Labs

Existing set of features aren't covered by any functional tests. There should be some in place to help protect against regression.

Since moving to using TypeScript, the coverage reports either fail or are wrong. This needs to be fixed so we can go back to failing CI builds at a certain...

App can be incrementally changed over to TypeScript. This is a nice to have and I'll probably look at this after first release.

For desktop, we can get the selected text using HTML as the coercion type. It's unknown if this is available on the mobile version. If not, we need to investigate...