Closed Bug 870056 Opened 8 years ago Closed 8 years ago

Enable testClearPrivateData


(Firefox for Android Graveyard :: General, defect)

Not set


(Not tracked)

Firefox 24


(Reporter: gbrown, Assigned: gbrown)



(2 files)

Robocop test testClearPrivateData was disabled while investigating Panda instability. We should enable it now.

Unfortunately, there were changes to the menu structure while it was disabled -- we need to accommodate those changes.
On tablets, Clear Private Data is in a Privacy and Security section now. We need to select the section, then the item. 

While I was at it, I increased the max wait time for the notification; this allows the test to pass on my Galaxy S, for the first time ever (see bug 837274).
Attachment #747080 - Flags: review?(jmaher)
Comment on attachment 747080 [details] [diff] [review]
enable testClearPrivateData

Review of attachment 747080 [details] [diff] [review]:

::: mobile/android/base/tests/
@@ +34,4 @@
>          mAsserter.ok(mSolo.searchButton("Clear data"),"checking clear button","clear button exists");
>          mSolo.clickOnButton("Clear data");
> +        // TODO: extra long wait here for bug 837274
> +"Private data cleared", 0, 60000),true,"private data cleared successfully");

I really don't like this 60 second wait, but I do like tests that work!
Attachment #747080 - Flags: review?(jmaher) → review+
The first patch introduced some utilities in BaseTest; this patch uses those changes to clean up some other tests.

Try run is a little disappointing, but I think the failures are just existing issues:
Attachment #747958 - Flags: review?(jmaher)
Comment on attachment 747958 [details] [diff] [review]
(2) Follow-up: use BaseTest.mDevice and selectSettingsItem()

Review of attachment 747958 [details] [diff] [review]:

do we have a try run with a handful of retriggers?  some of these tests are changing enough that I would like some assurance this is not making it worse.
Attachment #747958 - Flags: review?(jmaher) → review+
There is a try run shown in Comment 5, and here's another: I think the patch is OK, but rc2 is not reliable enough right now to get a reassuring try run. I will not land this just yet.
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 24
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.