AI Testbot and AppCrawler¶
AppCrawler functionality provides an easy self-contained option to test mobile applications using an automated test procedure. Bitbar testing provides solution to run AppCrawler for both Android and iOS mobile applications.
AppCrawler tries to mimic human behavior in order to get reliable and valuable tests. AppCrawler navigates through the application under test and interacts with app elements.
Bitbar’s AI Testbot is based on artificial intelligence doing exploratory testing on your application.
- AI Testbot works only with Android versions 5.0 or newer
- you get video recording of each test run
- screenshots of the test execution
- test steps with descriptions and links to screenshots of what was done
Using AI Testbot¶
To create a new project using the AI Testbot, click on the Test Run Creator menu item and fill in the necessary values.
Select which environment you are testing
Select the AI Testbot for starting an AI based exploratory testing session
Choose you application file for testing. If your application file needs some additional files (like photos or something), you can include them here.
Select the devices you want your application to be run on. Note that AI AppCrawler runs on Android devices only (for now).
In the advanced options, you can add things like user credentials (to allow) login in to applications. Advanced options also allow you to limit the duration of the test run. Default value is 30 minutes and AI Testbot will typically use all available time.
There are two possible ways to use AppCrawler in Bitbar Testing.
- Either navigate through Projects and proceed to ‘New Test Run’ (green ‘+’) at top right corner. In the Test Run Creator select AppCrawler framework. These steps were described above.
- Second option is to click on AppCrawler menu item on main menu. Upload application file, devices and start execution. You have here the option of providing possible user credentials required by the application under test.
In both cases results of test execution with screenshots are presented in the test run view as for normal test executions.