Closed
Bug 773313
Opened 13 years ago
Closed 12 years ago
GCLI: Not possible to test the output of async commands
Categories
(DevTools Graveyard :: Graphic Commandline and Toolbar, defect, P2)
DevTools Graveyard
Graphic Commandline and Toolbar
Tracking
(Not tracked)
RESOLVED
FIXED
Future
People
(Reporter: miker, Unassigned)
References
Details
(Whiteboard: [gclicommands])
Using the following for any async command fails:
DeveloperToolbarTest.exec({
typed: "somecommand",
outputMatch: /pattern/
});
This is because we have no immediate output from async commands
Comment 1•13 years ago
|
||
Triage, filter on TEABAGS
Priority: -- → P1
Target Milestone: --- → Firefox 17
Comment 2•13 years ago
|
||
Triage: Filter on the TRIAGE keyword.
Priority: P1 → P2
Target Milestone: Firefox 17 → Future
Comment 3•13 years ago
|
||
New component triage. Filter on "Lobster Thermidor aux crevettes with a Mornay sauce"
Component: Developer Tools → Developer Tools: Graphic Commandline and Toolbar
Comment 4•12 years ago
|
||
Fixed with bug 685526
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Firefox → DevTools
Updated•7 years ago
|
Product: DevTools → DevTools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•