Reading Recommendations # 28

Reading Recommendations - Adventures in QA

The 28th issue of my software testing reading recommendations contains 6 blog posts. The first blog post is from Google announcing the new option for Android beta testing. I also wrote a post about this topic on Monday. Then there is a book review from Janet Gregory of the book “Fifty Quick Ideas to Improve Your Tests”. There are two posts written live from #TestRetreat about “How Can We Interview Testers Better?” and “Bringing Energy Back to Testing”. Then there are two great posts about “On being and becoming a speaker at conferences” and “How I Survived My First Year of Testing”.

Enjoy reading the posts during the nice summer days and feel free to send me any kind of reading recommendations if you have a great article to share.

Iterate faster on Google Play with improved beta testing | Android Developers Blog

Read more

Beta Testing for Android Apps

Beta Testing for Android Apps - Adventures in QA

Since a couple of years Google is offering beta testing for Android apps. With this feature companies or developers have the chance to release Android beta apps to mobile testers via the Google Play Store. This feature is integrated into the Google Play Developer Console and is very easy to use. All you have to do is to upload your beta apk file to the developer console and to publish the app to the known beta testers.
Mobile development teams are able to create their own beta testing community with the help of G+ communities or Google groups. Since last week, Google is offering two more options to improve the beta testing even further. With this update, mobile tester and developer are able to create a public beta tester group without the need of the G+ community or a Google group. All you have to do, is to enable this option in the developer console and to send the beta testing URL to possible testers.

The URL has the scheme: Whenever a tester is clicking this link he or she can become a beta tester of the app. After clicking the link, the beta tester will get an update of the app in the Google Play Store and is able to download the beta version.

Read more

Reading Recommendations # 27

Reading Recommendations - Adventures in QA

The 27th issue of my software testing reading recommendations contains 7 blog posts. There are posts about the pyramid and the dog-bone revisited. The challenge in providing accessibility, habits for agile testing and a post about custom ViewMatchers in Espresso for Android test automation. Another post is about “Test Levels! Really?!”, “The Dos and dont’s of testing automation” and one post from Markus Gärtner is dealing with “Working in a distributed company”.

Enjoy reading the posts.

Seth Eliot’s Blog » Blog Archive » The pyramid and the dog-bone revisited

Read more

[Infographic] QA Mistakes and how they were solved

Udemy Infographic - Adventures in QA-header

The company Udemy, send me the following very interesting infographic about major QA fails and solutions from the last 25 years. It is pretty interesting to see what kind of bugs occur and how they were solved. The infographic contains bugs from companies such as AT&T, Pentium, US Navy, NASA, Airbus, Lookheed and many more. … Read more

People in Testing Interview with Eddy Bruin

Eddy Bruin - Adventures in QAThis time in the “People in Testing” series, I had the chance to interview Eddy Bruin, who is an agile test coach in the Netherlands. Eddy is the co-founder of BUXIT, a community which goal it is to improve products through attention for User Experience.

Daniel: What is currently your biggest challenge at work?

Eddy: I’m currently an Agile coach in a big firm. It’s all pretty new to them and most of the developers are working on the other end of the world. My biggest challenge is coaching these people with the limited facilities we have. Only talking to a phone is hardly enough to create a team spirit and to communicate effectively. The biggest test challenge in this aspect is letting the team realize there are more ways to test besides exhaustive checking while treating the application as a complete black box. Let’s say that every time we change the color of the car the testers want to test the gearbox again.

Read more