Daniel, Author at Adventures in QA

[Reblog] How to convince your colleagues to write Automated Tests or why would you use Cucumber as an Automation Tool

May 7, 2018February 1, 2017 by Daniel

This post is a reblog from Serghei Moret, who is my colleague at XING. Serghei is an awesome test automation engineer developing really helpful solutions for our mobile app environment for iOS and Android. Lately he started to write on his own blog http://www.waysoftesting.com/. In his first post he is writing about “How to convince your colleagues to write Automated Tests or why would you use Cucumber as an Automation Tool”.

I really like the first post from Serghei and I want to help him spread the word about his blog and about his work and effort he is putting in mobile test automation. If you haven’t seen his blog, check it out.

Here is a short excerpt of the blog, the full article can be found here.

How to convince your colleagues to write automated tests? I think that a lot of people have asked this question and probably already found a dozen of correct and incorrect answers. In this article I’ll try to describe the way, how the automation framework was successfully implemented for several teams in different companies. Also I’ll speak about the reasons why you might use Cucumber in a wrong way. […]

Reading Recommendations # 80

May 7, 2018February 1, 2017 by Daniel

This is the 80 issue of my reading recommendations contains 6 very interesting blog posts. This time with “How to Monitor Mobile App Traffic With Sniffers”, “One Year Software Quality Page – Behind the scenes”, “Continuous Delivery for Mobile Apps using Fastlane”, “What You Need To Know When Planning Your Test Lab in 2017”, “Open Sourcing Bluepill: Run iOS Tests in Multiple Simulators” and “Introduction to Android Espresso Testing and Spoon”.

Enjoy reading the posts and send me new ones that are worth reading and I will mention you and link to your social links or blog.

	How to Monitor Mobile App Traffic With Sniffers
Source: https://stanfy.com/blog/monitor-mobile-app-traffic-with-sniffers/

33 Test Automation Leaders to Follow on Twitter

May 7, 2018January 13, 2017 by Daniel

What a nice start into the day, when you take a look at your smartphone and seeing a tweet like this Congratulation @dnlkntt to be one of 33 test automation leaders you need to follow on Twitter. https://t.co/rDZH1IcCKe What a start for 2017 — Dirk Meissner (@dirkmeissner) January 12, 2017 I somehow missed this list … Read more

Reading Recommendations # 79

May 7, 2018January 11, 2017 by Daniel

This is the 79 issue of my reading recommendations contains 6 very interesting blog posts and one video about mobile app security. Please watch this video! Thanks to all the bloggers out there writing the great content. This issue include the topics: “The Testing Pendulum: Finding balance in exploration”, “How to Efficiently Test Your Mobile App for Battery Drain?”, “Android Test Sharding on Genymotion Cloud Virtual Devices”, “Should test automation be left to developers?”, “Test Automation Leadership” and “More than just Ranking — The Different Stages of App Store Optimization”.

Enjoy reading the posts and send me new ones that are worth reading and I will mention you and link to your social links or blog.

	Katrina the Tester: The Testing Pendulum: Finding balance in exploration
Source: katrinatester.blogspot.de/2016/12/the-testing-pendulum-finding-balance-in.html

Mobile Bug Matrix

May 7, 2018January 9, 2017 by Daniel

Let’s start the year 2017 with some fresh and new mobile content. Today’s post is about the mobile bug matrix. Developing, testing and releasing mobile apps can be a challenging task. However, patching an app to fix bugs is not easy, too. How do you decide which bug is going to be fixed in an hotfix or not? Once a bug is online and installed on user’s mobile phones, there is a high likelihood that the bug will stay there for a longer time period, because not everyone is updating apps every day or has the auto update enabled.

There is no way in rolling back an app version once it has been uploaded. When I explain this problem to people who are not into mobile developing and testing I use the metaphor of a burned CD. Do you remember the good old times, when magazines added CDs with useful tools or CDs containing important drivers for your PC? Then you also remember how frustrating it was when the software on that CD had bugs or was completely broken. Once the CD is burned and delivered there is no way of rolling it back. The only way to solve the problem is to send a new CD ;). The same happens with native mobile apps. Once the app file was uploaded to an app store and users have installed the buggy version, you only have the chance to patch/ update this version with the next version.

Patching an app is time consuming, requires development and testing efforts and maybe even more alignments with other departments in the company. Furthermore, the planned development and testing in the current cycle will be slowed down or paused until the app is patched. And you should also keep in mind that some app stores have a review process in place, which may take some days until the patched app is available to the users.

One way to minimize the likelihood of doing a hotfix is an extended internal testing phase with your colleagues. Another way is to distribute the app to some beta testers to gain their feedback. But we all know that the real nasty bugs happen in the wild on the customer phones and companies need to handle them as soon as possible.