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.
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.
Maybe you have seen it already on YouTube or twitter. Currently, I am recording an online testing course for Ministry of Testing about mobile testing. In this course I will teach you the fundamentals of mobile testing.
The course will include the following topics:
- History of mobile devices
- Hardware of mobile devices
- Mobile Device Fragmentation
- Mobile Data Networks
- Comparison between iOS and Android
- The different mobile app types
- Mobile app stores
- Mobile app business models
In each lesson I will talk about the testing impact and will provide usefule resource for you to kickstart your mobile testing activities.
Take a look at the course teaser.
The complete course will be online soon in the dojo at https://www.ministryoftesting.com/dojo/courses.
I am looking forward to your feedback and the discussions about mobile testing in the club as well on the ministry of testing community page.
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 lastest 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
This is a reblog, of my blogpost iOS Calabash Launcher for MacOS from tech.xing.com. I want to share the post with you, because it might be of interest.
Today, the XING mobile releases team want to give something back to the Open Source community. At XING, using Open Source software in our projects is natural. For our mobile apps (iOS and Android) we use Calabash to write end-to-end automated checks, to verify that the user flows are covered before going live. For those people who worked with Calabash for iOS and Android they know that it’s sometimes really hard to define screens, to detect the ID as well as the text behind an element. The default Calabash installation provides a console based element inspector, which makes it not easy to work with. Furthermore, the default installation from Calabash doesn’t offer any visual device detection, test execution, element inspection or setup possibilities.
But this will change today! We are proud to Open Source our Calabash Launcher. Read more