I have developed my testcases in one environment called ABC. Now my company has created different environment. But in diff environment elements are going to be same. So when I use same step for diff environment only one or 2 step is executiong others are not. Can you help me in this case?
I have attached a file .
example: i want to select manager,I have to go through same step as in other url.
1) in branch element this how"Manager" is showing
2) in trunk element is "Manager" is same
So what should I write that works in both url.
Thank you.
I have attached a file .
example: i want to select manager,I have to go through same step as in other url.
1) in branch element this how"Manager" is showing
2) in trunk element is "Manager" is same
So what should I write that works in both url.
Thank you.
1 Answer, 1 is accepted
0
Hello Darshana,
Thank you for your interest in Test Studio.
For the example you mentioned and attached images for, although these two environments are nearly identical and our workflow to target the intended element for this scenario is ultimately the same button (eg. Create -> Investment Management -> Manager), even minor differences on the page may force us to make small adjustments to our test script. For example, the depicted difference between the number of menu options would force us to avoid any filters for index in our find logic (eg. TagIndex) when searching for 'Investment Management'. Instead we want to make sure to find the element by a unique id or its TextContent. Unfortunately without seeing a copy of your test or a step failure detail (double-click red X next to failing step -> choose Export -> attach created ZIP archive) it is difficult to pinpoint the exact issue, please provide those pieces of information for further investigation on my part.
In a more general sense, running tests against multiple environments is described here in our documentation. If any part of your application deals with frame's, you will need to follow the bottom sections ('FrameInfo BaseURL' OR 'UsesBaseUrlHost) for elements contained within frames to run across multiple environments.
I look forward to hearing back from you.
Regards,
Mario
Telerik
Thank you for your interest in Test Studio.
For the example you mentioned and attached images for, although these two environments are nearly identical and our workflow to target the intended element for this scenario is ultimately the same button (eg. Create -> Investment Management -> Manager), even minor differences on the page may force us to make small adjustments to our test script. For example, the depicted difference between the number of menu options would force us to avoid any filters for index in our find logic (eg. TagIndex) when searching for 'Investment Management'. Instead we want to make sure to find the element by a unique id or its TextContent. Unfortunately without seeing a copy of your test or a step failure detail (double-click red X next to failing step -> choose Export -> attach created ZIP archive) it is difficult to pinpoint the exact issue, please provide those pieces of information for further investigation on my part.
In a more general sense, running tests against multiple environments is described here in our documentation. If any part of your application deals with frame's, you will need to follow the bottom sections ('FrameInfo BaseURL' OR 'UsesBaseUrlHost) for elements contained within frames to run across multiple environments.
I look forward to hearing back from you.
Regards,
Mario
Telerik