Comments for Nat On Testing

Comment on Lessons from a watir success story by Randy

Randy — Tue, 27 Jul 2010 23:09:42 +0000

Its always useful to learn from other peoples successes (and failures), thanks for sharing Nat, very well written!

Comment on Lessons from a watir success story by Jason

Jason — Mon, 26 Jul 2010 02:36:41 +0000

Great write-up. Brilliant. Some great ideas and tips here. Thanks.

Comment on Automating a WPF UI using ruby, win32ole and White by Krishna

Krishna — Mon, 19 Jul 2010 10:03:04 +0000

Hi,

I want to know whether we can automate the WPF UI using RFT 8.1.
Because I am not able to recorgnise all the objects in WPF UI such as labels, tabs, some icons etc…

Thanks
Krishna

Comment on Programmatically take screenshot in IronRuby by Nat

Nat — Thu, 03 Jun 2010 16:57:33 +0000

Great stuff. I’ve written a similar app in java before, now a .Net-dependent one in ironruby… but there still remains the problem of a multi-platform solution. A tool that takes a shot of every screen, not just the main one… It would be something very simple like:

ScreenShotApp.grab_and_save_to(“c:\\screenshot.png”)

which would also cope with:

ScreenShotApp.grab_and_save_to(“/Users/nat/screenshot.png”)

…etc…

On being called, it would figure out what platform it’s running on and use the appropriate (and well-hidden-from-the-user) platform-specific code.

Any takers?

Comment on Programmatically take screenshot in IronRuby by Alister Scott

Alister Scott — Thu, 03 Jun 2010 09:39:02 +0000

Have you seen what Tim did on this?

http://altentee.com/2008/capturing-screenshots-in-watir/

Comment on FireWatir JSSH “Unable to connect” – FIXED! by c0de

c0de — Sat, 10 Apr 2010 04:34:18 +0000

First problem solved! THX!

Comment on How to check for errors on every page using Watir by Robbie Wareham

Robbie Wareham — Tue, 06 Apr 2010 16:59:38 +0000

“add_checker” runs a lot more regularly than just page load. I discovered this when using “add_checker” to keep a copy of the previous page html to report on failure (when investigating a failure, the previous page is often more useful than a screenshot of the page where the error occured, infact errors dismissed as flakey testing turned out to be caching issues because we had the html of the previous page to refer to). The “previous” html was continually a copy of the “current” html, and it was then that I discovered that a lot of events trigger add_checkers.

Also, add_checker can easily miss page loads as well. Again while investigating “flakey” tests, I saw that when the application navigated from page A to page C via a quick visit to page B, occasionally add_checker failed to run on page B. Unfortunately the add_checker running on page B was crucial to test reliability!

Anyway, these are my observations on add_checker, and you’ll be pleased know that test reliability is much improved now that I fully understand add_checker.