Closed
Bug 870056
Opened 12 years ago
Closed 12 years ago
Enable testClearPrivateData
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 24
People
(Reporter: gbrown, Assigned: gbrown)
Details
Attachments
(2 files)
|
5.94 KB,
patch
|
jmaher
:
review+
|
Details | Diff | Splinter Review |
|
8.90 KB,
patch
|
jmaher
:
review+
|
Details | Diff | Splinter Review |
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.
| Assignee | ||
Comment 1•12 years ago
|
||
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).
https://tbpl.mozilla.org/?tree=Try&rev=accfdbb77986
Attachment #747080 -
Flags: review?(jmaher)
Comment 2•12 years ago
|
||
Comment on attachment 747080 [details] [diff] [review]
enable testClearPrivateData
Review of attachment 747080 [details] [diff] [review]:
-----------------------------------------------------------------
::: mobile/android/base/tests/testClearPrivateData.java.in
@@ +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
> + mAsserter.is(mSolo.waitForText("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+
| Assignee | ||
Comment 3•12 years ago
|
||
Whiteboard: [leave open]
Comment 4•12 years ago
|
||
Flags: in-testsuite+
| Assignee | ||
Comment 5•12 years ago
|
||
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: https://tbpl.mozilla.org/?tree=Try&rev=a4dfd8c56685
Attachment #747958 -
Flags: review?(jmaher)
Comment 6•12 years ago
|
||
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+
| Assignee | ||
Comment 7•12 years ago
|
||
There is a try run shown in Comment 5, and here's another: https://tbpl.mozilla.org/?tree=Try&rev=52fc4b3050cb. 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.
| Assignee | ||
Comment 8•12 years ago
|
||
https://tbpl.mozilla.org/?tree=Try&rev=9e4cfc429deb looks good now.
https://hg.mozilla.org/integration/mozilla-inbound/rev/1d741cce312b
Whiteboard: [leave open]
Comment 9•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 24
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•