I am testing a Software using Qf test the Components are dynamic and has no ID, we tried xpath but the Html tree is complicated. Do you have any ideas how to handle that in Qf test with step explanation???
QF test Dynamic Components whithout IDs
603 Views Asked by B.geziry At
1
There are 1 best solutions below
Related Questions in WEB-FRONTEND
- php Variable name must change in for loop
- register_shutdown_function is not getting called
- Query returning zero rows despite entries existing
- Retrieving *number* pages by page id
- Automatically closing tags in form input?
- How to resize images with PHP PARSE SDK
- how to send email from localhost using codeigniter?
- Mariadb max Error while sending QUERY packet PID
- Multiusers login redirect different page in php
- Imaginary folder when I use "DirectoryIterator" in PHP?
Related Questions in QF-TEST
- php Variable name must change in for loop
- register_shutdown_function is not getting called
- Query returning zero rows despite entries existing
- Retrieving *number* pages by page id
- Automatically closing tags in form input?
- How to resize images with PHP PARSE SDK
- how to send email from localhost using codeigniter?
- Mariadb max Error while sending QUERY packet PID
- Multiusers login redirect different page in php
- Imaginary folder when I use "DirectoryIterator" in PHP?
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
The easiest way to do this, if you only have one or few of such dynamic components:
You are now having two suites. Both of your suites are basically looking like this:
It is important to notice, that the QF-Test component ID of your mouse click has the same id/string as the QF-Test ID of the component node below your "Window and components" node. This is because the "Window and components" node is representing some kind of database. Whenever a mouse click/text replay/check/... node gets replayed QF-Test will search for a component node (below the the "Window and components" node) with this id/string. QF-Test will then try to find the component in your GUI based on the recognition information that is provided in this component node AND the parents of this component node. Interesting details about this recognition algorithm are described in the handbook. The most important chapters are:
So by having a look at the differences between multiple (two) recordings it is often possible to come up with a component hierarchy that is describing your wanted components. The most easiest way to do so in general is to delete all intermediate parent nodes. So
is becoming
Then compare all Features, Extra Features and other attributes of this component node and the Window node in the two suites. Delete those that are not the same in both suites, except for the "QF-Test ID" attribute. Here choose a speaking name for your component. Now you can use the chosen speaking name in the "QF-Test component attribute" of mouse clicks etc. nodes.
Normally this is it. However it can happen that the occurring component description is now matching too many components in your application to test. In this case, Extra Features etc. need to get added again until the recognition becomes as stable as wanted.
In case you have multiple of such components, the recording of QF-Test can be adapted to your needs via Resolver scripts. With resolver scripts it is possible to modify the recording, such that certain Window/component nodes will not be recorded, or that certain Features/Extra features will be recorded differently and so on.