Yes, setting the compare mode mode to RelativePathOnly and specifying the common part of the URL helped me.
Now i have another question regarding finding the element on the specific page.
I have several test instances where the test will be executed, but in specific cases, URL may have nothing common .
Almost as described here. The base URL for project settings is currently set to http://qadomain1.com/Baseline_Build. I have an element that is added to some app page on specific instance.
The full URL to that page for this specific instance looks like this:
http://qadomain1.com/ - the domain, that may change.
/Baseline_Build/ - instance name that may change also.
/area/PageName.aspx - static path to page.
?pid=12345&gid=12345 - dynamic query.
The idea is to add element/page to element explorer that will be found on every of that instances listed above (if i will use running tests via test lists with different base url's).
What is the best way to do this?
By setting for the page element the base URL like: 'http://qadomain1.com/Baseline_Build' and limiting the path to 'area/PageName.aspx' this will make the EntireURL look like 'http://qadomain1.com/Baseline_Build/area/PageName.aspx' which is ok. But in this case, as I understand the CompareMode should be changed to 'BaseURL'?
And the project BaseURL should be limited to 'http://qadomain1.com/'.
Will this work, if I would create a test list, and in test list settings the BaseURL will be 'http://qadomain2.com/Some_Build' ?
Will the test list BaseURL used instead page element BaseURL when the search for the element will be performed on a completely different server?
Thanks in advance.