Skip to main content

Maintain Locators - Selenium Automation Projects

Automating your application is easy on the way to reach your goal in your selenium tests. But give me answers to below questions or answer yourself.
1. Is it readable?
2. Is it easily modifiable while your script grows?
3. Is it easily identifiable?
4. Can anybody edit your locator? etc....
For all these questions, your answer might be a big NO.To solve this prob, here is the approach.

Maintaining Locators:
Always maintain your locators in a single file which is supported by your script driven language like below.
Java   ---  you have .properties file
Python  --- Config parser or dictionaries
C#  --- .config file
Ruby  --- YAML file
So maintain your locators in a single file and edit whenever you want like QTP Object Repository.
Your file should contain your locators like this.

Ex: file
# Here registration is my page and firstname is element on registration page.
# Just for ID or Name
registration.submit=css=form submit

Accessing Locators in Scripts:
Just create a variable of type properties in globally in your class.
public static Properties locators = new Properties();
Then, load your locators file to JVM.
InputStream locatorStream = ClassName.class.getResourceAsStream("/");
Here ClassName refers your class name.
Thats all. Use it in your scripts like 

The above spoken is an approach. Also you can start with another approach.
1. Design Page Objects representing your pages or part of pages
2. Use your locators directly inside you page object classes you design.
3. Now your script contains only your methods your page object classes providing.
Now maintaining your locators is easy while automation project grows. Just find you page object class for a specific page and change your locators/methods as you want. No need to care about your scripts.
Refer this post: PageObjects

Hope this helps you start your own framework.


Popular posts from this blog

Change IE Browser ZOOM settings

Lot of UI automation testers could have faced this problem as we could change the zoom settings while operating manually for our convenience and forgot to reset to 100%.
But our QTP and some other related tools would operate the browser perfectly if browser zoom is 100%. So wee need to change the zoom before start to run the scripts. Its better to have a code snippet in our framework to change this zoom setting right?
Here we go...

1. We can simply change the Registry values before Invoking IE
Function ChangeRegistry Dim objShell Set objShell = CreateObject("WScript.Shell")  objShell.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Zoom\ZoomFactor", "100000", "REG_DWORD" Set objShell = Nothing EndFunction This option is very useful. But in real time, lot of customers could have restricted write access to windows registry. So we can try other options.

2. Use IE COM object and Change Settings
Function ChangeIEZoom Dim intZoomLevel, objIE  intZoo…

QTP - Object Identification - Prerequesties

While starting a new project or proof of concept or after new QTP installation, we would face the issue in identifying objects as QTP built objects like WinList, WebEdit, etc.; instead everything will be identified as WinObject.

Here are some steps to ensure you did the environment setup RIGHT before start automating.
Did you enabled required Add-ins only while launchingDid you selected "Record >> Record and Run Settings" - This should be based on what type of application you are working with
Windows app - Windows >> Record and run test on any windows applications. Web app - Web >> Record and run test on any open browser.
Did you tried to launch UFT/QTP and then AUT.If its web, ensure browser zoom level set to 100%Try disabling the protected mode in IE for web.Launch UFT and AUT using RUN AS ADMINISTRATORAlso see the Object Identification Methods if you are interested.

Run JavaScript from QTP

Yeah, You can run your pure JavaScript from QTP using RunScript method. Lot of times, we are in need of firing events or simulating actions on web page which is not supported by QTP. At that time, you can use your direct DOM methods and directly execute your script on the web page from QTP like,
Dim MyPage, SearchBox Set MyPage = Browser("title:=Google").Page("title:=Google") Set SearchBox = MyPage.RunScript("document.getElementsByName('q')(0);") SearchBox.Value="testing"
'if objects available in frames, Set SearchBox = MyPage.RunScript("document.frames(4).document.getElementsByName('q')(0);")
Set objFrame = Browser("title:=Google").Page("title:=Google").Frame("title:=something")
objFrame.RunScript("document.getElementsByName('q')(0);") Also, you can execute by obtaining actual browser window object if you have IE app like, Dim IEApp Set IEApp = CreateObject("Internet…