703062 - GCLI should do some coverage analysis to improve test coverage

Status: RESOLVED FIXED

(DevTools :: Console, defect, P2)

Comment 1

[Joe Walker [:jwalker]]

Moving GCLI bugs to Developer Tools: Console. Filter on 'baked beans are off'.

Comment 2

[Joe Walker [:jwalker]]

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

Comment 3

[Joe Walker [:jwalker]]

Attachment: upload 1

a.k.a https://github.com/campd/gcli/pull/7

Comment 4

[Joe Walker [:jwalker]]

https://tbpl.mozilla.org/?tree=Try&rev=8566837e9d3d

Comment 5

[Tim Taubert [:ttaubert] (inactive)]

https://hg.mozilla.org/mozilla-central/rev/5e39ff32da82