Closed Bug 703062 Opened 9 years ago Closed 9 years ago
GCLI should do some coverage analysis to improve test coverage
No description provided.
Depends on: 663081
Depends on: 664207
Depends on: 664377
Depends on: 664203
Moving GCLI bugs to Developer Tools: Console. Filter on 'baked beans are off'.
Component: Developer Tools → Developer Tools: Console
Coverage tests run. It's painful on windows. TODO: Run tests under node Run tests in chrome under coverage tools Add a command with param groups, use one of the params Add a command with a defaultValue, check it gets through and is over-ridden Add a command with an array param, use 0, 1, 2 params Remove a command check it's gone Register a listener with canon.commandOutputManager, check output gets through Call canon.getCommandNames Use a command with a script argument Use a command with a merged argument Use a command with a boolean argument (both ways) Use a command with a named argument Increment and decrement a number argument Use a command with a selection argument Increment and decrement a selection argument Complete a JS argument Complete a selection argument Check an iterator is not called by completion Use a command with a node argument that passes/fails no match/fails multiple match Call Status.combine Alter an argument at position 3, check contents of arg at position 2 (prev empty) Check Assignment.getStatus Execute a JS command Call Requisition: .getStatus, .getArgsObject, .getAssignment(num, string), .toCanonicalString() .getInputStatusMarkup() .getAssignmentAt Check all the escaped chars get through OK Find a way to call Requisition._assign/._tokenize ?! Complete a command Test history Exercise all Fields
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 11
You need to log in before you can comment on or make changes to this bug.