forked from karma-runner/karma
-
Notifications
You must be signed in to change notification settings - Fork 0
Todos
Dignifiedquire edited this page Jan 1, 2013
·
6 revisions
I went through my list and these are the ones that I think are more important. Items within a section are ordered by priority.
- auto reload config change (at least files,exclude)
- timeout (per spec/suite)
- handle unload event (full page reload)
- sudden death (first failure, stop execution)
- global ~/.testacular config #64
- normalize browser errors
- use single port for web/cli (remove runner-port)
- don't synchronize browsers (don't wait for all browsers, just execute) + sharding
- better e2e framework (for testing Testacular)
- reorganize: plugins (reporters, preprocessors, adapters, launchers) #158
- refactor logger to support appending to files (log4js) #188
- refactor web server using connect #253 and #105
- don't watch non-matching files
- write some descriptions/comments to each module/component
- better release cycle, automate canary release ? #210
- git commit msg convention + generating changelog
- pre-commit hook (unmerged stuff, iit, ddescribe)
- pre-commit hook (check msg convention)
- JS Validator, see this post either as pre-commit hook or as grunt task
- polish the docs and publish it on the homepage