PawletOS/app_Settings
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
32,635 Commits 1 Branch 0 Tags
d7cb15e33febabf276024f888645964871e78e15
Commit Graph

4 Commits

Author SHA1 Message Date
Matthew Fritze
172eac4c51 Test the Columns in the SearchIndexablesContract 
The test is going into settings because of the lack testing
support in framework/base for this kind of change, and
because Settings search depends on this change.

Test: make RunSettingsUnitTests
Bug: 33390556
Change-Id: I8a87d4228a37fca475791409b89c7d135c29004a
 2016-12-07 09:45:51 -08:00
Guang Zhu
2705ae35f9 Avoid JUnit4 collision in android-support-test, mockito-target 
Bug: 31072145
Test: make droid checkbuild

Change-Id: I7f2b13a4c28e51d76313ee3b6d13c904c2925228
 2016-08-25 19:43:16 +00:00
Salvador Martinez
3fb4e96b0d Tests for launch support on default feature 
Includes some espresso tests to ensure that the proper
tab is selected when you attempt to launch settings.

Bug: 30233920
Change-Id: I171293114bd84b064b333091fcf2394d44debed5
(cherry picked from commit d1ef20beaa)
 2016-08-22 21:52:46 +00:00
Benjamin Franz
d11b713a9f Change build targets for settings tests 
1. Split existing tests into fully automatable (unit/) and not fully
automatable (app/)
2. Revert previous changes to test runners on app/
3. Fix some typos in readme

This will enable us to add the fully automatable test target
SettingsUnitTests to the continuous integration tests on the platform.

Change-Id: I0f42c59fde84891e4bfc379150c2f0c61ce1329f
 2016-01-21 12:32:15 +00:00