Telerik Test Studio摸索笔记（十一）

Here's how these URLs would break out into Page nodes in the Elements Explorer with the following Compare Mode options:

• BaseURL
• Compared portion of URL: http://www.google.com
• Result: All three would be the same page.
• FullPath
• Compared portion of URL: http://www.google.com/translate
• Result: All three would be the same page.
• FullPathAndQuery
• Compared portion of URL: http://www.google.com/translate/?hl=en#de|en|hungary
• Result: All three would be separate pages, since each URL is different from the others. (Query and Fragment portions differ.)
• FullPathAndQueryNoFragment
• Compared portion of URL: http://www.google.com/translate/?hl=en
• Result: The first two URLs would be one page (the Query is the same: "?hl=en"), and the third would be a separate page. (Query has a different language.)
• TheRelativeoptions work the same; however, they ignore the www.google.com portions of the URL, so two different sites with the same Path, Query, and Fragment would end up as the same page, for example:
• http://www.google.com/translate/?hl=en#de|en|money
• http://teststudio.net/translate/?hl=en#de|en|money
• TheTitleoption only uses the page title for comparison and ignores the URL entirely.

通过不同的录制方式

可以解决在不同环境上的脚本移植

一开始默认用的是FullPathAndQuery

后续试试RelativePathAndQuery

感觉思路上又可以走不寻常路了

本来是想通过录制一个project，里面是通用的功能

然后另存为另一个project

一个project针对一个项目

现在的话

倒是可以统一一个project里面

然后录制所有脚本

用testlist来区分

把我那个另存为计划任务的project，执行有问题的情况给解决了