Pages
-
Recent Posts
- Bewildr + Cucumber Example
- Counting strings in a file: Ruby vs Windows Command shell
- IronRuby vs. Gherkin – a temporary fix
- Learning Ruby? Here’s the book for you…
- Announcing ‘bewildr’ – test your WPF UI apps with IronRuby
- How to get the submodules of a ruby module
- Netbeans ‘Cucumber Features’ plugin in Beta!
Recent Comments
- Nat on Counting strings in a file: Ruby vs Windows Command shell
- Neil on Counting strings in a file: Ruby vs Windows Command shell
- Andrew Grimm on Stop Ruby’s Test::Unit suite files running all your tests
- Nat on How to connect to an Oracle database in IronRuby
- Mark Micallef on How to connect to an Oracle database in IronRuby
Tags
Abbot agile agile testing Automated Testing bewildr Books cheat sheet cucumber database Data Conversion Testing Example Code Exceptions FireBug Firefox Firewatir fitnesse Fix Internet Explorer IronRuby ISEB Java mac os x Maximo Mistakes MS Access NetBeans QA Rational Functional Tester Regular Expressions RQuery RSpec Ruby Ruby on Rails Safari SQL sqlite Standards Test::Unit Test Case Management Test Data testing Tools WATIR white win32oleCategories
- agile
- Automated Testing
- bewildr
- Books
- cucumber
- Data Conversion Testing
- Example Code
- fitnesse
- General Testing Stuff
- IronRuby
- Links
- Making Life Easier
- Manual Testing
- Mistakes
- Rational Functional Tester
- RQuery
- RSpec
- Ruby
- Ruby on Rails
- Test Data
- Test Driven Development
- Test Management
- Test Management
- Test::Unit
- Testing Theory
- Tools
- Uncategorized
- WATIR
- white
- win32ole
Meta
This work by Nathaniel Ritmeyer is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported.
Category Archives: Automated Testing
TURN: test::unit reporting as it should have been…
TURN (“Test::Unit Reporter (New)”) aims to fix test::unit‘s default output. Instead of waiting until the end of a test run for failure details, Turn displays failures immediately. It looks promising… Bookmark to:
Posted in Automated Testing, Making Life Easier, Ruby, Test::Unit, Tools
Tagged Automated Testing, Ruby, Test::Unit, Tools
Leave a comment
How to test a WPF app using IronRuby and White
—UPDATE— Since I wrote this post, I have put together a ruby gem designed for testing WPF UIs called ‘bewildr’. I wrote up an introductory post about bewildr here. Bewildr removes the need for using White – it’s written in … Continue reading
Posted in Automated Testing, Example Code, IronRuby, Making Life Easier, Ruby, Test::Unit, Tools, bewildr, white
Tagged Automated Testing, bewildr, Example Code, IronRuby, NetBeans, Ruby, Test::Unit, Tools, white
1 Comment
Updated script to list all cucumber step definitions
In a previous post I put up a small script that would dump out all step definitions available in a cucumber project. Here’s an updated version… it hasn’t changed much apart from the output is now a html table that … Continue reading
Posted in Automated Testing, Example Code, Making Life Easier, Ruby, Tools, cucumber
Tagged Automated Testing, cucumber, Example Code, Regular Expressions, Ruby, Tools
Leave a comment
Automating a WPF UI using ruby, win32ole and White
UPDATE (17/2/2010): It *can* be done, see here: How to test a WPF app using IronRuby and White. The solution doesn’t use win32ole though… just IronRuby —– Short story: it doesn’t work (…well, not out-of-the-box). Long story: I’ve finally had … Continue reading
Posted in Automated Testing, Example Code, Ruby, Tools, white, win32ole
Tagged Automated Testing, Example Code, Ruby, Tools, white, win32ole
1 Comment
Lessons from a watir success story
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 agile, Automated Testing, FireBug, Firefox, Firewatir, NetBeans, Ruby, Test::Unit, Tools, WATIR
10 Comments
How to list all cucumber step definitions
If you’re using cucumber you probably have step definitions split across several files, and you’re probably using a tool that doesn’t do a good job of listing the available step definitions (one of the biggest downsides of using cucumber). What … Continue reading
Posted in Automated Testing, Example Code, Ruby, cucumber
Tagged cucumber, Example Code, Ruby
4 Comments
Cucumber step definition for debugging
Building on a previous post about debugging cucumber tests with ruby-debug, here’s a simple cucumber step definition you can use in your cucumber scenario in order to debug it: Then /^I debug$/ do breakpoint 0 end Use it as follows: … Continue reading
Posted in Automated Testing, Example Code, Ruby, Tools, cucumber
Tagged Automated Testing, cucumber, Example Code, Ruby, Tools
Leave a comment














