| «« Managing Yesterday's Test Methods | Why Pyra for Google? »» |
|
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
  
|
Administering A and B
I realised that test suites are the best way to administer A and B tests. You keep the tests where they always were but move them between Test Suite A and Test Suite B. No complicated software necessary -- and Test Suite A always stays green. Posted at February 22, 2003 at 11:24 AM ESTLast updated February 22, 2003 at 11:24 AM EST Comments
Ah, that is a nice simple solution. I like that. Do you think that this would be a good plan for us? Having two suites? » Posted by: Jimbo Jones at February 22, 2003 01:40 PMI have a question. When you find a new bug, and you make a test case for it, does it go into the "A" suite or "B" suite? You are not checking in code that breaks the build, you are just adding a test that you had not thought of before (or had just incountered in user / customer testing). If you put it into "A", it will no longer be green, but it doesn't mean that the code there works all the time anyways... you are sort of lying to yourself thinking that the code passes all tests. So, do you lie to yourself, or break the "always green" rule? » Posted by: Jimbo Jones at February 23, 2003 01:58 PMNah, you don't lie to yourself. New bug test methods go into the B suite because they fail. You are only lying to yourself if you think your code has 0 bugs. :) » Posted by: Ryan at February 23, 2003 11:37 PM |
