Category Archives: Test Management

Programmatically take screenshot in IronRuby

Posted on June 2, 2010 by Nat

After figuring out how to take a screenshot using .Net, I translated the C# I came up with to IronRuby. Now, when any of my IronRuby-powered tests fail, I take a screenshot – saves loads of time when trying to … Continue reading →

Posted in Example Code, IronRuby, Test Management | Tagged , , , , | 2 Comments

Lessons from a watir success story

Posted on December 19, 2009 by Nat

There aren’t enough UI test automation success stories documented on the net, so here’s my contribution. This post is about  how we started with zero automated UI testing capability, and how a couple of months later we had the capability … Continue reading →

Posted in Automated Testing, Ruby, Test Management, Test::Unit, Tools, WATIR, agile | Tagged , , , , , , , , , | 10 Comments

Find duplicate test names in ruby test::unit files

Posted on October 3, 2009 by Nat

I’ve recently found a couple of instances of tests with the same test name in the same test::unit TestCase class. This is a bad thing, because the when the ruby interpreter reads the file in, it will ignore all methods … Continue reading →

Posted in Automated Testing, Example Code, Making Life Easier, Ruby, Test Management, Test::Unit, Tools | Tagged , , , , , | Leave a comment

Quick and easy Watir test suites with Test::Unit

Posted on September 24, 2009 by Nat

A test team usually has a need for a few fixed test suites, eg: a sanity suite or a suite which contains all tests for a full run. There’s usually also a need to be able to create suites with … Continue reading →

Posted in Automated Testing, Example Code, Making Life Easier, Ruby, Test Management, Test::Unit, Tools, WATIR, agile | Tagged , , , , , , , , , | 2 Comments

Finding the balance between hacky and over-engineered UI test automation frameworks

Posted on September 4, 2009 by Nat

There are very few real requirements for a UI test automation framework: It should provide accurate test results It should provide accurate test results every time you ask it for results It should make it easy to write tests It … Continue reading →

Posted in Automated Testing, General Testing Stuff, Mistakes, Test Management, Testing Theory | Tagged , , | 1 Comment

How to print test names when executing Ruby Test::Unit tests

Posted on August 5, 2009 by Nat

When I run my test_all.rb from the command line, I get ‘.’ when a test passes, but I don’t know which test it was that passed. I only get the names of tests that fail or error. Quite sensible – … Continue reading →

Posted in Automated Testing, Making Life Easier, Ruby, Test Management, Test::Unit, Tools | Tagged , , , , | Leave a comment

Test Case Interdependency

Posted on July 12, 2007 by Nat

One of the most common ways of structuring a series of test cases is to make one test case dependent on the outcome of another. For example, Test Case ‘A’ verifies the functionality surrounding the ability to create an account. … Continue reading →

Posted in Automated Testing, Manual Testing, Mistakes, Test Management, Testing Theory | Tagged , | 1 Comment