Closed Bug 896576 Opened 11 years ago Closed 11 years ago

[fig] Remove getAllPagesList/getBookmarksList/getHistoryList from BaseTest

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 26

People

(Reporter: Margaret, Assigned: capella)

References

Details

(Whiteboard: fixed-fig)

Attachments

(3 files, 2 obsolete files)

This methods don't do anything anymore (I disabled the tests that depend on them). Instead of re-implementing them for the new about:home, I think it would be better to create a utility class or something for testing things related to about:home, instead of continuing to dump things in BaseTest.
Assignee: nobody → markcapella
Status: NEW → ASSIGNED
Attached patch Remove [getAllPagesList] (obsolete) — Splinter Review
This removes the [getAllPagesList] pieces ... Let me know if I'm confused and you just wanted to remove those 6 method stubs in BaseTest and leave everything else in place (for later?) ...
Attachment #779532 - Flags: review?(margaret.leibovic)
Comment on attachment 779532 [details] [diff] [review] Remove [getAllPagesList] Review of attachment 779532 [details] [diff] [review]: ----------------------------------------------------------------- This is looking good, but I want to see a new version that doesn't delete so much stuff. I also want to make sure we file the follow-up bugs I mentioned. This is a good first step, but we'll need to replace the places that getAllPagesList is used with some other call to get the visited list in the new about:home. I'd like to see if there's a way we can make a utility class to get things from about:home, rather than sticking those methods back in BaseTest. ::: mobile/android/base/tests/robocop_autophone.ini @@ -4,5 @@ > # fails on gs2, nexus one, lg revolution, droid pro, nexus s > > -#[testAllPagesTab] > -# fails on gs2, nexus one, lg revolution, droid pro, nexus s > - Huh, I didn't know this file existed, we didn't update it in bug 880060. But if you're killing this test, this is the right thing to do. ::: mobile/android/base/tests/testAllPagesTab.java.in @@ -19,5 @@ > -/* Tests opening the all pages tab, that items look correct, clicking on an item > - and long tapping on an item > -*/ > - > -public class testAllPagesTab extends BaseTest { Please file a follow-up bug about replacing this test with a new testVisitedPage test. We can probably salvage some of the test logic from here in a new test for the new visited page. ::: mobile/android/base/tests/testAwesomebarSwipes.java.in @@ -21,5 @@ > > public void testAwesomebarSwipes() { > blockForGeckoReady(); > > - ListView list = getAllPagesList("about:firefox"); Let's just comment this line out for now, and add a comment saying that getAllPagesList was removed in this bug. This will make us less confused when someone goes to fix bug 896565. ::: mobile/android/base/tests/testShareLink.java.in @@ -82,5 @@ > - } else { > - // The view should not be null but sometimes getChildAt fails > - // TODO: Investigate why this fails > - mAsserter.todo_isnot(allpages, null, "View should not be null but sometimes it is"); > - } This is all commented out anyway, so we don't need to remove this right now. You can add a comment above the getAllPagesList call to say it was removed in this bug. Could you also file a bug to fix this part of this test (and have it block 895673)? We'll want to fix this, rather than just remove it.
Attachment #779532 - Flags: review?(margaret.leibovic) → feedback+
Bug 897481 - [fig] Update testShareLink.java.in - re-implement [Test share popup in Top Sites]
Bug 897483 - [fig] Create new testVisitedPage test to replace original testAllPagesTab.java.in
If this gets review+, I plan to move ahead to the next piece for [getBookmarksList] ... same approach as this one ...
Attachment #779532 - Attachment is obsolete: true
Attachment #780418 - Flags: review?(margaret.leibovic)
Comment on attachment 780418 [details] [diff] [review] Remove [getAllPagesList] Review of attachment 780418 [details] [diff] [review]: ----------------------------------------------------------------- Looks good to me. Thanks for filing those follow-ups.
Attachment #780418 - Flags: review?(margaret.leibovic) → review+
Attached patch Remove [getBookmarksList] (obsolete) — Splinter Review
for [getBookmarksList] I'm thinking you'll want to: Remove the method stubs in BaseTest Remove testBookmarksTab and file a bug to create a new testBookmarksPage Comment and file a bug to update |share popup in the Bookmarks tab| in testShareLink.java.in Comment and file a bug to update |runAwesomeScreenTest()| in testBookmark Comment and file a bug to update |bookmarklets clicked in awesomescreen| in testBookmarklets
Attachment #781321 - Flags: review?(margaret.leibovic)
Comment on attachment 781321 [details] [diff] [review] Remove [getBookmarksList] Review of attachment 781321 [details] [diff] [review]: ----------------------------------------------------------------- Looks good, but make sure you get those follow-up bugs filed. ::: mobile/android/base/tests/robocop_autophone.ini @@ +9,5 @@ > > #[testAxisLocking] > # fails on gs2, nexus one, lg revolution, droid pro, nexus s > > +# [testBookmark] I don't think we should disable these on fig, since they're not posing a problem for us right now on TBPL, and I don't want us to forget about re-enabling them. ::: mobile/android/base/tests/testBookmark.java.in @@ +38,5 @@ > mAsserter.is(true, false, "Unable to find method"); > } > > + // Removed by Bug 896576 - [fig] Remove [getBookmarksList] from BaseTest > + // runAwesomeScreenTest(); With this disabled, does this test pass? Maybe we could re-enable testBookmark if that's the case, then fix this part in a follow-up. ::: mobile/android/base/tests/testBookmarklets.java.in @@ +59,5 @@ > } > if (!found) { > mAsserter.is(found, true, "Found the bookmark: " + js + " and clicked on it"); > } > + */ Same question here, I wonder if we could just comment out enough broken code to get the test to pass, re-enable it, and fix this part in a follow-up. If it's non-trivial to try to fix it though, we can just deal with the re-enabling part in the follow-up. ::: mobile/android/base/tests/testShareLink.java.in @@ +90,2 @@ > // Test the share popup in the Bookmarks tab > ListView blist = getBookmarksList("about:firefox"); At first I was confused, then realized that this is in the middle of a commented-out chunk :)
Attachment #781321 - Flags: review?(margaret.leibovic) → review+
Quick question for later ... why the diff between robocop.ini and robocop_autophone.ini ? Should any given robocop test be defined in both robocop.ini and robocop_autophone.ini, or is it an either/or situation? (I see active 7 tests run from both places) (8 counting testMigration but we removed that in m-c) [testAboutPage], [testAwesomebar], [testBrowserProvider], [testFormHistory], [testNewTab], [testPasswordProvider], [testSystemPages]
Bug 899182 - [fig] Re-implement robocop testBookmark.java.in
Bug 899183 - [fig] Re-implement robocop testBookmarklets.java.in
Bug 899185 - [fig] Update testShareLink.java.in - re-implement [Test the share popup in the Bookmarks tab]
Bug 899187 - [fig] Create new testBookmarksPage test to replace original testBookmarksTab.java.in
Without getBookmarksList() there's really nothing of value in partially enabling the remaining tests, so I've left then disabled as before.
Attachment #781321 - Attachment is obsolete: true
Attachment #782735 - Flags: review?(margaret.leibovic)
Comment on attachment 782735 [details] [diff] [review] Remove [getBookmarksList] Review of attachment 782735 [details] [diff] [review]: ----------------------------------------------------------------- Once again, thanks for filing all those follow-up bugs.
Attachment #782735 - Flags: review?(margaret.leibovic) → review+
Comment on attachment 782735 [details] [diff] [review] Remove [getBookmarksList] then it's on to the last piece |getHistoryList| https://hg.mozilla.org/projects/fig/rev/9b7ae4a52863
Attachment #782735 - Flags: checkin+
Attachment #780418 - Flags: checkin+
Followup bugs after getHistoryList() removal... Bug 900105 - [fig] Create new testHistoryPage test to replace original testHistoryTab.java.in Bug 900107 - [fig] Update testShareLink.java.in - re-implement [Test the share popup in the History tab] Bug 900109 - [fig] Re-implement robocop testClearPrivateData.java.in Bug 900110 - [fig] Re-implement robocop testHistory.java.in
Getting close to finished here :-)
Attachment #783863 - Flags: review?(margaret.leibovic)
Comment on attachment 783863 [details] [diff] [review] Remove [getHistoryList] Looks good. With this, we can close out this bug. And now we'll have to actually think about what kind of utility we'd want to make for getting these pages! There are a handful of fig test patches in my review queue, so maybe some of them start to address this.
Attachment #783863 - Flags: review?(margaret.leibovic) → review+
Comment on attachment 783863 [details] [diff] [review] Remove [getHistoryList] Corrected attachment name https://hg.mozilla.org/projects/fig/rev/b0e8ef08abae
Attachment #783863 - Attachment description: Remove [getBookmarksList] → Remove [getHistoryList]
Attachment #783863 - Flags: checkin+
Whiteboard: fixed-fig
See bug 901432, it looks like that is going to re-implement the shared methods we need (or at least provide a place for us to put those methods).
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 26
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: