Monthly Archives: July 2013

Technical Debt: A Nightmare for Testers

By Michael Hackett

The sprint is almost over; the burndown chart has not budged. The test team sits around waiting. They hear about all kinds of issues, obstacles and impediments at the daily stand-up but there is no code to test. Closing in on the demo and sprint review… then at Wednesday’s standup: the heroes arrive and tell everyone,

“All the stories are done. Everything is in the new build. Test team – get to work! You have one day to test everything for this sprint, we will have an internal demo of everything tomorrow afternoon and a demo to the PO on Friday morning. Get busy!”


LogiGear Magazine – July 2013 – Agile Testing

LogiGear Magazine – July 2013 – Agile Testing

LogiGear Corporation

LogiGear Corporation provides global solutions for software testing, and offers public and corporate software-testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast and cost-effective results. Since 1994, LogiGear has worked with hundreds of companies from the Fortune 500 to early-stage startups, creating unique solutions to exactly meet their needs. With facilities in the US and Vietnam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

For more information, contact Joe Hughes + 01 650.572.1400


Letter From The Editor – July 2013

In our continuing effort to be the best source of information for keeping testers and test teams current, we have another issue to explore testing in Agile development. As Agile evolves, systemic problems arise and common rough situations become apparent. We want to provide solutions.

For anyone who has worked on Agile projects, especially if you have worked at more than one company or for a few clients, you know “testing in Agile” can be an adventure. Remember there are no “rules” or best practices for Agile testing. There are better practices. Every team and Scrum implementation is unique. This is still evolving.


Quantify the Impact of Agile App Development

By Larry Maccherone, Director of Analytics, Rally Software

Agile is here to stay. Once the radical alternative to Waterfall development methods, these legacy methodologies are being disrupted and replaced by Agile practices that improve time-to-market, reduce development costs, and produce higher quality software that better meets customer expectations. As the world demands more software, development teams – from scrappy startups to big corporations – are meeting the challenge with Agile.

But while Agile software development projects scale across the enterprise, management is still searching for the best way to gain deeper visibility into these projects. Large organizations cannot rely on the subjective anecdotes of those closest to the work; they require quantitative insight upon which to base business decisions.


Is Your Cloud Project Ready to be Agile?

By David Taber, CIO, SalesLogistix

In the decade since the Agile Manifesto, the movement has encouraged a number of best practices like test-driven development, user-centered design, iterative development, clean code, refactoring, continuous integration, and—arguably—cloud computing. I’m a card-carrying Agile zealot, and to me its benefits are unarguable.

Is your IT organization ready to be Agile, seriously? Score yourself on these questions:


A Practical Guide for Testers and Agile Teams

By John Turner

I have worked with testers on an Agile team before and it has worked very well for both the team and the customer. In my previous role at Bank of Ireland, testers who had come from a traditional testing background worked within our teams to help ensure we had quality deliverables at the end of each iteration. It was different from traditional test approaches in that they were sitting with the team, collaborated constantly and were integral to the process of developing the solution. I never found them critical of poor quality or guilty of ring fencing roles and responsibilities. This was refreshing and without doubt a better way of ensuring quality than those I had experienced before.

Recently, here at Paddy Power, we have been interviewing for a number of open Agile tester positions. I’m pretty sure I know what a good Agile tester looks like but I have often struggled to fully articulate what that entails. I have had this book on my shelf for a couple of months and now I’m looking to it to help me fully understand what an Agile tester is.


Principles for Agile Test Automation

By Emily Bache

I feel like I’ve spent most of my career learning how to write good automated tests in an Agile environment. When I downloaded JUnit in the year 2000 it didn’t take long before I was hooked – unit tests for everything in sight. That gratifying green bar is near-instant feedback that everything is going as expected, my code does what I intended and I can continue developing from a firm foundation.

Later, starting in about 2002, I began writing larger granularity tests, for whole subsystems; functional tests if you like. The feedback that my code does what I intended, and that it has working functionality has given me confidence time and again to release updated versions to end-users.


Vietnam’s National Costume – The Áo Dài

By Brian Letwin

When one thinks of Vietnam, the first picture in their mind is probably the conical hat, gracing the heads of rice farmers and street vendors. But these hats are purely utilitarian, meant to protect people from the rain and sun. On the opposite end of the Vietnamese fashion spectrum is the traditional dress, known as the áo dài, one of Vietnam’s most iconic cultural garments.

Áo dàis were created in 1744 by the command  of Lord Nguyen Phuc Khoat of Hue. At that time, fashion was universal – there was little difference in style between the peasants and the aristocrats. Lord Nguyen, influenced by the fashions of the Chinese imperial court, decreed that that both men and women in his court wear trousers and a gown with buttons down the front. 


Glossary: Agile Testing


Defining Lean Software Development is challenging because there is no specific Lean Software Development method or process. Lean is not an equivalent of Personal Software Process, V-Model, Spiral Model, EVO, Feature-Driven Development, Extreme Programming, Scrum, or Test-Driven Development. A software development lifecycle process or a project management process could be said to be “lean” if it was observed to be aligned with the values of the Lean Software Development movement and the principles of Lean Software Development. So those anticipating a simple recipe that can be followed and named Lean Software Development will be disappointed. You must fashion or tailor your own software development process by understanding Lean principles and adopting the core values of Lean.


In The News – July 2013

Three New TestArchitectTM Products

LogiGear has expanded its TestArchitect product line with the introduction of three new TestArchitect Editions— Professional, Mobile Plus and Enterprise.

The Professional Edition is an economical automation solution for Windows-based applications. Mobile Plus offers Windows-based application plus mobile testing, and Enterprise includes all Windows, web, cloud and mobile testing capability. Mobile Plus and Enterprise support  iOS and Android phones and tablets, with both web and hybrid app testing capability.