This is a migrated thread and some comments may be shown as answers.

False Negative for a Dynamic Label

3 Answers 97 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Jonathan
Top achievements
Rank 1
Jonathan asked on 19 Oct 2010, 02:50 PM
When I attempt to test for the invisibility for a dynamic label I receive a false negative. After attempting to hard code as well as use the built in wizard I get the same results. I have attached a document outlining the issue.

3 Answers, 1 is accepted

Sort by
0
Cody
Telerik team
answered on 25 Oct 2010, 09:32 PM
Hi Jonathan,

I apologize it has taken so long to reply to your problem. This may be a case where instead of making the element truly invisible it is being moved off screen. Can you run the test, export the test results and attach the .zip file for us to study please? This will include the DOM at the time of failure that I can study to try and discover why it's not working as expected. I will also need a copy of your test (the .aii and matching .resx and .cs file).

Best wishes,
Cody
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
0
Jonathan
Top achievements
Rank 1
answered on 25 Oct 2010, 09:54 PM
I have enclosed a zip copy of the project. Please let me know if there is any other items that you may need. I did get it to pass the step by changing to verifying the existence of the element.
0
Cody
Telerik team
answered on 25 Oct 2010, 11:42 PM
Hello Jonathan,

Thank you for sending a test I can run. I see what's happening now. It is true step 36 in the test removes the error message about the phone number. It actually does it by removing the element all together. But it's happening via an Ajax Postback which is updating the DOM invisibly to us in the background. Your coded step 27 is using a cached copy of the DOM which has gone stale due to the postback that just happened in step 36. The cached copy shows the element still present and still visible.

I see you also have a step 38, wait for the error message element to no longer exist. This is the correct action in this specific instance. Step 36 actually causes the element to be removed from the DOM and waiting for it to Not Exist is exactly the right test to make here. You do not need the coded step 37 at all. It is safe to delete it.

Kind regards,
Cody
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Tags
General Discussions
Asked by
Jonathan
Top achievements
Rank 1
Answers by
Cody
Telerik team
Jonathan
Top achievements
Rank 1
Share this question
or