| 38210445730ee04c351c7cc1b3800cfe23e34325 |
|
27-Jun-2012 |
Makoto Onuki <omakoto@google.com> |
Reorganize import in contacts provider
Change-Id: If3afb134ea36bd93859efcd114885526e1592b91
/packages/providers/ContactsProvider/tests/src/com/android/providers/contacts/EvenMoreAsserts.java
|
| 63630bc7f962fd2b6f2c1bc41cbed45a8bc354ba |
|
17-Apr-2012 |
Makoto Onuki <omakoto@google.com> |
Use 3 bucket sorting logic for frequent.
Bug 6343819
Change-Id: Id2a2827fca611e62a5a1406faa73026625feaede
/packages/providers/ContactsProvider/tests/src/com/android/providers/contacts/EvenMoreAsserts.java
|
| 87426833d4c2c626e032f5d0b84a08b58024daf6 |
|
17-Apr-2012 |
Makoto Onuki <omakoto@google.com> |
Fix the last failing photo test
Also add some nice features to the asserts for complex data.
- assertImageRawData() now writes the expected and actual images to the
cache dir when failing.
- assertStoredValues() and its siblings now dump the cursor to logcat
when failing.
Bug 6280711
Change-Id: I77aff61b0494580d0b2ba24b35eb045a18cd48c8
/packages/providers/ContactsProvider/tests/src/com/android/providers/contacts/EvenMoreAsserts.java
|
| c23a30e0510cf56d1dafddc79d1ab99ae9297a3f |
|
12-Apr-2012 |
Makoto Onuki <omakoto@google.com> |
Fix most of photo tests
Adjusting existing unit tests for higher res photos turned out to be tricky,
because the size of the test images were selected for 256x256.
(e.g. cropping tests)
Also we don't want the display photo size to change depending on the running
device.
So let's just keep using 256x256 for all unit tests.
Added new asserts to EvenMoreAssert to compare image raw data, which prints
actual/expected dimensions when it fails.
Even with this CL, ContactsProvider2Test.testInputStreamForPhoto() still fails
with the following assert message. The image size seems to be correct, so I'm
not sure why. This may be because we've changed the compression rate, but
I didn't dig into it.
"Different data lengths: expected=1088 actual=1578,
expected dimentions=[96 x 96] actual dimentions=[96 x 96]"
Anyway, with this CL at least PhotoStoreTest will no longer crash, so let's
merge it now and take care of the failing test later.
Change-Id: I935f76acee3c2de99030c62e14f43de07074fb8a
/packages/providers/ContactsProvider/tests/src/com/android/providers/contacts/EvenMoreAsserts.java
|
| 00e7c94b70f4b477653534dbe559d1759d796157 |
|
16-Jun-2011 |
Debashish Chatterjee <debashishc@google.com> |
Added checks in voicemail provider to not expose call_log fields.
- Voicemail provider now has check to ensure that no field outside of its
projection is accesible.
- Moved functionality to check ContentValues against a projection map to
DbQueryUtils.
- Associated test cases.
Change-Id: I23033c96f74f0ab981152f70e585c69ba5284602
/packages/providers/ContactsProvider/tests/src/com/android/providers/contacts/EvenMoreAsserts.java
|
| 59f6477e10203617f504857f7e9aee2fda393f4f |
|
07-Jun-2011 |
Debashish Chatterjee <debashishc@google.com> |
Introduced new voicemail fields in 'calls' table.
The 'calls' table is going to be shared between the existing call_log
provider, and to be added voicemail provider. This change adds all the
columns needed to support voicemail in the 'calls' table.
The call_log provider, however, uses only one additional field
'voicemail_uri', whereas all other new fields will exclusively be used the
new voicemail provider. The change also ensures that the voicemail
provider specific fields are not exposed through the call_log provider.
Change-Id: Ieea4b14052b7e7e9db0e674138772b4e06b3f074
/packages/providers/ContactsProvider/tests/src/com/android/providers/contacts/EvenMoreAsserts.java
|