48 lines
1.5 KiB
C
Raw Normal View History

Add a new build, install, test development (bit) tool This is a cleaned up version of a utility that I've had sitting around for a while. The bit tool can run an android platform build, then sync or install the outputs of that, and then run instrumentation tests. It's better than what we usually do: make && adb shell stop && adb sync system && adb shell start Here's the help text: usage: bit OPTIONS PATTERN Build, sync and test android code. The -b -i and -t options allow you to specify which phases you want to run. If none of those options are given, then all phases are run. If any of these options are provided then only the listed phases are run. OPTIONS -b Run a build -i Install the targets -t Run the tests PATTERN One or more targets to build, install and test. The target names are the names that appear in the LOCAL_MODULE or LOCAL_PACKAGE_NAME variables in Android.mk or Android.bp files. Building and installing ----------------------- The modules specified will be built and then installed. If the files are on the system partition, they will be synced and the attached device rebooted. If they are APKs that aren't on the system partition they are installed with adb install. For example: bit framework Builds framework.jar, syncs the system partition and reboots. bit SystemUI Builds SystemUI.apk, syncs the system partition and reboots. bit CtsProtoTestCases Builds this CTS apk, adb installs it, but does not run any tests. Running Unit Tests ------------------ To run a unit test, list the test class names and optionally the test method after the module. For example: bit CtsProtoTestCases:* Builds this CTS apk, adb installs it, and runs all the tests contained in that apk. bit framework CtsProtoTestCases:* Builds the framework and the apk, syncs and reboots, then adb installs CtsProtoTestCases.apk, and runs all tests contained in that apk. bit CtsProtoTestCases:.ProtoOutputStreamBoolTest bit CtsProtoTestCases:android.util.proto.cts.ProtoOutputStreamBoolTest Builds and installs CtsProtoTestCases.apk, and runs all the tests in the ProtoOutputStreamBoolTest class. bit CtsProtoTestCases:.ProtoOutputStreamBoolTest\#testWrite Builds and installs CtsProtoTestCases.apk, and runs the testWrite test method on that class. bit CtsProtoTestCases:.ProtoOutputStreamBoolTest\#testWrite,.ProtoOutputStreamBoolTest\#testRepeated Builds and installs CtsProtoTestCases.apk, and runs the testWrite and testRepeated test methods on that class. Launching an Activity --------------------- To launch an activity, specify the activity class name after the module name. For example: bit StatusBarTest:NotificationBuilderTest bit StatusBarTest:.NotificationBuilderTest bit StatusBarTest:com.android.statusbartest.NotificationBuilderTest Builds and installs StatusBarTest.apk, launches the com.android.statusbartest/.NotificationBuilderTest activity. Change-Id: I9cff7a23852fa1a67369e7807f7ae9f6e45d6131 Test: none
2016-10-19 17:03:06 -07:00
/*
* Copyright (C) 2016 The Android Open Source Project
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
#ifndef ADB_H
#define ADB_H
#include "proto/instrumentation_data.pb.h"
Add a new build, install, test development (bit) tool This is a cleaned up version of a utility that I've had sitting around for a while. The bit tool can run an android platform build, then sync or install the outputs of that, and then run instrumentation tests. It's better than what we usually do: make && adb shell stop && adb sync system && adb shell start Here's the help text: usage: bit OPTIONS PATTERN Build, sync and test android code. The -b -i and -t options allow you to specify which phases you want to run. If none of those options are given, then all phases are run. If any of these options are provided then only the listed phases are run. OPTIONS -b Run a build -i Install the targets -t Run the tests PATTERN One or more targets to build, install and test. The target names are the names that appear in the LOCAL_MODULE or LOCAL_PACKAGE_NAME variables in Android.mk or Android.bp files. Building and installing ----------------------- The modules specified will be built and then installed. If the files are on the system partition, they will be synced and the attached device rebooted. If they are APKs that aren't on the system partition they are installed with adb install. For example: bit framework Builds framework.jar, syncs the system partition and reboots. bit SystemUI Builds SystemUI.apk, syncs the system partition and reboots. bit CtsProtoTestCases Builds this CTS apk, adb installs it, but does not run any tests. Running Unit Tests ------------------ To run a unit test, list the test class names and optionally the test method after the module. For example: bit CtsProtoTestCases:* Builds this CTS apk, adb installs it, and runs all the tests contained in that apk. bit framework CtsProtoTestCases:* Builds the framework and the apk, syncs and reboots, then adb installs CtsProtoTestCases.apk, and runs all tests contained in that apk. bit CtsProtoTestCases:.ProtoOutputStreamBoolTest bit CtsProtoTestCases:android.util.proto.cts.ProtoOutputStreamBoolTest Builds and installs CtsProtoTestCases.apk, and runs all the tests in the ProtoOutputStreamBoolTest class. bit CtsProtoTestCases:.ProtoOutputStreamBoolTest\#testWrite Builds and installs CtsProtoTestCases.apk, and runs the testWrite test method on that class. bit CtsProtoTestCases:.ProtoOutputStreamBoolTest\#testWrite,.ProtoOutputStreamBoolTest\#testRepeated Builds and installs CtsProtoTestCases.apk, and runs the testWrite and testRepeated test methods on that class. Launching an Activity --------------------- To launch an activity, specify the activity class name after the module name. For example: bit StatusBarTest:NotificationBuilderTest bit StatusBarTest:.NotificationBuilderTest bit StatusBarTest:com.android.statusbartest.NotificationBuilderTest Builds and installs StatusBarTest.apk, launches the com.android.statusbartest/.NotificationBuilderTest activity. Change-Id: I9cff7a23852fa1a67369e7807f7ae9f6e45d6131 Test: none
2016-10-19 17:03:06 -07:00
#include <string>
using namespace android::am;
using namespace google::protobuf;
using namespace std;
class InstrumentationCallbacks {
public:
virtual void OnTestStatus(TestStatus& status) = 0;
virtual void OnSessionStatus(SessionStatus& status) = 0;
};
int run_adb(const char* first, ...);
string get_system_property(const string& name, int* err);
int run_instrumentation_test(const string& packageName, const string& runner,
const string& className, InstrumentationCallbacks* callbacks);
string get_bundle_string(const ResultsBundle& bundle, bool* found, ...);
int32_t get_bundle_int(const ResultsBundle& bundle, bool* found, ...);
float get_bundle_float(const ResultsBundle& bundle, bool* found, ...);
double get_bundle_double(const ResultsBundle& bundle, bool* found, ...);
int64_t get_bundle_long(const ResultsBundle& bundle, bool* found, ...);
#endif // ADB_H