Mobile Archives - Page 2 of 25

My Interviews on Mobile Testing

May 7, 2018November 2, 2015 by Daniel

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:

People in Testing with Viktor Johansson

May 7, 2018October 26, 2015 by Daniel

This time in the “People in Testing” series, I had the chance to interview Viktor Johansson. Viktor is currently working in New York City for a tech startup called Axial. Viktor is very passionate about mobile testing and likes to build devices labs with lego. If you have any kind of question to Viktor, you can contact via twitter.

Daniel: What is currently your biggest challenge at work?

Viktor: To keep up with our several, weekly releases. As an embedded tester in an agile team, there is a lot to test. New features are constantly being built. I need, together with the team, prioritize my testing and try to identify risk areas quickly. I am a strong believer in dogfooding. Everybody in an organization can test and bring value to a product. I have received good support from different stakeholders across the organization. Building those relationships, bridging channels of communication has been invaluable. It has not only helped increase the quality of our product, but has also given me a greater understanding of the business in order to be a better tester. Communication with the end users has also been essential.

Mobile Test Pyramid

May 7, 2018October 19, 2015 by Daniel

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.

Android M Testing with Doze and App Standby

May 7, 2018October 7, 2015 by Daniel

You probably all know that Google has started with the rollout of Android M (Marshmallow). Android app developers and testers must know the new features that are coming with the latest version of Android M. Next to the brand new permission system, Android M also introduces Doze and App standby to save battery.

If a user leaves a device unplugged and stationary for a period of time, with the screen off, the device enters Doze mode. In Doze mode, the system attempts to conserve battery by restricting apps’ access to network and CPU-intensive services. It also prevents apps from accessing the network and defers their jobs, syncs, and standard alarms.
Periodically, the system exits Doze for a brief time to let apps complete their deferred activities. During this maintenance window, the system runs all pending syncs, jobs, and alarms, and lets apps access the network. (Source: Google documentation)

In order to be sure that your app is able to handle Doze and app Standby, Google provided some documentation on that. Here are the steps to make sure your app handles Doze (instructions copied from the documentation):

Testing your app with Doze

You can test Doze mode by following these steps:

Reading Recommendations # 37

May 7, 2018October 7, 2015 by Daniel

Reading Recommendations - Adventures in QA

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
Source: thesocialtester.co.uk/follow-the-work-bad-news-for-test-managers/