Closed
Bug 650580
Opened 13 years ago
Closed 10 years ago
[READY] Test for bug 624047 needs to be explicit about its setTimeout requirements
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)
References
Details
Attachments
(1 file)
865 bytes,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•13 years ago
|
||
Comment 2•13 years ago
|
||
Also, we could think of adding some test API that can force call of the code that is normally invoked by the internal storage timer and get rid of setTimeout from the test at all then.
Attachment #526551 -
Flags: review?(jonas) → review+
Assignee | ||
Updated•13 years ago
|
Summary: Test for bug 624047 needs to be explicit about its setTimeout requirements → [READY] Test for bug 624047 needs to be explicit about its setTimeout requirements
Assignee | ||
Comment 3•13 years ago
|
||
(In reply to comment #2) > Also, we could think of adding some test API that can force call of the code > that is normally invoked by the internal storage timer and get rid of > setTimeout from the test at all then. Great. Is this something that you can work on, please?
Comment 4•13 years ago
|
||
(In reply to comment #3) > Great. Is this something that you can work on, please? Yes, but not sure how soon I can get to this. It's a large change and needs good testing and thinking if that is going to test what needs to be tested. But yes, I can do that.
Assignee | ||
Comment 5•13 years ago
|
||
(In reply to comment #4) > (In reply to comment #3) > > Great. Is this something that you can work on, please? > > Yes, but not sure how soon I can get to this. It's a large change and needs > good testing and thinking if that is going to test what needs to be tested. > But yes, I can do that. Great. I guess we can proceed with this patch for now, but I filed bug 653593 to track the future improvements here.
Assignee | ||
Comment 6•10 years ago
|
||
Bug 600307 removed this test.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Assignee | ||
Comment 7•10 years ago
|
||
Oops, I landed an empty patch for this by mistake: https://hg.mozilla.org/integration/mozilla-inbound/rev/5992fd8e82d0
Comment 8•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/5992fd8e82d0
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•