July releases round-up

Posted by on August 05, 2009|Comments|Read full article

rWebUnit 1.3.1

The stylesheets, javascripts and image references in dumped html source are now substituted with absolute URL for better viewing.

TestWise 1.5.x

TestWise 1.5 introduced many new features particularly in refactorings and windows CHM help, checkout ChangeLog for details.

PRoR 186-v20

Gem upgrades: rWebUnit 1.3.1, win32 utils, fastercsv 1.5, prawn 0.5, ...


And many updates to the documentations.

PRoR-191 preview: Watir on Ruby 1.9.1

Posted by on August 06, 2009|Comments|Read full article

The long waiting One-Click Ruby Installer for Windows is coming closer, it's first preview release has been available over 2 months now. Based on it, we packaged a preview release of PRoR with Jari Bakken's fork of Watir for Ruby 1.9.1.

You can download it here, WARNING: this is a preview software.

Here is comparison of running a fairly complex 3-minute Watir test case using two versions of PRoR-191 and PRoR-186.

Ruby 1.9.1 (mingw32)

C:\sandobx>ruby -v
ruby 1.9.1p129 (2009-05-12 revision 23412) [i386-mingw32]

C:\sandobx>spec -fs lodgement_spec.rb
loading win32ole from stdlib on 1.9
Loading pages ...Cost: 1.640552
Lodgement 
 - [Story 123] A complete end-to-end test happy case
Finished in 171.78125 seconds

Ruby 1.8.6 (mswin32)

C:\sandobx>ruby -v
ruby 1.8.6 (2008-03-03 patchlevel 114) [i386-mswin32]

C:\sandobx>spec -fs lodgement_spec.rb
Loading pages ...Cost: 0.656
Lodgement 
 - [Story 123] A complete end-to-end test happy case
Finished in 174.983 seconds

Here are some observations:

  • No noticeable performance differences, as expected, as test execution time is most depend on web application server response time and browser rendering time.
  • Page class loading time (Ruby's require/load classes) using Ruby 1.9 is longer than in Ruby 1.8.6
  • close_others (Watir) does not work

TestWise Tips - Capture web pages from test execution

Posted by on August 27, 2009|Comments|Read full article

Quite often, testers/developers want to capture web pages from executing automated test cases. There are a number reasons (or benefits):

  • Manual Inspection / Verification
  • Capture application error text or stack traces
  • Check or looking for certain text (such as payment receipt number, then reconcile manually)
  • Auditing

By using TestWise, you can do it effortlessly if using Page Objects (ie. if you are new to it, please have a look at this paper)