Verify or Wait for element to ExistNot do not refer the element from the repository when converted to code

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Won't Fix

Last Updated: 04 Apr 2018 08:32 by ADMIN

ADMIN

Elena

Created on: 09 Nov 2017 13:24

Type: Feature Request

Verify or Wait for element to ExistNot do not refer the element from the repository when converted to code

Steps to reproduce: 

1. Create a sample project and add the following steps: 

- Verify element Exists

- Verify element ExistsNot

- Wait element Exists

- Wait element ExistsNot

2. Convert these to code and double check that the ExistsNot steps refer to an element with the current find expression. In contrary the Exists steps refer the element from the Pages file directly. 

That way editing the find expression of the element will be updated and referred in the Exists steps. But the ExistsNot steps in code should be manually updated. 

Expected: The elements in all converted steps to be referred from the elements' repository.

1 comment

ADMIN

Ivaylo

Posted on: 04 Apr 2018 08:32

Hello Elo,

Thank you for your feedback. I understand your concerns, however we will not be fixing this as this is done by design.
Since we are calling Wait.ForExist internally in Pages you cannot invert the condition (using Wait.ForExistNot) that is why when you have wait for exists step you can use Pages.Element.Wait.ForExists while in the not exist you have to use html find expression. 
Unfortunately as you already noticed the find expression of the element should be updated manually if changed.

Thank you for your understanding regarding this matter.
Best Regards,
Ivaylo