Comments on: Watin Test Recorder: Watin Model Style

By: monarch

monarch — Thu, 12 Feb 2009 18:03:14 +0000

I got the latest code from SourceForge and see the Watin Model tab but no entries like that in your screen shot. Is there some trick to getting the WATIN model to work?

By: jfk

jfk — Tue, 18 Mar 2008 19:22:52 +0000

go James go

By: stefano

stefano — Wed, 27 Feb 2008 13:42:53 +0000

thank you very much, James. It should be very appreciated.

By: James Avery

James Avery — Tue, 19 Feb 2008 15:50:37 +0000

I got pulled in other directions, but the work is done and hopefully in the next week or two I am going to integrate it into the main watin code.

By: stefano

stefano — Tue, 19 Feb 2008 07:49:05 +0000

I was looking forward to this project. no more news?

By: Ken Draper

Ken Draper — Fri, 25 Jan 2008 20:18:19 +0000

We are a small web development shop who would greatly benefit using this product. Any date for your new release?

By: Joshua McKinney

Joshua McKinney — Fri, 30 Nov 2007 01:50:23 +0000

I second phil’s Duuuuude comment. I’m definitely keen to see this.

By: Scott Bellware

Scott Bellware — Wed, 28 Nov 2007 19:21:00 +0000

Just to be clear, I'm talking about core DSL for testers, not customers. Jeremy is talking about customer DSL through FitNesse.

This point also goes to the assumption that led to the creation of Watin by .NET developers: that C# and Ruby are equals among languages for testing.

Part of the reason why Watir is powerful, is that Ruby is a great language for evolving a DSL from an API.

This is a point that C# developers miss because there is no notion of a next level of abstraction in C# above an API, and the process of abstraction for C# developers is prematurely terminated at the API.

This shortcomming of exploration and understanding on the part of .NET developers into a new knowledge realm is a big reason why Watin exists in the first place.

If you're a .NET developer without a purview into *why* leading testers are using Ruby, and without a purview into Ruby capabilities that reach over and above those of C#, you might just assume that Watir's power rests merely in its ability to automate a browser, and therefore there's no reason why a C# clone shouldn't be created so that C# programmers wanting a piece of the browser automation game can continue with C#.

Ruby and C# aren't languages of equivalent capability; Watir and Watin are tools that reflect the capabilities of the underlying environment; .NET developers might have learned something valuable from Watir if they had believed that they had something to learn before creating Watin.

Folks, even the testers are out-pacing us .NET developers on matters of plain old programming practice.

By: JAmes avery

JAmes avery — Wed, 28 Nov 2007 16:58:15 +0000

Scott,
I see where you are going with that (the DSLs and such), and it is something I will look into more. But, I also think there is room for this tool as well. I have 100s of pages to cover and no business users available to write tests, this will help me do that so I can get on the road of refactoring this boat. It might also work better for people like Phil who are working on open source projects with no real business users to speak of (and a large legacy code base as well)

If anyone else is interested in the DSL approach here is a good intro:

http://codebetter.com/blogs/jeremy.miller/archive/2006/07/15/147400.aspx

-James

By: Scott Bellware

Scott Bellware — Wed, 28 Nov 2007 16:42:18 +0000

@secretGeek,

Yeah, that’s usually the official party line for The Society for the Preservation of Software Technology Anachronism.

Not sure if you’re pointing out for effect, if you’re a card-carrying member. I’ll play along though…

Yep. I’m such a good programmer, I don’t see how I could possibly not be naturally endowed with all the knowledge relevant to contemporary software testing practice. Sheesh. God bless yesterday. if it weren’t for what I learned yesterday, I might be expected to continue to make an effort to learn again today… let alone tomorrow!