A UI map is a mechanism that stores all the locators for a AUT in one place for easy modification when identifiers or paths to UI elements change in the AUT. The test script then uses the UI Map for locating the elements to be tested. Basically, a UI map is a repository of test script objects that correspond to UI elements of the application being tested.
What makes a UI map helpful?
Its primary purpose for making test script management much easier. When a locator needs to be edited, there is a central location for easily finding that object, rather than having to search through test script code. Also, it allows changing the Identifier in a single place, rather than having to make the change in multiple places within a test script, or for that matter, in multiple test scripts.
To summarize, a UI map has two significant advantages.
What makes a UI map helpful?
Its primary purpose for making test script management much easier. When a locator needs to be edited, there is a central location for easily finding that object, rather than having to search through test script code. Also, it allows changing the Identifier in a single place, rather than having to make the change in multiple places within a test script, or for that matter, in multiple test scripts.
To summarize, a UI map has two significant advantages.
- Using a centralized location for UI objects instead of having them scattered throughout the script. This makes script maintenance more efficient.
- Cryptic HTML Identifiers and names can be given more human-readable names improving the readability of test scripts.
There are various ways a UI Map can be implemented. Following are the few famous ways :
- Properties File In Java
- XML File
- Excel Sheet
- Java Class File(stores public String variables each variable storing a locator value)
No comments:
Post a Comment