Hot News - Magazine

Category: Automation Testing

Test Automation Tool Shopping Guide

A short-list of selection criteria and popular automation tools.

By LogiGear Staff

There are a lot of test automation tools available in the market, from heavy-duty enterprise level tools to quick and dirty playback-and-record tools for browser testing. For anyone just starting their research we’ve put together a short list of requirements and tools to consider.

Testing Tools: It ain’t Only About Automation!

Test execution and utility tools that can make your job easier

By Michael Hackett, LogiGear

My first exposure to the necessity for testers to have an array of tools was from the groundbreaking article “Scripts on my Toolbelt” by Danny Faught. Danny laid out the ideal approach to any testing job, and it got me thinking “How can I leverage tools to help me?” I needed a group of tools to get my tasks done. I needed to have a full toolbelt! It makes a lot of sense. A carpenter can’t do everything with a saw, he needs dozens of tools to get the job done.

Avoid Epic Fail. Get Professional Help

Bringing in experts can set you up for automation success.

By Michael Hackett and Joe Luthy, LogiGear Corporation

Test automation isn’t easy when your testing gets beyond a few hundred test cases. Lots of brilliant testers and large organizations have, and continue to struggle with test automation, and not for lack of effort. Everyone understands the value of test automation, but few testing organizations realize its full potential.

Letter from the Editor – April 2014

Testing tools – very important, very often overlooked, and very often where mistakes are made.

First, the most common mistake people make about tools is thinking tools are only about test automation! False. Automation tools are merely one type testing tool. We will try to balance this issue between test automation tools and other test tools.

I heard a story about test automation, very recently in fact, of a company that paid a large licensing fee to a major tool vendor, and invested  a lot of training and time to develop a phase 1 automation project. The intent was to scale up the initial phase into a large product suite automated regression tool. After just 6 months the project was dropped due to high test maintenance costs, over-idealized expectations and time demands. A whole lot of money, time, and tester goodwill went down the drain! I have heard too, too many of these stories with test tools, and specifically automation tools.

Test Automation Games

By Jonathan Kohl

Two dominant manual testing approaches to the software testing game are scripted and exploratory testing. In the test automation space, we have other approaches. I look at three main contexts for test automation:

1. Code context – e.g. unit testing.

2. System context – e.g. protocol or message level testing.

3. Social context – e.g. GUI testing.

In each context, the automation approach, tools and styles differ. (Note: I first introduced this idea publicly in my keynote “Test Automation: Why Context Matters” at the Alberta Workshop on Software Testing, May 2005) 

Testing Netflix on Android

By Amol Kher, Wello Inc.

When Netflix decided to enter the Android ecosystem, we faced a daunting set of challenges:

1. We wanted to release rapidly (every 6-8 weeks).

2. There were hundreds of Android devices of different

shapes, versions, capacities, and specifications which need to playback audio and video.

3. We wanted to keep the team small and happy.

Of course, the seasoned tester in you has to admit that these are the sort of problems you like to wake up to every day and solve. Doing it with a group of fellow software engineers who are passionate about quality is what made overcoming those challenges even more fun. 

Test Automation is Not Automatic

By Randall Rice, Rice Consulting

Recently while teaching a workshop on Testing Dirty Systems, I uttered this “Randyism” off the top of my head, “Test automation is not automatic.” I realized immediately that I had just concisely stated the problem in making test automation a reality in many organizations.

Most testers know that test automation is not automatic. (Wouldn’t it be great?) However, management many times does not know or accept that reality.

There are some test tools, such as unit test tools, that are practically automatically applied. My remarks in this article are aimed at the capture/playback and scripting tools for test automation.

Automation Frameworks and How to Build a Simple One

By Karthik KK

An automation framework is a way to organize your code in meaningful manner so that any person who is working with you can understand what each file contains.

Automation frameworks differ based on how you organize your code – it can be organized based on your data, so that any person who wants to use or edit data files such as an excel sheet can do so easily. These types of frameworks are known as data-driven frameworks.

Keyword-driven frameworks are those which can be written with keyword functions such as: Login, ClickButton, SearchList etc. These enable automation engineers to work within the framework easily, without ambiguity in function or code.

The combination of the above is called a Hybrid framework. There are some other frameworks which are named according to their usage such as Modular frameworks, structural frameworks etc.

Test Automation Interfaces for Mobile Apps

What you need to know in order to have effective and reliable test automation for your mobile apps

By Julian Harty

I realized that test automation interfaces are pivotal to effective and efficient test automation, yet very few people trying to test their mobile apps seemed to know how their automated tests connected with the apps they wanted to test. Even if you use commercial products that claim to remove the need to write test automation code you may find the information enlightening, at least to understand the mechanics and some of the limitations of how these products ‘work’.

This article provides an overview of the topic of test automation interfaces, starting from stuff we need to know, then things we need to learn & understand, then the concluding section covers factors worth considering in order to have effective and reliable test automation for your mobile apps. I have included various additional topics that don’t fit into the know/understand/consider sections.

Mobile Test Automation – Best Practices

Test engineers face a rapidly changing mobile application landscape, making mobile test automation a necessity.

By Abhijit Phatak, mAutomate

We know that mobile apps are becoming increasingly complex along with the technological advances in  tablets and smartphones.

Test engineers have to address multiple challenges while testing data-centric mobile apps, including the growing diversity of device features, platforms, and technologies.

Fortunately, mobile testing automation can help take care of the majority of  the functional and non-functional intricacies of app behavior.

Test automation can be considered a mix of Environmental, Behavioral, Performance and Complete Ecosystem testing.