Closed
Bug 657598
Opened 14 years ago
Closed 13 years ago
GCLI needs browser run tests in addition to internal unit tests
Categories
(DevTools :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jwalker, Assigned: jwalker)
Details
i.e. Selenium (probably)
Assignee | ||
Updated•14 years ago
|
Blocks: GCLI-ENABLE
Comment 1•14 years ago
|
||
Started writing a selenium test suite, see the last couple commits on https://github.com/fitzgen/gcli/commits/bug-657598-selenium-tests
So far I have:
* A simple test which walks through executing the help command.
* A test which runs the unit tests and asserts that none failed.
* A test for command history which makes sure that bounds behave properly when you try to go too far backward or forward through history.
Updated•14 years ago
|
Assignee: nobody → nfitzgerald
Version: Trunk → 6 Branch
Assignee | ||
Updated•13 years ago
|
Assignee: nfitzgerald → jwalker
Assignee | ||
Updated•13 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•13 years ago
|
||
selenium would be nice, but we're better off having something that can work within firefox
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•13 years ago
|
No longer blocks: GCLI-FUTURE
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•