Letter from the Editor – September 2012

There has been a tectonic shift in software development tools in just the past few years. Agile practices and increasingly distributed teams have been significant factors but, in my opinion, the main reason is a new and more intense focus on tools for testing driven by more complex software and shorter development cycles.

There have always been developer tools and platforms (IDEs) and they are getting better. There have always been project management tools and now they are extending further across teams and becoming more integrated.

For a long while testing stood alone. Most of the focus was on integrating bug trackers into team tools, but that’s typically where it stopped. The first generation of integrated tools were cumbersome and poorly documented, and their lack of sophistication failed to provide significant benefits to the whole team or to make product development faster. 
A lot has changed. Stand-alone tools are on the road to obsolescence. The direction today is full integration and transparency. Rapid development and deployment demands greater automation, communication, focus, and information transfer. To achieve this, integrated test platforms at a minimum need to include test case managers, automation tools, bug tracking, and automatic reporting that can fully integrate with and leverage development platform tools and reporting.

New tool technology is contributing to improved development practices. XP’s Continuous Integration (CI) practice is based on autobuilds from source control using an integrated bot or agent, automated re-running of unit, integration and regression test, and automatic notification of code changes, bug fixes, and automated test failures. Continuous Integration enabled by better tools is now separating successful teams from Scrumbuts or more aptly—slow, less than efficient teams.

We have often stressed testers being integrated by co-locating in the same work area as developers to better integrate in the planning and estimation process, and have better access to product owners and customers. Ideally, this paves the way to becoming more technically integrated and valuable. This leads to teams that are cross-/multi-functional and have a bigger variety of quality work. The result of this type of integration is more gray box, and earlier test execution, and ultimately better product quality.

For your career growth and to better support your product teams, learning more about integrated test platforms, ALMs, CIs and the varieties of tools and practices that go along with them will be a great benefit. This issue focuses on the tools and practices that will help and support all of us in providing rapid and higher quality information to the rest of the product development team.

In this issue, Eric Landes looks at the benefits of using Agile ALM; LogiGear Marketing Director, Joe Luthy presents a keyword based testing tool for Visual Studio; an article from Software Consortium examines recent changes to the ALM toolbox; I talk about the importance of integrated test platforms; Bryce Johnson shows us how to speed up automated testing and finally, Tad Anderson reviews the book Continuous Integration in .NET.

I hope you find this issue full of information about the importance, growth and use of integrated test platforms, and that you learn a few tips about Continuous Integration.

Next issue? Mobile Test Automation!

Michael Hackett
Senior Vice President
Editor in Chief

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, cost-effective results. Since 1994, LogiGear has worked with Fortune 500 companies to early-stage start-ups in, creating unique solutions to meet their clients’ needs. With facilities in the US and Viet Nam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

The Related Post

Hi everyone and welcome to our fourth edition of LogiGear Magazine. This month we finish Michael Hackett’s piece on “Agile in Testing” with part five, Tools.
On the whole, everyone wants to do a great job, have a better work environment, happy clients and customers, and to be employed by a company earning lots of money. All great goals! But this is not always the case. When it is not, you can suggest process improvements, better tool use, different estimating techniques, ...
DevOps can be a big scary thing. Culture change, constant collaboration— whatever that means— a big new set of tools… it’s a lot. What most teams want is to have a smooth running software development pipeline. I have stopped using the phrase “DevOps,” and now I say “Continuous Delivery.” There are many reasons for this.
How do you test software? How do you validate it? How do you find bugs? These are all good questions anyone on your project team or anyone responsible for customers may ask you. Can you articulate your test strategy─not your test process, but explain your approach to testing? I find that this can be a ...
This is our first Trends issue in our 10- year history. Trends are important to help foresee what is on the horizon and coming next.
For everyone still celebrating holidays: Happy Lunar New Year! At this time of the year many teams and companies are starting new projects, new initiatives, and hiring new staff. LogiGear Magazine will continue to be the resource for you for better testing with much less stress! We are excited about the focus of this month’s ...
Everything is mobile. What else can we say? Everything. If your product or service is currently not, it will be very soon. As Apple says: “There’s an app for that.” There is an app for everything. The race for mobile apps has consumed the software development world. I did a few projects at Palm Computing in the ...
This is our third issue concerning topics of Continuous Delivery (CD) and DevOps with the inclusion of Continuous Testing. DevOps has been around for a while and I hope the period of buzz is over and companies moving towards building a development pipeline have begun their process, including changing their test strategies.
A lot has changed since I began staffing test projects. From hiring college students and interns for summer testing programs, to building networks of offshore teams around the world, and from having 24-hour work schedules to having instant crowdsourced public beta or bug bounty testing—things have changed.
Because of the type of work I do (consulting projects at different companies), I’ve been lucky in my Software Development career to have worked on a bunch of software projects specific to hardware devices or integrating new hardware into software systems. Starting with the Palm Pilot, I worked on some operating systems (OS) projects, firmware, ...
What is testing in Agile? It’s analogous to three blind men attempting to describe an elephant by the way it feels to them. Agile is difficult to define and everyone has their own perspective of what Agile is. When it comes to testing and Agile the rules are what you make them. Agile is ideas ...
Every organization goes through times when the internal, or home team, cannot execute the testing project easily or quickly enough. The reasons are many, from the lack of an effective test strategy to low automation engineering skill, to staff positions going unfilled due to a great job market. With everyone working and very few people ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe