Firebase
Products
Use Cases
Pricing
Docs
Support
Home
Products
Use Cases
Pricing
Docs
Support
The Firebase Blog
Customize your Firebase Test Lab Robo tests
26 de enero de 2017
Doug Stevenson
Developer Advocate
The
Firebase Test Lab
team is kicking off 2017 with some new features that make it easier for you to customize the testing of your Android apps. The following two enhancements are designed to save you time and money, so you can get the most out of Test Lab for your daily testing routine.
Sparse Device Matrix Selection
Previously, when selecting the combination of device and API levels, you were obliged to run against every possible valid combination of selected device and API level. For example, to run a test on a Nexus 5 and Nexus 7 on both API levels 19 and 21, the device selection matrix used to look like this:
The above selection would have scheduled the test on a matrix with a total of
four
combinations of device and API level. But what if I want to test against only
two
configurations: a Nexus 5 with API level 21, and a Nexus 7 with API level 19? With the old UI, that was not possible. However, with the new UI, you can easily get this behavior:
The above selection will only schedule the two selected combinations of device and API level. You are no longer obliged to test on
every
possible combination of selected device and API. With this new UI, you can now be much more specific about the configurations you want. This makes it faster and less expensive to retry tests on only those configurations where your app previously encountered errors.
Saved Matrix Templates
If you use Test Lab frequently and are tired of entering the same device matrix information repeatedly, you can now save a matrix configuration as a template, and refer to that template when running a test. There is a new templates tab available on the Test Lab feature home screen:
Here, you can create and manage your device matrix templates. Then, when you go to run a test, you can select from a list of your templates to apply to the test:
Custom Text Input for Robo Test
If you're already using Firebase Test Lab for Android to run its automated
Robo test
, you've probably already gotten a lot of mileage out of its ability to intelligently crawl your app running on our devices. But for some of you, Robo wasn't a very useful option, because it was unable to bypass a custom login screen, or enter some specific text at the right place.
Now, you can configure a Robo test to use specific strings at key locations in your app. Here's an example of the Firebase console UI that specifies both a credential for a custom login form, and a search term to be used in a search box:
This UI is available as an "advanced option" when running a test.
This configuration is telling the Robo test to type the string "test_lab_user" into every EditText widget with the Android resource ID named "tv_username". It will do similarly for the tv_password and tv_search EditText widgets. This type of customization will make it easier for Robo log into your app and perform a search where those named widgets are observed. You can have text prepared for any EditText in your app that has a resource ID, as long as you're able to provide its name. However, this does not work for WebView elements.
Keep thinking about app quality!
The Firebase team wants your app to be successful, and a great way to make that happen is by using features provided by Firebase.
So make 2017 a year of high quality for your app!
About
Firebase gives you the tools and infrastructure to build better apps and grow successful businesses.
Learn more
Popular Posts
Introducing Cloud Firestore: Our New Document Database for Apps
Best Practices: Arrays in Firebase
The beginners guide to React Native and Firebase
Firebase expands to become a unified app platform
Email Verification in Firebase Auth
Archive
►
2022
(5)
►
marzo
(2)
►
febrero
(2)
►
enero
(1)
►
2021
(41)
►
noviembre
(3)
►
octubre
(4)
►
septiembre
(4)
►
agosto
(7)
►
julio
(6)
►
junio
(4)
►
mayo
(3)
►
abril
(2)
►
marzo
(2)
►
febrero
(3)
►
enero
(3)
►
2020
(39)
►
diciembre
(1)
►
noviembre
(4)
►
octubre
(8)
►
septiembre
(4)
►
agosto
(6)
►
julio
(3)
►
junio
(4)
►
mayo
(2)
►
marzo
(3)
►
febrero
(1)
►
enero
(3)
►
2019
(31)
►
diciembre
(1)
►
noviembre
(4)
►
septiembre
(4)
►
agosto
(2)
►
julio
(3)
►
junio
(1)
►
mayo
(1)
►
abril
(4)
►
marzo
(7)
►
febrero
(2)
►
enero
(2)
►
2018
(55)
►
diciembre
(3)
►
noviembre
(8)
►
octubre
(1)
►
septiembre
(6)
►
agosto
(9)
►
julio
(1)
►
junio
(5)
►
mayo
(5)
►
abril
(4)
►
marzo
(7)
►
febrero
(2)
►
enero
(4)
▼
2017
(86)
►
diciembre
(10)
►
noviembre
(6)
►
octubre
(5)
►
septiembre
(6)
►
agosto
(9)
►
julio
(6)
►
junio
(7)
►
mayo
(8)
►
abril
(5)
►
marzo
(10)
►
febrero
(9)
▼
enero
(5)
Debugging Firebase Cloud Messaging on iOS
Customize your Firebase Test Lab Robo tests
Firebase Remote Config loading strategies
Welcoming Fabric to Google
Some Tips for Boosting your App's Quality in 2017
►
2016
(66)
►
diciembre
(6)
►
noviembre
(11)
►
octubre
(9)
►
septiembre
(9)
►
agosto
(6)
►
julio
(6)
►
junio
(7)
►
mayo
(3)
►
abril
(1)
►
marzo
(1)
►
febrero
(4)
►
enero
(3)
►
2015
(24)
►
diciembre
(2)
►
noviembre
(1)
►
octubre
(4)
►
septiembre
(1)
►
agosto
(2)
►
julio
(2)
►
mayo
(4)
►
abril
(1)
►
marzo
(5)
►
febrero
(1)
►
enero
(1)
►
2014
(29)
►
diciembre
(3)
►
noviembre
(3)
►
octubre
(3)
►
septiembre
(1)
►
agosto
(2)
►
julio
(2)
►
junio
(1)
►
mayo
(4)
►
abril
(4)
►
marzo
(2)
►
febrero
(1)
►
enero
(3)
►
2013
(28)
►
diciembre
(3)
►
noviembre
(2)
►
octubre
(2)
►
septiembre
(1)
►
agosto
(2)
►
julio
(2)
►
junio
(3)
►
mayo
(1)
►
abril
(3)
►
marzo
(6)
►
febrero
(2)
►
enero
(1)
►
2012
(8)
►
diciembre
(2)
►
octubre
(1)
►
septiembre
(1)
►
julio
(1)
►
junio
(1)
►
abril
(2)
Recent Posts
