Agile Testing

by Stan Taylor

Category Archives: Test Automation

The evolution of cucumber UI test steps

by Stan on 2016/03/16, one comment

I’m currently the framework/lead developer of a UI testing framework using Selenium WebDriver and Cucumber (written in Javascript using the bindings).  In an ideal world, cucumber test steps have no reference to anything beyond what is visible to the user in the user interface: And I enter Password1 in the Password field And I click […]

Automating android cordova/phonegap applications with appium

by Stan on 2015/10/16, no comments

I am just putting this out there for others to find, because I had such a difficult time locating this crucial tidbit of information: if you select the Android WebView context in your hybrid mobile application, you can run your DOM-based Selenium tests against it using appium. I am tasked with creating UI automation for an […]

Identifying form elements by the <label> tag contents

by Stan on 2015/10/16, one comment

In a previous post, I explained how I use the text associated with UI objects in my cucumber tests. My steps look something like this: Given I go to the login page And I enter “johndoe” in the field with id “username” And I enter “password1” in the field with id “password” If the application […]

Writing Selenium test steps for cucumber tests

by Stan on 2015/10/03, 2 comments

In my current job, I’m responsible for developing a framework for performing UI testing of web and mobile applications with Selenium WebDriver/Appium, using the bindings for node.js Javascript. We have adopted cucumber as the format for defining the tests. Conventional wisdom regarding UI testing holds that you should always strive to select UI objects by the […]

Underestimating myself

by Stan on 2015/07/23, no comments

I’m a self-taught programmer; I’ve never done it full-time. Most of the QA jobs that I have had over the years have included some amount of scripting and/or automated testing work, but it’s always been done alongside other QA tasks. When I was job hunting last year, I concluded that if I really wanted to remain competitive […]

Often overlooked test automation challenges

by Stan on 2012/08/08, no comments

The company I work for develops several different products as part of a unified offering. These products need to work with each other and with products from other companies. Each product development team has its own manual QA and automation team, and we have a solutions testing team that ensures interoperability between our products and […]

“Just Good Enough”

by Stan on 2011/08/10, one comment

One of the automation engineers on our team is extremely thorough. When she does code reviews, she sends back lengthy emails, and she provides a lot of good information regarding coding practices. Her devotion to detail is a real asset to the team. However, she is getting burned out on code reviews and sometimes I […]

The value of automated UI testing

by Stan on 2009/08/03, one comment

During my recent job hunt, test automation came up in practically every interview, typically some broad question like, ‘So, how would you go about implementing test automation?” My standard answer is that you generally get the best bang for your buck the farther deeper in your code you test. As an example, I contrast maintenance […]

Software testing categorization

by Stan on 2009/07/15, no comments

Over at the Google Testing Blog, Miško Hevery has a short post on what constitutes small, medium and large testing. To summarize his post: Small: make sure each class works properly in isolation Medium: make sure the classes work together Large: end-to-end scenario testing to make sure that everything is wired together properly

Types of automated testing

by Stan on 2009/05/20, no comments

Over at his I. M. Testy blog, BJ Rollison offers succinct definitions of five approaches to automated testing: record and playback automation, keyword or action-word driven automation, scripted automation, procedural automation, and model based automation. It’s a good quick reference.