02.28.08
Real Programmers Code in Binary

From Corey Goldberg’s blog.
Please notice the comment.
Looks like that keyboard has one key too many.
The only exhaustive testing there is is so much testing that the tester is exhausted. - William C. Hetzel

From Corey Goldberg’s blog.
Please notice the comment.
Looks like that keyboard has one key too many.
I saw this question at watir-general.
Short story is, there is no simple solution at the moment. I am just porting my tests from Watir to Firewatir and I have noticed two major differences:
I created a separate branch of my tests for Firewatir, until I see what should be changed in original tests to make them compatible with both Watir and Firewatir. If I can not make them work at both, I do not think that maintaining two branches will be much work.
If you are using id’s for identifying page elements, I think most of your test should work.
I am updating Watir Tutorial for a while now. It is still not done. At the moment, I am at the Pop Ups page. I have gathered data from Jonathan Kohl’s excellent user guide, Paul Rogers’ excellent pop ups article and Watir FAQ. I will continue to do that, but I need help.
At the moment I have found solutions for 4 types of pop ups: new browser windows, file uploads, JavaScript pop ups and security alerts. 4 types are not covered yet: modal dialogs, modeless dialog, basic authentication and file downloads.
Since pop ups are source of problems for lots of Watir users, I would really appreciate any help. If you have working code, ideas or just a little time to review what I have done, please do it. Tutorial is just a bunch of wiki pages that anybody can edit and comment. If you need help with wiki, please let me know.
One comment says it all:
The world needs more songs about testing!
Go to Geordie Keitt’s blog and listen to Rapid Tester,
a song about a tester at wit’s end about how to test all the stuff that he’s expected to test.
Via Mike Kelly’s blog.