aboutsummaryrefslogtreecommitdiffstats
path: root/components/script/dom/bindings/codegen
diff options
context:
space:
mode:
authorbors-servo <metajack+bors@gmail.com>2015-01-16 08:18:46 -0700
committerbors-servo <metajack+bors@gmail.com>2015-01-16 08:18:46 -0700
commite7d79842a85dfa8eaee8c2f441977edbf061bbed (patch)
treed884ed9055bc5e0930af4286f2408e3c84c5838b /components/script/dom/bindings/codegen
parent9fd675c266a85317198e89f9eb0e917af5a405d0 (diff)
parentd0cc2801197773df8e1db15cf370b2fb94a98b6f (diff)
downloadservo-e7d79842a85dfa8eaee8c2f441977edbf061bbed.tar.gz
servo-e7d79842a85dfa8eaee8c2f441977edbf061bbed.zip
auto merge of #4569 : donaldpipowitch/servo/add-unit-tests-for-textinput, r=jdm
Please bear with me. This is the first Rust code I've ever written and the first systems programming language I've ever used. I've added unit tests for all methods of TextInput ( - except `handle_keydown`). I probably didn't cover all cases - I don't know if this is a real requirement until we have some coverage tools which identify all missing cases easily. If someone could show me how to create a `KeyboardEvent` easily I could add another test for `handle_keydown`. Other questions: 1. Running `$ time ./mach test-unit -c script test_textinput` takes `3m29.536s` on my MacBook Pro (2012). Any hints on speeding this up? 2. Who is responsible for the feedback of the unit tests? It would be nice if the output could be colored (e.g. make `11 passed;` green, `0 failed;` red and so on.)
Diffstat (limited to 'components/script/dom/bindings/codegen')
0 files changed, 0 insertions, 0 deletions