-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathstep.yml
138 lines (124 loc) · 3.96 KB
/
step.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
title: |-
Run tests with ADB
summary: |
Run tests from the emulator command-line shell with Android Debug Bridge
description: |
Run tests from the emulator command-line shell with Android Debug Bridge.
When you run tests from the command-line with Android Debug Bridge (adb), you get more options for choosing the tests to run than with any other method. You can select individual test methods, filter tests according to their annotation, or specify testing options. Since the test run is controlled entirely from a command-line, you can customize your testing with shell scripts in various ways.
website: https://testify.dev
source_code_url: https://github.com/ndtp/bitrise-step-android-testify
support_url: https://github.com/ndtp/bitrise-step-android-testify/issues
host_os_tags:
- osx-10.10
- ubuntu-16.04
project_type_tags:
- android
type_tags:
- test
is_requires_admin_user: true
is_always_run: false
is_skippable: false
run_if: ""
toolkit:
bash:
entry_file: step.sh
inputs:
- adb_command: "$ADB_COMMAND"
opts:
title: "The command-line statement to run with adb"
summary: "The command-line statement to run with adb"
description: |
The command-line statement to run with adb
is_sensitive: false
is_expand: true
is_required: true
- module: "$MODULE"
opts:
title: "The gradle project module name"
summary: "The gradle project module name"
description: |
The gradle project module name. e.g. `:app`
is_sensitive: false
is_expand: true
is_required: true
- app_apk: "$APP_APK"
opts:
title: "The full path to the application apk under test"
summary: "The full path to the application apk under test"
description: |
The full path to the application apk under test. For library projects, this will be the test apk.
is_sensitive: false
is_expand: true
is_required: true
- app_package: "$APP_PACKAGE"
opts:
title: "The package name of the app"
summary: "The package name of the app"
description: |
The package name of the app. For example, `com.sample`
is_sensitive: false
is_expand: true
is_required: true
- test_apk: "$TEST_APK"
opts:
title: "The full path to the test runner .apk"
summary: "The file name of test runner .apk"
description: |
The file name of the test runner .apk
is_sensitive: false
is_expand: true
is_required: true
- test_package: "$TEST_PACKAGE"
opts:
title: "The package name of test runner .apk"
summary: "The package name of test runner .apk"
description: |
The package name of test runner .apk
is_sensitive: false
is_expand: true
is_required: true
- test_runner: "androidx.test.runner.AndroidJUnitRunner"
opts:
title: Test Runner
description: |-
The fully qualified class name for the Instrumentation test runner. e.g. `androidx.test.runner.AndroidJUnitRunner`
is_required: true
- device_density: "$DEVICE_DENSITY"
opts:
title: "DPI value to set on the emulator"
summary: "DPI value to set on the emulator"
description: |
DPI value to set on the emulator
is_sensitive: false
is_expand: true
is_required: false
- animations: false
opts:
title: Enable animations on the emulator
is_required: true
value_options:
- true
- false
- show_ime_with_hard_keyboard: false
opts:
title: Show the onscreen keyboard (IME)
is_required: true
value_options:
- true
- false
- show_passwords: false
opts:
title: Show password entry characters
is_required: true
value_options:
- true
- false
- verbose: false
opts:
title: Enable verbose log?
description: |-
You can enable the verbose log for easier debugging.
is_required: true
value_options:
- true
- false