Get Automated Testing “Done”

How to fit automated testing into scrum, and keep testers in sync with other teams

One of the benefits of the approaches of agile projects is their friendliness towards testing. The testing activities, and the testers with it, are integrated into the teams, and testing and quality are redefined as team responsibilities. Automation nowadays is a must-have that needs to be addressed. Automation happens on multiple levels in a system, starting with unit tests. Here, we’ll focus on functional tests at the UI level.

For functional tests timely automation can be difficult, due to UI dependency. A team might be “done” with work items in a sprint, but the development and automation of functional tests might not have been finished yet. Having to do such automation later is unattractive; it places the testing and automation out of sync with the other activities in the team, making it harder to cooperate.

A first step to make testing manageable in short sprints is to use a domain language approach. This can help the whole team express and communicate tests quickly. We use keyword based “actions” that are easy to manage, use and implement, and is supported well with our product TestArchitect™. We also have a tool to translate actions to and from Behavior Driven Development (BDD) scenarios, another domain language approach.

Actions become the basis of the modular test design method called Action Based Testing (ABT), which organizes the tests into “test modules”. A main distinction is made in ABT between modules for “business tests” and for “interaction tests”. In a business test one would use business level actions like “rent car” or “check balance”, while in an interaction test the actions would be at a lower level, like “select menu item” or “check window exists”.

To get to automated testing “done” in agile sprints we ended up with a process that is shown in the picture. When the sprint starts the testers create the higher business level tests. These tests stay at the same level as the user stories and acceptance criteria. Further into the sprint, interaction tests are developed, when the user interfaces have become stable enough to make it worthwhile.

Also very early in the sprint interface mappings are made. We recommend that those are created without the use of an interface viewer or other spy tool. This encourages the team to define easy to maintain identifying properties for upcoming UI elements, like the “name” property in Java. This also encourages better collaboration between QA and Dev teams.

When the UI becomes available, the team is ready with:

  • Test Modules

⇒ Business Level Tests

⇒ Interaction Tests

  • Interface mappings
  • Actions – At this point actions are well thought out and finalized but not yet automated

LGMweb.201512.hans.01The automation focuses on the actions and only happens when the UIs become fairly final. (If you follow the approach, last-minute changes will be accommodated easily).

An additional way to relieve teams and keep automated testing in sync with development is something we like to call “Outsourcing 2.0”, which is part of our services offering as a company. Under this model, excess workload for test development and automation is handed over to a service group that can grow and shrink over time, and can service multiple agile teams. This way the attention of all team members can be focused on new functionalities.

Hans Buwalda
Hans Buwalda, CTO of LogiGear, is a pioneer of the Action Based and Soap Opera methodologies of testing and automation, and lead developer of TestArchitect, LogiGear’s keyword-based toolset for software test design, automation and management. He is co-author of Integrated Test Design and Automation, and a frequent speaker at test conferences.
Subu Baskaran
Subu Baskaran has over 11 years of experience in leading large, complex outsourcing projects both from onsite and offshore. He has a Bachelor’s degree in electronics and instrumentation engineering from Sastra University, India and an MBA from Cass Business School, London.

The Related Post

Distinguishing these terms from each other can be rather confusing. In an attempt to go back to the basics, Nadine Schaeffer explains in detail the benefits and the necessity of using realistic situations.
There is a multitude of Agile testing techniques that are quite sophisticated. The DAD process can help guide your process of tailoring decisions. Agile developers are said to be quality infected, and disciplined agilists strive to validate their work to the best of their ability. As a result they are finding ways to bring testing and ...
Agile Automation Michael Hackett – Senior Vice President – LogiGear Corporation Michael Hackett Michael is a co-founder of LogiGear Corporation, and has over two decades of experience in software engineering in banking, securities, healthcare and consumer electronics. Michael is a Certified Scrum Master and has co-authored two books on software testing. Testing Applications on the ...
LogiGear Magazine – July 2013 – Agile Testing
Take our quick survey on Testing in an Agile Development Team! Agile‘s impact on software development teams is huge. For test teams it can be even more pronounced — and good, especially if your existing projects have been problematic. There are many positive things about the move to be more Agile and responsive in software ...
Video narrated by MICHAEL HACKETT – Certified ScrumMaster This is Part Four of a Four Part Video on “New Roles for Traditional Testers in Agile Development” Michael shares his thoughts on “A Primer – New Roles for Traditional Testers in Agile”   LogiGear Corporation  LogiGear Corporation LogiGear Corporation provides global solutions for software testing, and ...
Janet Gregory draws from her own experience in helping agile teams address alternative ways to cope with roadblocks including projects without clear documentation, testers with limited domain knowledge and dealing with either black box or white box testing. For testing on projects without clear documentation, is exploratory the only method? I often make “tester errors” ...
SKILLS Agile teams need training! One of the missing links in the implementation of Agile development methods is the lack of training for teams. I noticed in our recent survey on Agile that only 47% of the respondents answered “Yes” that they had been trained in the Agile development process, with over half responding “No.” ...
Mark Levison has over twenty years experience in the IT industry, working as a developer, manager, technical lead, architect, and consultant. He discovered Agile in 2001 and is now a Certified Scrum Trainer and Agile Coach with Agile Pain Relief Consulting. Levison has introduced Scrum, Lean and other Agile methods to a number of organizations and coaches from ...
This is part 2 of a 2-part article series; part 1 was featured in the September 2020 issue of the LogiGear Magazine, and you can check it out here. Part 1 discussed the mindset required for Agile, as well as explored the various quadrants of the Agile Testing Quadrants model. Part 2 will delve into ...
Agile, in terms of software development, has incorrectly and for too long come to mean fast and “getting product out the door quicker.” But Agile is not about speed; it is about being flexible. I always begin my discussions on Agile development by getting a definition for the word Agile. Agile, in terms of software development, ...
Build the right test platform including infrastructure, virtual lab and process. Testing embedded software is both similar and dissimilar to application software testing. The first eye-catching thing is that embedded software is significantly less visible to the end user. User interfaces are limited; there may be a console-based text menu, a simple command line interface, ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe