<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by JeanDal: Hi,
I heard that QArun was specialized in web app
I just want a confirmation 'cause I'm not sure about that.
Thanks a lot
Not sure what you mean by "specialized in web app test."
I mean by "specialized in web app" that QARun is usefull for tests related to web sites, web applications and that it could be better to use an other tool like WinRunner or Rational Robot in order to test non web GUI.
Thanks for your answer.
Absolutely not. We test web-apps all day long, and QARun is much more in the "I'm automating a mainframe" mindset, so it becomes *VERY* difficult to do even the simplest things against web-apps without a lot of upfront work.
- There is no built in way to get the source code of a page. You have to hack up a thing to View->Source or write your own DLL functions.
- If you try to click an item that is not visible on the screen (ie: scrolling) then the action will fail unless you put in ScrollDown/Retry code.
- Older versions of QARun were very crash-prone when automating certain versions of IE, especially just after calling WinClose.
- You basically have to write separate codebases for IE v. NS. It is difficult to get stuff working in both versions at the same time. (This might be an unavoidable fact of life).
- You cannot really automate against NS6.0+ that I've seen. This also might be a fact of life, and not possible with other automation tools.
...if your sales rep is telling you anything different, your sales rep is lying, as I believe these are all well-known issues.
Basically, QARun has not much built-in helpful utilities to automate against dynamic web-pages, and you can spend a lot of time writing infrastructure / helper / support code in order to get it to do what you want.