Closed Bug 585730 Opened 14 years ago Closed 14 years ago

Make Mozmill-test testSuggestHistoryBookmarks local

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: u279076, Assigned: aaronmt)

References

Details

(Whiteboard: [litmus-data])

Attachments

(3 files, 1 obsolete file)

Module: testAwesomeBar/testSuggestHistoryBookmarks.js Test-page: Use any 1 page from test-files/layout/mozilla*
Blocks: 579965
Assignee: nobody → aaron.train
Status: NEW → ASSIGNED
Unsure if I should proceed with the changes here or if it's best to wait for a clean test with a fix from bug 592411
(In reply to comment #1) > Unsure if I should proceed with the changes here or if it's best to wait for a > clean test with a fix from bug 592411 The two are unrelated. You should be able to make this test local without affecting any changes in testPlacesAPI.js.
Attached patch Patch v1 - (default) (deleted) — Splinter Review
cleanup + converts test to make use of local content and data
Attachment #471182 - Flags: review?(anthony.s.hughes)
Comment on attachment 471182 [details] [diff] [review] Patch v1 - (default) >+ for each (var entry in entries) { > controller.assertJS("subject.enteredTitle == subject.underlinedTitle", >+ {enteredTitle: LOCAL_TEST_PAGE.string, underlinedTitle: entry.toLowerCase()}); Can you put each member on its own line? >+ for each (var entry in entries) { > controller.assertJS("subject.enteredTitle == subject.underlinedTitle", >+ {enteredTitle: LOCAL_TEST_PAGE.string, underlinedTitle: entry.toLowerCase()}); > } Same here please.
Attachment #471182 - Flags: review?(anthony.s.hughes) → review-
Attached patch Patch v1.1 - [nit fixes] - (default) (obsolete) (deleted) — Splinter Review
Attachment #473526 - Flags: review?(anthony.s.hughes)
Attachment #473526 - Attachment is obsolete: true
Attachment #473526 - Flags: review?(anthony.s.hughes)
Attachment #473530 - Flags: review?(anthony.s.hughes)
Attachment #473530 - Flags: review?(hskupin)
Attachment #473530 - Flags: review?(anthony.s.hughes)
Attachment #473530 - Flags: review+
Comment on attachment 473530 [details] [diff] [review] Patch v1.1 - [nit fixes] - (default) >-var setupModule = function(module) >+var setupModule = function() nit: bracket fixes please. Otherwise r=me.
Attachment #473530 - Flags: review?(hskupin) → review+
Keywords: checkin-needed
(In reply to comment #6) > Created attachment 473530 [details] [diff] [review] > Patch v1.1 - [nit fixes] - (default) This patch causes a regression failure... Fail: controller.assertJS: Failed for 'subject.getNumberOfVisibleRows() == 1' File: firefox/testAwesomeBar/testSuggestHistoryBookmarks.js:96 Please fix this failure and resubmit your patch.
Keywords: checkin-needed
Attached patch Patch v1.2 - (default) (deleted) — Splinter Review
(In reply to comment #8) > (In reply to comment #6) > > Created attachment 473530 [details] [diff] [review] [details] > > Patch v1.1 - [nit fixes] - (default) > > This patch causes a regression failure... > > Fail: controller.assertJS: Failed for 'subject.getNumberOfVisibleRows() == 1' > File: firefox/testAwesomeBar/testSuggestHistoryBookmarks.js:96 > > Please fix this failure and resubmit your patch. Ah, we we're using a unique site in the online version - 'litmus'. When typed into the awesomebar, it was unique enough to pull in one visible row. When we switched to generic local mozilla pages, we were using 'mozilla', which pulled in the default bookmarks as well. I changed this to mozilla-grants and we type 'grants' if that's alright. We pull in one visible row like before. Second failure is due to bug 592411
Attachment #478033 - Flags: review?(anthony.s.hughes)
Comment on attachment 478033 [details] [diff] [review] Patch v1.2 - (default) Regression seems to have been fixed. r+
Attachment #478033 - Flags: review?(anthony.s.hughes) → review+
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Move of Mozmill Test related project bugs to newly created components. You can filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Product: Testing → Mozilla QA
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: