Page 1 of 1

Need to find an element from the application I'm testing

PostPosted: Fri Jul 20, 2018 4:42 pm
by KarenW
Hello.

I'm testing an application which creates graphs (like a flowchart).

Which has a start node and an end node in the beginning.

There is a menu through which more nodes can be added on the page and can be connected to existing nodes.

My challenge is if I want to automate this application testing, but how do I find the element locator for the nodes added on the fly.

Thanks

Re: Need to find an element from the application I'm testing

PostPosted: Mon Jul 23, 2018 11:31 am
by eValid
KarenW wrote:Hello.

I'm testing an application which creates graphs (like a flowchart).

Which has a start node and an end node in the beginning.

There is a menu through which more nodes can be added on the page and can be connected to existing nodes.

My challenge is if I want to automate this application testing, but how do I find the element locator for the nodes added on the fly.

Thanks


Thanks for the question KarenW.

You're correct, it is quite tricky to validate a page that changes between when you first make a recording on it and when you want to test it -- after various run-time changes have been made.

The best way to do this is to find some part of the page that can act as an anchor, or "fixed point" for your testing.

The eValid PageMap is the way to do this, as described in this manual page:

http://e-valid.com/Products/Documentati ... p.gui.html

We haven't seen your page, but we would recommend choosing as an anchor some uniquely labeled DOM element that lies above (lower index) the are that is going to changed dynamically.

Save this value for the next step.

Next, you will probably want to search, starting at the saved index value and search for a key feature of your graphic, using the DOM search commands:

http://e-valid.com/Products/Documentati ... dElementEx

The key takeaway idea here is that the part of the page above (lower index) the changed area won't change in structure, but after the dynamic changes have been made you can engineer your test script to only deal with the specifics of your test target.


-- eValid Support