Firebase Test Lab for Android Robo Test

Just trying out this awesome test tool called robo on the firebase console, robo automatically explores your app on a wide array of devices to find defects and report any crashes that occur, Robo test doesnot require you to write tests, according to the documentation found on the site robo is described as thus

"Robo test is a test tool that is integrated with Firebase Test Lab for Android. Robo test analyzes the structure of your app's UI and then explores it methodically, automatically simulating user activities. Unlike the UI/Application Exerciser Monkey test, Robo test always simulates the same user activities in the same order when you use it to test an app on a specific device configuration with the same maximum depth and timeout settings. This lets you use Robo test to validate bug fixes and test for regressions in a way that isn't possible when testing with the UI/Application Exerciser Monkey test.
Robo test captures log files, saves a series of annotated screenshots, and then creates a video from those screenshots to show you the simulated user operations that it performed. These logs, screenshots, and videos can help you to determine the root cause if your app crashes, and can also help you to find issues with your app's UI."
Documentation link here

I Performed the test on KEB API Demos and source code application on Nexus 5, API Level 23 and was able to perform to derive the results illustrated bellow

Activity map:
It shows a very detailed activity map of the application workflow as illustrated below


This linked video contains the video recording of the test operation carried out by robo

Other test tool like robo I would personally also try out is the instrumention test which runs espresso, robotium or UIAutomator 2.0. We can finally say it was a really successful collaboration between google android studio and firebase.


Comments

Post a Comment

Popular posts from this blog

C# and Java Language History and Evolution

Image
This post will describe C# and Java language history and evolution  C#  Microsoft earlier implemented a modified version of Java, which was called J++ and a modified version of the Java Runtime Environment (JRE). In 1997, Sun Microsystems sued Microsoft, stating that Microsoft added new features in a manner that contravened Sun's standards and conventions for Java platform neutrality, and which features therefore violated the license agreement between Microsoft and Sun. The suit was settled in 2001: Microsoft agreed to pay Sun $20 million and gradually phase out the Microsoft JRE over seven years.  At time of the settlement Microsoft had already revealed the first version of C# which was based on .NET as opposed to the JRE. While developing C#, Anders Hejlsberg's team at Microsoft studied a number of existing languages including C++, Java, Modula-2, C and Smalltalk. The most notable differences was the C# support for delegates and events, metadata attributes/annotation
Read more

Differences between C# and Java cont'd -- Variables and operators

Image
Variables and Operators Data Types   Brief Similarity on variables and operators   Both C# and Java are Type-Safe Languages   Java and C# were designed to be type-safe. An illegal cast will be caught at compile time if it can be shown that the cast is illegal; or an exception will be thrown at runtime if the object cannot be cast to the new type. Type safety is therefore important because it not only forces a developer to write more correct code, but also helps a system become more secure from unscrupulous individuals. Unified type system  Both languages are statically typed with class-based object orientation. In Java the primitive types are special in that they are not object-oriented and they could not have been defined using the language itself. They also do not share a common ancestor with reference types. The Java reference types all derive from a common root type. C# has a unified type system in which all types (besides unsafe pointers[12]) ultimately derive from
Read more