Skip to content

Commit 67d61cf

Browse files
authored
Update README.md
1 parent 04269c1 commit 67d61cf

File tree

1 file changed

+40
-0
lines changed

1 file changed

+40
-0
lines changed

README.md

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,4 +75,44 @@ Kraken with the help of Calabash-Android will install an instrumentation along w
7575

7676
## Kraken Settings
7777

78+
Kraken uses kraken_mobile_settings.json to specify in what devices the tests should be run.
79+
80+
### Generate settings file
81+
82+
The following command will show you the available connected devices or emulators and let you choose which ones you want to use.
83+
84+
kraken-mobile setup
85+
86+
### Run tests with settings file
87+
88+
kraken-mobile run <apk> --configuration=<kraken_mobile_settings_path>
89+
7890
## Properties file
91+
92+
Kraken uses properties files to store sensitive data such as passwords or api keys that should be used in your test cases.
93+
94+
### Generate properties file
95+
96+
The properties files should be a manually created json file with the following structure.
97+
98+
{
99+
"@user1": {
100+
"PASSWORD": "test"
101+
},
102+
"@user2": {
103+
"PASSWORD": "test2"
104+
}
105+
}
106+
107+
### Use properties file in your test
108+
109+
You can use the specified properties using the following sintax.
110+
111+
@user1
112+
Scenario: As a kjkhdkjds
113+
Given I wait
114+
Then I see the text "<PASSWORD>"
115+
116+
### Run tests with settings file
117+
118+
kraken-mobile run <apk> --properties=<kraken_mobile_properties_path>

0 commit comments

Comments
 (0)