| «« Managing a Music Collection in 2004 | An About JFace »» |
|
About
I'm Ryan Lowe, a Software Engineering graduate living in Ottawa, Canada. I like agile software development and Ruby on Rails.
I write this blog in Canadian English and don't use a spell checker. Typos happen.
Projects
» Full-time Ruby on Rails freelancer
» Full-time with Rails since May 2005 » Former committer for RadRails (now Aptana) » I also have a few Rails side-projects in development: 1. wheretogoinTO.com Toronto nightlife 2. Hey Heads Up! TODO list and sharing 3. Layered Genealogy family history research 4. foos for foosball scoring 5. fanconcert for music fans (on hold) Hiring Rails developers? I can telecommute by the hour from Ottawa, Canada »» Email: rails AT ryanlowe DOT ca
BulletBlog
Now hosted on Hey! Heads Up -- check it out!
Syndication
Pings
Recent
Derek Lowe's (Ryan's older brother) words at Ryan's funeral
blog@ryanlowe.ca no more Forging Email Headers: Good, Bad or Ugly? Sarcastic Dictionary (Part 1 of Many) Tags Hierarchies Twisting Rails is Risky Business Risky Business? My Take on Early Alphas Whoa, it's August 2007 Closing Comments A Postscript to "Growth at the grassroots" »» All Blog Posts
Linkage
del.icio.us/ryanlowe
technorati/ryanlowe.ca/blog Aurora Roy Jim Andrew Trasker Travis Kibbee Karen Dr. Unk Ayana Van Bloggers Joel Spolsky Robert Scoble Tim Bray Dave Winer Raymond Chen James Robertson Ruby/Rails Bloggers rubyonrails.org weblog David Heinemeier Hansson Dave Thomas James Duncan Davidson Mike Clark Jamis Buck Signal vs. Noise Tobias Luetke Amy Hoy: (24)slash7 Jeremy Voorhis Eclipse Bloggers Planet Eclipse EclipseZone Luis de la Rosa Eclipse Foundation Kim Horne Billy Biggs Ian Skerrett Mike Milinkovich Bjorn Freeman-Benson Denis Roy
Archives
|
Acceptance Testing Web App
Here's an idea for an acceptance testing tool I'm looking for. I say "looking for" instead of "want to build" because I'm sure 100 other people have already thought of it. The AudioMan project uses a spreadsheet to keep track of customer acceptance tests. These tests are derived (and grouped into) use cases given to us by the customer as feature requests. Each test consists of a number of steps and each step has an expected result: a behaviour by the application. If a step fails we log a bug and note it on the spreadsheet next to the failure. This sounds simple enough, but when you are adding features all of the time the spreadsheet is continually changing. Stuff like adding tests, removing tests for features that were taken out, changing steps or expected behaviours because the user interface has changed. So you end up with a new version of the spreadsheet every week. If you test the latest build with the latest spreadsheet all of the time it's hard to track your progress from just metrics because it might seem like the "completed %" never changes. It would be nice to have this all in a web app, that users can log into and put results into. They don't even have to do a whole test run, just part of one. Then you combine results from all of the users to find what you're really looking for: unexpected regressions. You already know what hasn't been implemented, that isn't interesting. The whole reason why you want these results is to make sure the stuff that worked last week still works. And if you had a lot of users putting testing results into the system (hey we can dream, right?) that information would be pretty handy ... so making it easy to use is important. But the real kicker is being able to use the testing results from a run done with "spreadsheet" version 40 and compare them to the results done from "spreadsheet" 30. Of course 30 will have less tests, probably have a few that we retired and aren't in 40 and will definitely have a few tests with changed steps/behaviours. This web app has to be able to know this and sort through it. All I want to be able to see is progress and regressions. Find this web app for me, would ya guys? Thanks. This would have been a good fourth year software engineering project for somebody too. A little PHP and mySQL. Posted at January 23, 2004 at 11:14 AM ESTLast updated January 23, 2004 at 11:14 AM EST Comments
This sounds just like what Peter wrote for the Passport Office. I belive that it was called "TestTracker" or something like that. It was a way to test and report on the manual tests that were performed. As for being able to compare version 30 and 40, what exactly do you want the web app to be able to do? Figure out what is new and what is not? What steps have NOT changed, and if you have gone from "pass" to "fail" on those steps? » Posted by: Jim at January 23, 2004 01:21 PMCheck this out: Here's to another feature... integration with Fit / Fitness. I have only scratched the surface of this framework - but pretty much, you make an html table outlining your tasks, and the framework runs that code... http://fit.c2.com/ |