Every software development team or company will come to the point where a test automation tool is needed to downsize the effort of regression testing. The test automation tool can help the tester and the whole team to concentrate on other important testing tasks that a tool can’t handle.
Selecting a tool sounds easy at the first look. Many people will pick the most used tool on the market or the one that supports the programming language of the product. Sure, these are two important factors when selecting a tool, but there is much more to consider when searching and selecting the tool.
Different Types of Test Automation Tools
But where to start? When deciding for a tool, it’s important to know the different types of test automation tools and how the tools are working on a high-level view. Basically, there are five different types of test automation tools on the market:
Image recognition: Tools in this category are taking screenshots of the UI elements in the product. The screenshots will be added to the automation scripts. With the help of the screenshots the application under test will be automated and verified.
Coordinate based recognition: With the help of x/y coordinates, tools in this category are interacting with the application under test to automate and verify the application.
OCR/ text recognition: Optical Character Recognition (OCR) or text recognition tools are able to identify elements based on their given text. The tools use the visible texts to drive the automation and to verify the application.
Native object recognition: Tools that use the native object recognition detect the control or UI elements on their given element tree. In most cases this tree is built by CSS, XPATH or XML to identify, automate and verify the elements.
Capture & Replay: Tools in this category offer a convenient and easy way to record the automated scripts. Every interaction on the screen being it scrolling, tabbing/ clicking or typing will be recorded and translated into automation steps for the tools. The recorded scripts can be used to replay the activities and to verify the application under test.
It is time again for my reading recommendations. I hope you have already missed them. In the last 3 weeks I was on vacation to recharge my batteries and to think about new blog posts. During that time I was mainly offline and the time was just great! You should try it as well :).
However, now it is time again for some really great software testing content that you should read. The 42nd edition of the reading recommendations contains 6 blog posts with different topics. There is a post about flaky tests, a post from Stephen Janaway is providing a cheat sheet for mobile testing which is really great. Katharina Clokie provided again another great pathway this time with the topic “Testing for Non-Testers”. Other posts are “Bug Automation”, “Why Social Skills Are Trumping Cognitive Skills” and “The 10 Do’s, and 500* Don’ts of Automated Acceptance Testing”.
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.
Your tests aren’t flaky | WatirMelonThis is a talk I delivered at the Google Test Automation Conference (GTAC) on Tuesday 10th November at Google in Cambridge, Massachusetts. I am going to be using the F-word a lot in this talk. Like a lot. I apologize in advance if I offend. You know the F-Word don’t you? Also known as the…
As a mobile testing leader you will be responsible for developing the market strategy for the mobile testing department at QualityMinds.
We are convinced that mobile computing will become a fixture in every software project in the future. That is why we are looking for a new QualityMind, someone passionate about all things mobile-related: devices, apps and the possibilities behind them. In order to handle this multifaceted task, you need to have technical experience and enthusiasm, keep in touch with the newest developments and ideas in the field as well as be prepared to lead your own team.
helping define and create a new business model
preparing market strategy
customer acquisition in cooperation with our sales management
the most important task: built a team of “mobile freaks”
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: Read more
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. Read more