comment on

I've chased this particular rabbit down an alarming number of holes over the past several years.

I have a couple of suggestions (but they don't involve any of the software you've mentioned):

You mention SAMIE and Win32::IE::Mechanize, so I'm going to assume that you're working on a Windows platform with Internet Explorer. Far and away the best IE test driver I have ever seen is called WATIR and runs under Ruby. It works by directly manipulating the DOM/COM interface in IE. The developers on the project are great, and have implemented a lot of features at users' request. The WATIR framework is far superior to SAMIE, IMO.

But that still leaves the problem of javascript popups and all the other things you need to manipulate in order to do effective system/functional testing. It is still the case that the tools to develop software are far more powerful than the tools to test software.

I am building a test automation system right now that uses WATIR/Ruby to muck around in the HTML, but uses Win32::GuiTest to handle complex javascript popups. The Perl layer also uses all of the other powerful Perl goodness of file checking, network connections, DBI, etc. It's turning out to be remarkably effective.

If you are interested in cross-browser testing, both Selenium and IEUnit I think show a lot of promise, but they have limitations that make them impractical for my particular project.

Please let us know your experience, as there are many other monks attempting this work, also.

In reply to Re: Automation and Manual testing using HTTP::Recorder by McMahon
in thread Automation and Manual testing using HTTP::Recorder by mkirank

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks