In the beginning of 2019, I launched my mobile testing course in cooperation with Ministry of Testing. In case you haven’t heard about it, this short blog post will give you an idea what to expect from the course which is available on the Dojo from Ministry of Testing. The course name is: A Beginners Guide to Mobile Testing and was made for software testers who are new to mobile testing or want to switch from another industry field to mobile. The course teaches you the foundations and will cover all the basics of mobile testing and have even sprinkled in some quick, fun tasks throughout to help you develop new mobile related use cases to implement at your company.
This 9-part course will take you through the fundamentals of testing mobile applications and help you kick start your activities.
The Course Content
The course will cover:
- The different mobile data networks including the pros and cons.
- The technical specifications of mobile devices including the architecture as well as the built-in sensors which are used by millions of mobile apps.
- The different mobile app types and how they can affect your testing activities.
- The different business models behind apps to aid you in defining a solid mobile testing strategy.
- The different mobile app stores focusing on Apple and Google.
Beginners Guide to Mobile Testing is approximately 1 hour 30 minutes long and packed with around 3 hours worth of tasks for you to try out as well as extra resources to support you.
There are lots of open resources suggested in the individual Lesson Resources sections, as well as, links to The Club forum where you can share your progress and findings from the authentic testing tasks recommended throughout this course.
In addition, you can take a look at my book “Hands-On Mobile App Testing” which can be used to support your learnings while taking this course.
It would be advantageous if you have a basic understanding of software testing, but no mobile skills are required.
If you want to checkout the course, take a look at the introduction video here.
Imagine you and your team just a released a redesign of the login section of your software product. Shortly after the release you notice that the numbers of newly registered users dropped almost to zero. But why? Is it because the change of the register button to a register link? Or is it the new naming of the register element?
Maybe this kind of changes should have been tested before with an A/B test.
What is A/B Testing?
A/B testing in the context of digital software products gives a team the power to test and compare ideas like in a science experiment with real users. With the help of A/B testing new features or a redesign of an app can be tested against real customers, without letting them know. Almost everything can be tested with an A/B test. For example a color change of UI elements, a change in the navigation pattern, different texts or even whole app sections.
To start with A/B testing it’s recommended to define a strong hypothesis. Read more
About a month ago I wrote the following blog post about my mobile testing online course “A Beginners Guide to Mobile Testing” powered by Ministry of Testing. The complete course is now live at https://www.ministryoftesting.com/dojo/series/beginner-s-guide-to-mobile-testing-daniel-knott
In total the course is 1h 30mins long and will teach you the fundamentals of mobile testing. Please take a closer look at my last blog post to get the full picture what the course offers.
If you have any questions about the course let me know or take a look at the club, where you can discuss and share your learnings with other testers. Just follow this link to the club.
“It works on my machine,” is probably the most frequent comment a software tester will hear from a developer once a bug has been reported. An expected reply from a tester would be, “Then back up your system. We need to deliver it to our customers, because our product is only working on your system.” We all know that software isn’t bug free and never will be. However, software testers should use their testing skills and techniques to find as many issue as possible. Especially with mobile testing, software testers need a variety of techniques to identify issues in different environments and scenarios before the customer will find them.
In my latest blog post for Applause, I described two important mobile testing techniques to know. The first one is interrupt testing and how to test for interrupts especially for push notification as well as system interrupts. The second described technique is input testing. Most of the mobile tester I have talked about this topic, they always mention the input testing via the touchscreen. True this is the most important input mechanism, but there is more to cover. Furthermore, I have mentioned more techniques that are worth to know.
Read the complete article here:
Mobile devices and mobile apps are everywhere these days. Customers are using mobile devices and apps to play games, listen to music, and work from wherever they are. According to TechBeacon, more than half of mobile users will delete an app if it is crashing, freezing, or showing too many errors. As those who work in the field of mobile testing know, a mobile testing strategy is the key to success for a high-quality app. But defining a strong mobile testing strategy isn’t that easy. Mobile testers are facing many challenges to solve. There is device fragmentation, user mobility, high mobile user expectations, and device-specific hardware functions just to name of view.
And the challenges don’t stop there for mobile testers. More and more apps are now able to connect to wearable devices and other IoT devices.
Defining a Mobile Testing Strategy
With the rising complexity of mobile testing, a mobile development team needs to define a mobile testing strategy. With the help of a tailored test strategy, a mobile team can focus on the most important parts to deliver a great app to their users. It’s fairly easy to define a mobile testing strategy that will help downsize the amount of work needed during the development and testing phases. All you need to do is to gather user insights, define user scenarios, and specify your mobile testing approach. If you want to know how to define your own mobile testing strategy in three steps, read my lastest blog post at the Applause blog.
Read the complete article here: