|
||||
|
“We can’t automate everything. It costs too much.” I’ve heard that concern—that test automation costs too much—multiple times when talking with folks in the middle of an Agile transition. They know that automated regression testing is important in an Agile context. But they’re concerned about the costs. And they can’t even imagine getting to a point where all . . . → Read More: Why Test Automation Costs Too Much This post started out as a quick little entry about a cool parlor trick you can do with RSpec to make it work for auto-generated test data. But in the middle of writing what was supposed to be a simple post, my tests found a subtle bug with bad consequences. (Yeah for tests!) So now this post . . . → Read More: Adventures with Auto-Generated Tests and RSpec The subject of how much to automate, and the related topic of how to calculate the ROI for test automation, comes up on a regular basis. In fact, it popped up on a couple of the mail lists I read recently. Usually there’s at least one person arguing that test automation is expensive and that there are . . . → Read More: How Much to Automate? Agile Changes the Equation Are you an open source test automation tool aficionado? I am. That’s why I’m organizing OSTATLI, a small, non-commercial, invitation-only gathering next Thursday in my office in Pleasanton to provide an opportunity for us to express our mutual love of open source test automation tools. Participants will bring their laptops, loaded with their favorite tools, and we’ll . . . → Read More: Open Source Test Automation Tools Love-In (OSTATLI), Feb 5, Pleasanton, CA At the AA-FTT workshop last October, I did this lightning talk titled “A Place to Put Things.” In it, I propose standardizing on places to put different kinds of information associated with automated functional tests. It seems to me that one of the key success factors for the xUnit family of unit testing frameworks is that they . . . → Read More: A Place to Put Things …and it isn’t cooperating? I sympathize. I recently fought my way through the process of automating a test to reproduce a bug on a legacy(*) web application that had no IDs on any of the elements that I wanted to address. And I thought it might be helpful to capture some of my lessons learned here in . . . → Read More: So You're Trying to Automate Tests for a Legacy Web Application… Several people have asked me recently why I’m not a fan of the traditional test automation tools for Agile projects. “Why should I use something like Fit or Fitnesse?” they ask. “We already have <insert Big Vendor Tool name here>. I don’t want to have to learn some other tool.” Usually the people asking . . . → Read More: Agile-Friendly Test Automation Tools/Frameworks “They never give us enough time to automate our tests, and then they complain at us that we don’t test fast enough!” J. shook her head. “And when I want to hire more people to help automate, they tell me I have too many people already! Management blames me because testing takes too long, but . . . → Read More: Effective Test Automation Isn't Created in a Vacuum At the moment, I’m creating a little Acceptance Test Driven Development (ATDD) demo. I’m keen on Ruby these days, so I wanted to do it all in Ruby. And I wanted to use Fitnesse. And as it happens, Fitnesse supports RubyFIT. Or RubyFIT supports Fitnesse. Something like that. So I . . . → Read More: RubyFIT and Fitnesse Some time ago, I wrote about how Jennitta Andrea (among others) fired my imagination about what could be possible with advances in functional test automation tools. I’m delighted to announce that Jennitta is heading up the Agile Alliance Functional Testing Tools program. With her boundless energy and contagious enthusiasm Jennitta recruited Ron Jeffries and me to . . . → Read More: Call for Participation: the Agile Alliance Functional Testing Tools Visioning Workshop |
|
|||
|
Copyright © 2010 Test Obsessed - All Rights Reserved |
||||
Popular Posts