I built this to mimic exploratory testing the best I could make it. Also because it was something I needed at the time and thought should exist. I do believe with the speed of development these days we need more tools like this to help us keep pace and not sacrifice quality. I also got tired or writing and refactoring tests for a constantly changing application so I automated the automation.
Probably not but that is the challenge of building somethign that does. Will it work for most apps? I think so. If it doesn't work for your app, help make it work by contributing a pull request. :)
I have only tested this on OSX and Linux environments but it will need some refactoring for Windows. Please help make it work by adding a pull request. :)
-
Crawl portrait "default": (-s (max runtime in seconds), -e (avd name or "em1 em2 em3"), -c (path to config file), --debug (print debug output))
aaet crawler -s 300 -e EM1 -c path/to/configFile.txt --debug --trace
- See all options:
aaet crawler --help
- Note: The Crawler automatically starts the emulator(s) if not already started.
-
Crawl landscape: (-s (max runtime in seconds), -e (avd name), -c (path to config file), --debug (print debug output), -o (orientation))
aaet crawler -s 300 -e EM1 -c wordpress.txt --debug -o landscape --trace
- See all options:
aaet crawler --help
- Note: Not all apps support landscape (e.g. app-debug.apk) so crawler will fallback to portrait
- Note: The Crawler automatically starts the emulator(s) if not already started.
-
Replay: (-c (path to config file), -s (max runtime in seconds or until last crawl steps are finished), --debug (print debug output))
aaet replay -c wordpress.txt -s 300 --debug --trace
- See all options:
aaet replay --help
- Select the past crawl you want to replay by the choice list.
- Replay crawler will then load last used config settings and command line arguments unless you override them.
- Note: The Crawler automatically starts the emulator or connects to device last used in selection.
-
Monkey: (-c (path to config file), -s (max runtime in seconds), --debug (print debug output), -e (avd name))
aaet monkey -c wordpress.txt -s 300 --debug -e EM1 --trace
- See all options:
aaet monkey --help
- Note: Not all apps are ideal for the monkey tester. Ideally, apps with lots of UI elements on each view work the best. If an app doesn't have many elements to interact with the monkey tester might appear to be doing nothing. This can be refactored of course and would love the help. Submit a PR!
- Note: The Crawler automatically starts the emulator(s) if not already started.
-
Crawl & Translate: (-s (max runtime in seconds), -e (avd name), -c (path to config file), --debug (print debug output), --reset (Appium App Reset default: false), -l (languages array "en fr de"), --translate (Google Translate String))
aaet crawler -s 120 -e EM1 -c wordpress.txt --debug --reset -l 'fr de' --translate --trace
- See all options:
aaet crawler --help
- Note: The Crawler automatically starts the emulator(s) if not already started.
- Note: Your app must support multiple languages for this to work.
- Note: The app will iterate through each language at the given time in seconds. e.g. -s 120 and -l "fr de", it will crawl and collect metadata in each language for 2 minutes each or until a crash occurs.
- Note: Do not put a comma between language code, just a space. e.g. "en de fr"
- Note: Need Google API Key. Go here to create dev account and get key. Set a GOOGLE_API_KEY environment variable or place key in config file.
-
Crawl & Applitools: (-s (max runtime in seconds), -e (avd name), -c (path to config file), --debug (print debug output), --reset (Appium App Reset default: false), --applitools (run applitools tests defined in config file))
aaet crawler -s 120 -e EM1 -c wordpress.txt --debug --reset --applitools --trace
- See all options:
aaet crawler --help
- Note: The Crawler automatically starts the emulator(s) if not already started.
- Note: The Crawler will upload to applitools based on the tests you define in the config TOML file. Make sure you add your API Key in the config file or have a APPLITOOLS_API_KEY environment variable set.
-
Crawl in Parallel: (-s (max runtime in seconds), -e (avd name or array "en fr de"), -c (path to config file), --debug (print debug output))
aaet crawler -s 120 -e "Nexus1 MyEmulator" -c wordpress.txt --debug --trace
aaet crawler -s 120 -u "UUID1 UUID2" -c wordpress.txt --debug --trace
- See all options:
aaet crawler --help
- Note: Do not put a comma between AVD's or UUID's, just a space. e.g. "AVD1 AVD2" or "UUID1 UUID2"
- Note: The Crawler automatically starts the emulator(s) if not already started.
- Note: You can force both orientations by passing
--bothOrientations true
This will only work when > 1 devices are running.
-
Crawl on the Cloud: (-s (max runtime in seconds), -c (path to config file), --debug (print debug output), --cloud (run on cloud service defined in config file))
aaet crawler -s 120 -c wordpress.txt --debug --cloud true --trace
- See all options:
aaet crawler --help
- Make sure you have the cloud settings and cloud caps configured in the config files.
- Note: The performance and logcat data is not captured on cloud runs, only screenshots. You can get this additional metadata from the cloud provider.
- Note: You can force both orientations by passing
--bothOrientations
This will only work when > 1 devices are configured in cloud caps file.
-
Note: The --config/-c can reference any file path. So if you have multple apps or versions you can configure your folder/file structure accordingly.
-
Debugging: Passing --debug will print out a lot of debugging output. One such debugging output are the instance variables set which are derived dynamically based on the config and command line arguments/options and then passed into each class. See here for example.
-
Definitely look at the --help menu for each option (crawler, replay, monkey). This will tell you all the available arguments you can use. Also, look at the code for further reference!