Previously left was considered positive and right considered negative.
Now left and down are negative, and right and up are positive.
For RTL, left is positive and right is negative.
Change-Id: Ia31e8c687c8c2716fc632b2fe88aa8955b934bce
I split testMigrateProfileId into two tests: one testing the migration
and one testing changing the default column test.
Since testChangeDefaultColumnTest does not migrate any profile ids, the
correct answer is indeed 1 and not 6. Next time I will be sure to run the
tests first :).
Change-Id: I7557e198072ed134c8b42d6187afcb93d388c5a1
This is a risky business, as we can be broken by platform changes like:
b/118891218
Note that TAPL itself still uses pressing Home button.
Change-Id: I55772622fac5f19f6c9f19716a185bbfdbf602a9
These tests call sendPointer() which fails with
"Injecting to another application requires INJECT_EVENTS permission".
Will re-add them later.
Test: running those in OOP and in-proc
Change-Id: I1c96fad14cf8bef896209a94065614a6207ea751
Moving some tests to TaplTests. It's a right idea in general, also
flakes seem to go away because of a different initialization pattern.
Reintroducing UIDevice.pressHome in the test's start. Once BVTs pass,
I'll switch back.
See b/121335479
Test: All nexus tests
Change-Id: I677be5b6aaf073d15e8f2cf9b7a940a1f457b325
On the AOSP target, there are not enough apps to make App Apps
scrollable. Moving the test to QS Tapl tests.
Change-Id: I95e196bafdbd0fee77705554890a7c3cda7ac92a
Tests: the affected test
This will allow running as many as possible automatic checks on AOSP
launcher and moving most AOSP tests that use TAPL to where they belong
to: Tapl Tests.
Bug: 110103162
Test: Running the test suites
Change-Id: I9192354e6097698d4b942c5682b79664ecc2336d
Doing so by not letting any events between XXX:enter and XXX:exit
events. This eliminates unnecessary permutations.
Example: 2 threads with 3 enter-exit pairs each would have produced 924
permutations before this, now only 20.
Bug: 120628042
Change-Id: Ia243d273a1d90202011679cc7520ea4c9e43918b
Tests: All tests that use race condition framework
This would guaranteed to repro b/118441555 before it was fixed.
The test doesn't use the most powerful feature of race condition
reproducer, which is enumerating all possible event sequences.
Instead, it uses explicit repro sequences, which makes the test much
faster.
Bug: 120628042
Test: The added test
Change-Id: I89a7a9964f160a8a20ba3d9dda2f248237713014
Removing a separate table for workspace screens. List of screens are
automatically parsed using the items in the favorites DB. Order of the
screen based on the screen id and rearranging screens is no longer
supported. In case the screens need to be rearranged, all the items
in the favorites db will need to be updated with new screen ids.
This makes backing up the DB (in the same database) easier as only
one table needs to be duplicates.
Change-Id: I8ba947a898f637d780e2f49925e78604263126e8
> Adding resource based allowing projects to control cache behavior
> Fixing missing comments from ag/5470467
> Adding support for no-immemory cache
Bug: 115891474
Change-Id: I691206805430cd93d3be78119bc249cefd79790a
I cloned the existing Instrumentation-based IntSetTest class
to be our first Robolectric test. Now Robolectric is working,
we can delete the Instrumentation test version.
Change-Id: I3adcfc451988a908c002b769b398348cb1782f1d
