test automation


Guide Your Agile Development with Traceable Tests

Testing professionals who are learning about agile often want to know how they can provide traceability among automated tests, features, and bugs and report on their testing progress. Here, Lisa Crispin gives an example of how her previous team worked together to integrate testing with coding and helped everyone see testing progress at a glance.

Lisa Crispin's picture Lisa Crispin
Accelerating the Adoption of Technical Practices

Agile teams are supposed to take responsibility for how they work and how they learn. But what if you need to jump-start that learning? Agile transformation is about making this happen rather than waiting for it to happen. You need to get your team to learn the technical side of agile, and soon. Here are some effective approaches.

Scott Barnes's picture Scott Barnes Clifford Berg
Automation Test Suites Are Not God!

In today’s age of tight deadlines and accelerating delivery cycles of software, test automation is surely favorable for the world of functional testing and critical to the success of big software development companies. But its various benefits have led to unrealistic expectations from managers and organizations. This article highlights the role and use of automation in an agile context and the irreplaceable importance of manual testing.

Nishi Grover's picture Nishi Grover
Using Containers for Continuous Deployment

Pini Reznik explains how containers can help shorten the software development feedback loop by drastically reducing the overhead involved in deploying new software environments. This leads to faster build and test executions and simplifies the standardization of the development and production environments, allowing for an easier transition to continuous deployment.

Pini Reznik's picture Pini Reznik
Applying Agile to Distributed Development: A Format for Success

Alexey Krasnoriadtsev has been managing globally distributed projects for more than ten years, applying agile methods to improve process efficiency, increase team productivity, and deliver quality products to market faster. With teams split across the globe, he shares with us his approach he's adopted to overcome the communication, process, and quality assurance obstacles facing team members who are a date line and time zone away.

Alexey Krasnoriadtsev's picture Alexey Krasnoriadtsev
Transition to Agile: Large Technical Debt, Small Project

When you transition to agile and you have a reasonably size codebase, chances are quite good that you’ve been working on the product for a while. You certainly have legacy ways of thinking about the code and the tests. Now learn how to work yourself out of the technical debt you have accumulated.

Johanna Rothman's picture Johanna Rothman
Is Test Automation a “Project”?

Test automation can turn into a real pain in the neck if a designated team is in charge of it or if the automators work on it as a separate project. In this article, Lisa Crispin seconds Bob Jones’s recent call for whole-team test automation and elaborates on the dangers of relegating test automation to an isolated project rather than integrating it into the overall software development process.

Lisa Crispin's picture Lisa Crispin
Test Automation in an Agile Environment

Many of us keep asking: If the benefits of automated testing are so vast, why does test automation fail so often? Artem Nahornyy addresses this common dilemma.

Artem  Nahornyy's picture Artem Nahornyy
Orders of Magnitude in Test Automation

Mike Kelly explains the following heuristic approach to help ensure your testing is roughly inline based on orders of magnitude across the various types of automation. It’s not a method for measuring effectiveness. Instead it’s simply a “smell” to tell you when you might need to take a little extra time to make sure you’re focusing your automated testing efforts at the right level.

Mike Kelly's picture Mike Kelly
Agile Testing as if People Mattered

As a test professional in waterfall, I was used to getting the code much later and buggier than I expected and being under tremendous pressure to finish my testing before the go-live date hit. Then one day, I found out that there was a better way. Testers could be involved much earlier in the lifecycle, they could participate in requirements and design decisions as they happened, and the code could actually be unit tested before I received it! Heaven? Nope, agile.

Daryl  Kulak's picture Daryl Kulak


AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.