Lately I was interviewed by Ryan Arsenault from Aberdeen Group on the blog TechProEssentials and by Srinivas Kadiyala for the Testing Circus magazine. Both interviews had a focus on mobile testing, my role as mobile tester, my current challenges at work, how I started my career in software testing and how I started my book about mobile testing. Maybe my interviews on mobile testing are interesting for you and will provide you with some new insights in my daily work life.
The following list is an excerpt from the questions I answered for the TechProEssentials:
Anyone who is involved in software testing and software test automation should know the test automation pyramid introduced by Mike Cohn (http://www.mountaingoatsoftware.com/).
This article contains excerpts from my book „Hands-On Mobile App Testing“ published with Pearson Education.
As you can see in the following image, the typical pyramid consists of three layers. At the bottom, there is the automated unit-testing layer, in the middle the automated integration testing layer and at the top there is the automated end-to-end testing layer (including the user interface tests). Each layer has a different size, indicating the number of tests that should be written within each stage. Manual testing is not part of the test pyramid, hence it is shown as a cloud for additional testing work.
But this pyramid is not applicable to mobile apps and mobile test automation. Mobile testing requires a totally different set of testing activities like movement, sensors, different devices and networks compared to other software like desktop or web applications. Lots of manual testing is required to be sure that a mobile app is working as expected in the different usage scenarios.
The 38th issue of the reading recommendation contains five interesting posts. This issue is mainly about learning, test automation and how to select the right mobile test devices for your team. There are posts with the topic “Audio Testing”, “Remote Experiential Learning”, “5 Things Your Boss Doesn’t Understand about Test Automation”, “Automated Verifications are Special, and Why This is Important” and an article about “How To Decide Which Devices to Buy for Mobile Testing” from Karen Johnson.
Enjoy reading the posts and send me posts that are worth reading and I will mention you and link to your social links or blog.
Google Testing Blog: Audio Testing – Automatic Gain Control
This time in the “People in Testing” series, I had the chance to interview Katrina Clokie. Katrina is a very passionate software testing expert in various testing fields. She is an active contributor to the software testing community and the editor of the Testing Trapeze magazine. If you have any kind of question to Katrina, you can contact her on twitter.
Daniel: What is currently your biggest challenge at work? Katrina: Since April I’ve been working in a test coaching role. My biggest challenge has been establishing good individual relationships with all the testers I work with. I spend a lot of time thinking about the number of interactions we have and what they are, as I know their primary responsibility is to their delivery teams and in some ways my work is a distraction from that. I am aiming to be approachable and helpful, without being overbearing and annoying. I hope I’m finding the right balance.
The 37th issue of the reading recommendation contains 6 posts. There is a great blog post from Rob Lambert about “Follow the work – bad news for Test Managers?”. Another posts are dealing with the topics “Test Early, to not fail often”, “Bugs are so yesterday”, “Measuring success in Testing”, “How do you surprise your team members during their next review?” and “The Tester Type Box – Why We Need To Break Out of It”.
Enjoy reading the posts and send me posts that are worth reading and I will mention you and link to your social links or blog.
Follow the work – bad news for Test Managers? – Rob Lambert Bad news for test managers
We use cookies to optimize our website and our service.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.