Forum Discussion
Hi,
> they won't name a specific element listing
Slightly extreme, but nevertheless: one will not get either good codebase or test code if relevant efforts were not invested into architecture.
To sum up (assuming that my understanding of your question is correct): you need to identify in reliable and stable manner web elements your test code interacts with. If you are not supported by your developers (i.e. web elements do not have unique and stable identifiers for whatever reason) then you are on your own to find out a way to find those elements. This may be search by element's text, relative search (e.g. all DIVs two level down from current element), OCR, some heuristic (e.g. web element that is next to the right from the current one), etc. Actual implementation depends on your tested application and to provide a good enough suggestion one must have a possibility to investigate your application in the Object Browser.
AlexKaras wrote:
Hi,
> they won't name a specific element listing
Slightly extreme, but nevertheless: one will not get either good codebase or test code if relevant efforts were not invested into architecture.
AlexKaras Totally agree here.
- Largent8034 years agoContributor
My developers do support me. The issue is that these elements are dynamic in nature I could have a item with one of these elements at 12pm and by 3pm that element could will change to another individual or department. So the names and departments have to be very dynamic when they are setup.
Also the product will be merging with another website which we have which similar so everything has to be dynamic this includes individuals who things are assigned to as well as departments that it is going to.
Related Content
- 6 years ago
- 7 years ago
- 4 years ago
Recent Discussions
- 4 days ago