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
This commit is contained in:
@@ -1,19 +1,5 @@
|
||||
LOCAL_PATH:= $(call my-dir)
|
||||
LOCAL_PATH := $(call my-dir)
|
||||
include $(CLEAR_VARS)
|
||||
|
||||
# We only want this apk build for tests.
|
||||
LOCAL_MODULE_TAGS := tests
|
||||
LOCAL_CERTIFICATE := platform
|
||||
|
||||
LOCAL_JAVA_LIBRARIES := android.test.runner bouncycastle
|
||||
|
||||
LOCAL_STATIC_JAVA_LIBRARIES := android-support-test mockito-target
|
||||
|
||||
# Include all test java files.
|
||||
LOCAL_SRC_FILES := $(call all-java-files-under, src)
|
||||
|
||||
LOCAL_PACKAGE_NAME := SettingsTests
|
||||
|
||||
LOCAL_INSTRUMENTATION_FOR := Settings
|
||||
|
||||
include $(BUILD_PACKAGE)
|
||||
# Include all makefiles in subdirectories
|
||||
include $(call all-makefiles-under,$(LOCAL_PATH))
|
||||
|
||||
Reference in New Issue
Block a user