Black Friday is coming and I want to give you guys the chance to buy my book ‘Hands-On Mobile App Testing’ with a 50% discount. The discount is only valid from 28. November – 29. November. Use the following link and get the discount for my book.
Note: This link will be active on the 28. November.
Happy Black Friday!
A couple of posts ago, I blogged about “How to File Mobile Bugs“. One part of this post was a screen recorder video that can be attached to a bug report in order to provide more useful feedback to the developers. If you search the app stores for screen recorder apps you will find lots of them offering recording features. However, nearly all apps require a rooted device in order to use the screen recording function but using a rooted device for mobile testing is not recommended.
One of the first companies who provide a mobile screen recorder that requires NO device rooting is ilos. ilos is providing an Android and iOS app. However, only the Android app can be used to record the current screen to capture bugs in your app. The iOS app is only able to get access to already taken videos from your account. As soon as Apple provide such a feature in iOS ilos will also offer the screen recording feature for the iOS version.
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
And since today I am also part of this great series and it’s an honor for me.
Find my interview here.
Thanks to Ryan Arsenault from uTest to make this happen.
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. Continue reading
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.