A couple of weeks ago the uTest blog started a new series called Authors in Testing. In this series several testing experts have been interviewed about certain testing topics and the book they wrote. There were interviews from
If you find a bug within a mobile app, you need to report it in order to get it fixed. Filing mobile bug reports requires some additional information that the developers need in order to reproduce and fix the bug.
But what is important when filing a mobile bug? What should a bug report look like?
Before I answer those two questions, I want to raise another one: “Why even send a bug report?”
Bug reports are very important for the product owner, product manager and the developers. Firstly, a bug report tells the developers and the product owner about issues they were not aware of. They also help to identify possible new features no one has thought of and, last but not least, they provide useful information about how a customer may use the software. All of this information can be used to improve your software. Read more
And here is the second day and video from the Google Test Automation Conference. At the second day there were again talks from Google, Facebook, American Express, Adobe or Comcast. This day was again just great, with great topics and great speakers. Check out the attached video and enjoy the various topics about test automation.
On 10/28/2014, the first day of the 2014 Google Test Automation Conference took place in Kirkland. For those who can’t attend the conference, Google provided a live stream and has now published the talks in a youtube video.
The video includes very interesting talks from various companies such as Google, Mozilla, Adobe, HP, Dropbox, Netflix or Facebook. The complete schedule can be found here.
All talks from the first day are included in this video.
Today, I want to share a video with you. The topic of the video is “Breaking the Matrix – Android Testing at Scale” and shows a talk from Google employees explaining how to scale your Android test automation using emulators.
Testing Android apps manually on emulators is not my first choice, however at some point it makes sense to use them as a part of your mobile test automation strategy to save time and money.
How is oour Android testing environment look like? Are you using emulators in your test environment?