Releasing an app is not an easy process. Once an app is rolled out to the customers there is no way of rolling it back like on web platforms. Imagine a native mobile app as a good old burned CD that was shipped as a part of a magazine or hardware parts containing the drivers. Once it’s burned and shipped you can’t fix it. The same applies for native mobile apps. Therefore, a solid mobile app launch strategy is key to success for every company.
Before an app can be released it’s important to know all the technical information about the software development cycle. How many developers, testers (internal or external) are involved in the app development. How often will the app be released, what is the sprint cadence. Is there an internal or external beta testing community in place that can be used before rolling out the app to the customers? As a foundation for the release strategy this kind of information is important.
When the development cycle comes to an end it’s important to gather all the required release information from the product team. Every release should have meaningful release notes informing the user about the new release. The store descriptions must be updated as well images.
Before building the release candidate of the new app version, every team must execute the automated checks and see if they pass. Additionally, it’s recommended to perform a last exploratory testing session to see if all the critical parts and the new features are working as expected.
The last thing before going live is to check the release checklist. A checklist for a release must be in place to double check that nothing was missed out. Find out in my last blog post for applause what the release checklist is all about and what needs to be done in the post release monitoring.
Read the complete article here:
LINK APPLAUSE BLOG
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 last blog post at the Applause blog.
Read the complete article here:
An average mobile user is checking his or her phone every six minutes and has around 40 apps installed. Checking the phone every six minutes means that an average user is looking more than 200 times a day at the mobile phone. If you have ever checked the mobile reviews in the biggest mobile app stores you can see that mobile users have a very high expectation. If an app needs more than two seconds to start, a mobile user is very likely to uninstall the app and leave a bad review and rating. The same goes for crashes during the startup, bad overall performance or a bad user experience.
The mobile user experience is key of success for a mobile app. A mobile app must have a really good design where all the logos, images and texts are optimized for a small screen. It’s important that an app is following the platform specific guidelines.
Furthermore, it’s important that an app is not consuming too much battery as well as mobile data.
If an app relies on images, it’s important to minimize the size to have faster loading times. An app should have a minimum amount of taps to solve a user problem. For example, provide the number keyboard for number input fields to avoid one unnecessary tap for a user.
To meet the high mobile user expectations, mobile testing is a crucial part in the development lifecycle and must performed by testing experts.
In one of my latest blog post, that I wrote for Applause, I outlined the importance of mobile user experience when it comes to the high mobile user expectation.
Read the complete article here:
Maybe you have seen it already in my page navigation. Since this week, I offer a mobile testing skype coaching. I had this idea in my mind for a while and during my vacation I thought, why not. Give it a try.
Since 2010, I am working in the field of mobile testing. During this time, I gained lots of knowledge in mobile testing technique, mobile test automation, the whole app development lifecycle and how to release an app in different ways. At the end of 2013, I decided to write a book about mobile testing to share my knowledge. The book Hands-On Mobile App Testing was published in 2015. One year later the German edition Mobile App Testing was published, too.
Many people from all over the world approached me and gave me very positive feedback about the book. With my mobile testing skype coaching, I want to take the next step and to provide a direct 1:1 communication with companies or independent developers.
Mobile Testing Skype Coaching
The coaching is based up on individual challenges and needs. Therefore, the target group for this coaching is broad, from:
- Independent mobile developers with no mobile testing skills.
- Startups without any software testers.
- Companies who want to establish a mobile testing department.
- People who want to become a mobile tester.
- Mobile tester who want to get new testing ideas.
If you are currently lost in mobile testing and need my help, take a look at the details and get in touch with me.
I think it was about time. Time to write my own mobile testing mnemonic. I am working in the field of mobile testing almost 9 years and during this time, I tested many different apps with different use cases. I learnt a lot during this time and I shared my learnings with the world in my own book about mobile testing. Reading books is awesome, but the content from more than 300 pages is hard to keep in mind and to remember. Therefore, I thought it is time to create a mnemonic with the name “Mobile App Testing”.
In the beginning I thought it will be hard to find for the right content for each letter. But in the end it was fairly easy. My mnemonic is covering areas like mobile devices, orientation, mobile browsers, interrupts, performance, automation and many many more.
Please take your time and read the complete mnemonic in the Ministry of Testing dojo here.