Hot News - Magazine

Category: Automation Testing

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.

Leverage Automation to Make Mobile Testing Manageable

The most significant facet of mobile testing is understanding the mobile ecosystem.

By Hans Buwalda, Aldo Kurnia, Do Nguyen and Joe Luthy

Mobile applications are growing in use and sophistication along with the speed of the networks and the increasing power of the devices. To be sure, mobile application testing can be done with minimal automation, but a high level of test automation will help assure the best quality mobile applications.

The most significant facet of mobile testing is to understand what goes on in the mobile ecosystem to be able to design tests appropriately. This sounds obvious, but due to the complex nature of the mobile ecosystem, it isn’t. The multiplicity of devices and operating systems alone make for a very challenging testing matrix, but layered on that are a variety of hardware operational nuances. These include what are best described as interruption events; things like incoming call and message notification, change in network speed, and power warning notices.

Agile ALM and the Tools to Practice It

Armed with the right tool or set of tools, a development team can incorporate ALM into its Agile process and start reaping the benefits of Agile ALM.

By Eric Landes

As the software development industry matures, it is devising methods for ushering products from inception to completion—a process that has come to be known by the buzzword ALM (Application Lifecycle Management). Of course, development teams having been practicing ALM since software development began. The fancy acronym is the new thing!

For its part, Agile software development methods  support all aspects of ALM. In fact, Agile puts ALM practices at the forefront of software engineering. This article explains how ALM can help organizations in general and then discusses how Agile practices utilize ALM.

Tools for Integrated Test Platforms

Regardless of your current state of tools, building an effective Continuous Integration suite of significant automated regression tests is the key to moving to a higher level of confidence in today’s development world.

By Michael Hackett, SVP, LogiGear

In the evolution timeline of software development tools, new tools have recently proliferated. We have all been sold on collaboration, transparency and traceability – but that is not enough. Today, test tools are more often taking center stage. Integrated test platforms can push us deeper technically, help test faster, add more tools for our use and help us provide better, faster appraisals of the product under test.

In this article, I will discuss the introduction and integration of test tools into project wide tools, called ALM (application lifecycle management) and go into greater details about eXtreme Programming’s important Continuous Integration practice.

A Look Inside The Agile Toolbox: 10 Top ALM Tools

The pervasive use of Agile methodologies has changed the way that development teams work. With this change, new tools and vendors have entered the traditional application life-cycle arena.

From Software Consortium

A recent evaluation of this trend was published by Forrester Research, the “Agile Development Managements Tools Forrester Wave” report.

Key observations of the report:

Tools have changed to be task, management and report oriented. There has been a shift from traditional ALM tools, which focused on development artifacts and their relationship, to tools which bring change and task management to the top of the feature list, support the development team in their daily tasks, and enable work to be reported and measured.

Stephen Copp Interview on Integrated Test Platforms


Michael Hackett sat down with EA’s Stephen Copp to discuss the world of integrated test platforms.

Continuous Integration in .NET

Times have changed, the tools have improved, and with books like this available you have no reason to not give CI a go.

By Tad Anderson

I still remember the first time I was on a project that used NAnt and CruiseControl.NET. It was years ago and both were new tools with plenty of bugs. The project manager took one of the team’s architects and dedicated him to getting CI up and running. I didn’t work with him for another 9 months. It was a complete nightmare. Every morning was dedicated to finding out why the builds failed, fixing the issue, and then manually rerunning the builds until successful. Then it was off to show management the new build reports. It didn’t take long for them to not want to be hassled with the process. A year after it all began the code base was removed from the CI process and went back to manual builds.

Not a very good story to start the review of a book on CI that I highly recommend you read. Times have changed, the tools have improved, and with books like this available you have no reason to not give CI a go. You may have plenty of excuses, but no reasons. Luckily this book contains a nice summary of excuses commonly used and does a nice job of debunking them.