========
cf613656fe
Author: Nick Alexander <nalexander@mozilla.com>
Bug 1022749 - Part 2: Show custom server URLs in status activity.
========
91268a261f
Author: Nick Alexander <nalexander@mozilla.com>
Bug 1022749 - Part 1: Show custom server URLs in setup activities.
========
2582a39b7f
Author: Nick Alexander <nalexander@mozilla.com>
Bug 1022748 - Review comments.
========
8c9a8df84f
Author: Nick Alexander <nalexander@mozilla.com>
Bug 1022748 - Part 4: Don't show Get Started activity when custom server URLs are passed.
The Get Started activity provides no feedback about custom URLs, and it
just gets in the way of power users, so skip it entirely.
========
2701a9ea52
Author: Nick Alexander <nalexander@mozilla.com>
Date: Mon Jun 9 17:25:51 2014 -0700
Bug 1022748 - Part 3: Pass through server details to update credentials activity.
This information can be extracted from the AndroidFxAccount object in
the activity, but feeding the information through extras keeps the
processing and display pipeline uniform across all setup activities.
========
b9dd884764
Author: Nick Alexander <nalexander@mozilla.com>
Date: Mon Jun 9 17:17:57 2014 -0700
Bug 1022748 - Part 2: Use custom server URLs passed through extras in setup activities.
========
be8284ea25
Author: Nick Alexander <nalexander@mozilla.com>
Date: Mon Jun 9 15:06:03 2014 -0700
Bug 1022748 - Part 1: Pass extras through setup activities.
This also passes the password button's show/hide state between create
and set up.
========
ce21e7f19a
Author: Nick Alexander <nalexander@mozilla.com>
Date: Wed Jun 4 14:15:09 2014 -0700
Bug 1019793 - Always upload in TestHealthReportUploadService.
========
e4c7393c6f
Author: Nick Alexander <nalexander@mozilla.com>
Date: Tue Jun 3 15:47:33 2014 -0700
Bug 1019793 - Don't create storage in TestHealthReportPruneService.
Creating real storage requires a valid Context, and in this test, we
only have MockContext.
========
872d926e32
Author: Nick Alexander <nalexander@mozilla.com>
Date: Wed Jun 4 14:21:17 2014 -0700
Bug 993134 - Part 5: Work around Android intermittent issue.
========
c76bb53901
Author: Nick Alexander <nalexander@mozilla.com>
Date: Tue Jun 3 17:02:15 2014 -0700
Bug 993134 - Part 4: Make fxa.TestAccountPickler robust.
This tested extracting data from an AndroidFxAccount before, and another
after, backed by different Android Accounts. Unfortunately, one Account
replaced the other, but had the same name, leading to a race
condition (between reading and deleting the first account). To address
this, we extract all the data before deleting, and then compare it to
the data from the newly pickled account.
========
bd32978f7b
Author: Nick Alexander <nalexander@mozilla.com>
Date: Tue Jun 3 15:34:09 2014 -0700
Bug 993134 - Part 3: Use AndroidSyncTestCaseWithAccounts to make fxa.TestAccountPickler when accounts exist.
========
ec7d910187
Author: Nick Alexander <nalexander@mozilla.com>
Date: Tue Jun 3 15:33:29 2014 -0700
Bug 993134 - Part 2: Extract AndroidSyncTestCaseWithAccounts.
========
6563ad7bd8
Author: Nick Alexander <nalexander@mozilla.com>
Date: Tue Jun 3 15:30:15 2014 -0700
Bug 993134 - Part 1: Make getApplicationContext return getTargetContext.
I was finding that repeated instrumentation-test runs were returning a
null application context, indicating a race between test start-up and
target instantiation. This works well for me on two test devices.
reftest and crashtest manifests can now be added to the build
configuration via REFTEST_MANIFESTS and CRASHTEST_MANIFESTS,
respectively.
The master manifest files have been added to layout/moz.build.
This patch enables the deprecation of master reftest manifests but stops
short of doing it. In the future, we could declare reftest and crashtest
manifests in their nearest moz.build file and generate the master
manifest (consisting of a bunch of "include" directives) as part of
config.status.
--HG--
extra : rebase_source : 3503f787b14b24c38daf577a710e67b583476858
extra : histedit_source : 21e55b3d28ee83afb47f3f779251a13c2a90db5f
Now that we've established a slightly better Python reftest manifest
parser, switch the existing manifest parsing code in
print-manifest-dirs.py to use it.
--HG--
extra : rebase_source : 9559eb5aa47d08b9854a27ed012f2a795abc67f7
extra : histedit_source : 7a9a8942f9310c079a5ea4321a7f4f2ad17008d1
The immediate goal of this patch is to give the build system and testing
tools the knowledge to identify reftest files and directories. Parsing
extra metadata out of reftest manifests is currently a non-requirement,
but may be supported some day.
--HG--
extra : rebase_source : 279680af28c9175f5babe458a57203e8b19ab724
extra : histedit_source : c0e463ea02f87a376ef48e2b25136e5f6be4e61a
The removed code is never reached, as GetWindowProxy() returns a JSObject
with OuterWindowProxyClass as its JSClass, and this will test false for
IsDOMClass and
(~c->flags) & (JSCLASS_HAS_PRIVATE | JSCLASS_PRIVATE_IS_NSISUPPORTS).
