Closed
Bug 686032
Opened 13 years ago
Closed 13 years ago
Test for bug 622088 conceals its location after it's done
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
mozilla9
People
(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)
References
Details
Attachments
(1 file)
(deleted),
patch
|
ted
:
review+
justin.lebar+bug
:
review+
|
Details | Diff | Splinter Review |
My patch in bug 668728 requires that when each test is finished, its location won't change. The test for bug 622088 breaks this invariant, by using history.replaceState. I have a simple patch to fix this.
Assignee | ||
Comment 1•13 years ago
|
||
Comment 2•13 years ago
|
||
Comment on attachment 559603 [details] [diff] [review]
Patch (v1)
Review of attachment 559603 [details] [diff] [review]:
-----------------------------------------------------------------
Fine, but again, I'd really prefer the original test authors to r+ these.
Attachment #559603 -
Flags: review?(ted.mielczarek) → review+
Assignee | ||
Updated•13 years ago
|
Attachment #559603 -
Flags: review?(justin.lebar+bug)
Comment 3•13 years ago
|
||
Copy-pasted from bug 685788 comment 3:
(In reply to Ehsan Akhgari [:ehsan] from comment #0)
> My patch in bug 668728 requires that when each test is finished, its
> location won't change.
It's not a problem if the test fails (e.g. throws an exception) and leaves the location different than it was initially?
ed. to add: The failure mode for many of these tests is to hang and not get to the SimpleTest.finish() call.
Assignee | ||
Comment 4•13 years ago
|
||
(In reply to Justin Lebar [:jlebar] from comment #3)
> Copy-pasted from bug 685788 comment 3:
>
> (In reply to Ehsan Akhgari [:ehsan] from comment #0)
> > My patch in bug 668728 requires that when each test is finished, its
> > location won't change.
>
> It's not a problem if the test fails (e.g. throws an exception) and leaves
> the location different than it was initially?
>
> ed. to add: The failure mode for many of these tests is to hang and not get
> to the SimpleTest.finish() call.
That should be fine, as my patch in bug 668728 would catch that as an explicit failure. So we'll have one timeout, and one explicit failure. Which is even better than only a timeout. ;-)
Comment 5•13 years ago
|
||
Comment on attachment 559603 [details] [diff] [review]
Patch (v1)
Cool; sounds like a plan!
Attachment #559603 -
Flags: review?(justin.lebar+bug) → review+
Assignee | ||
Comment 6•13 years ago
|
||
Flags: in-testsuite+
Target Milestone: --- → mozilla9
Comment 7•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•