| || |
how a tool differ a .net webform from html page
can anyone explain how test tool know one page is .net webform or traditional html page.
Can i say when a tool support web testing, means it can support .net web application testing?
Can a tool retrieve server control property? or all test tools can only identify any control as a html form control?
Very Thanks for any comments.
Re: how a tool differ a .net webform from html page
Richard, your query is a bit confusing, so I will try to answer based on what I think you want to do.
1. You tell the test tool what interface to use when you issue script commands. At a basic level you know to use a character interface or a GUI object interface method. Depending on the tool, it may support many different domain libraries, and your script commands must pick the right one for the specific task at hand.
2. No, you need to use the right interface for an HTML dialog and another for .Net applications, in the same testing tool, using the approach above. Not all tools support all domains, so you need to keep that in mind when you select your tool. This forum covers many examples on that topic.
3. What the tool can retrieve depends on what the level of support is for a given domain and if you invoke the proper interface. Within that, there are more powerful tools and some are better one way than another, again it is useful to search in this forum for different examples.
Your questions are rather generic, so if you want to get more helpful feedback you should specify what it is that you are trying to accomplish. You may be surprised how much feedback you can get.