Skip to main content

How selenium recorder compares with other tools?

I had chance to work on QTP and to sneak in to Test Complete in my Organization.
I am bit depressed as to how irrationally QTP and Test Complete record web application and how much script one should tweak manually to make it compact. Let me cite example of Google Search for this. A selenium test for Google Search would be like this -


selenium.open("http://www.google.com/");
selenium.type("q", "I love My Company");
selenium.click("btnG");



This certainly gives impression of app being opened, some thing being typed (though "q" might not be very clear here) and some button being clicked (again "bthG" is not very clear here)

Same recorded test in QTP be as following -


Browser("Google").Page("Google").WebEdit("q").Set "I Love My Company"
Browser("Google").Page("Google").WebButton("google search").Click

Google

With Browser and Page objects embedded every where it looks over kill me (Though this can be minimized through manual tweaking)

Now comes the Test Complete -



Sub Test1
Dim page
Dim cell
Dim textbox
Set page = Aliases.firefox.pageGoogle1
Call page.ToURL("http://www.google.com/")
Set cell = page.formF.table.cell
Set textbox = cell.textboxQ
Call textbox.Keys("I Love My Company")
cell.submitbuttonBtng.Click
End Sub



First of all this is too much of script for simple search in Google and would intimidate a novice test automation engineer. More over Google search text box and search button are associated with page > form > table and cell. I tweaked and associated text box and button with page and got through. This also required me to change NameMapping

So As far as script generated through recorder is concerned selenium looks better to me,
Any opinion on this ?

p.s. It took me half an hour to records Google test using Test Complete. Tool looks heavy on memory usage.

Comments

  1. You sound like an agile programmer and that is a good thing. For an agile programmer the code should be self-documenting.

    Selenium would appeal to an agile programmer because it is clean and easy to read. If I show your Selenium, QTP and Test Complete examples to my wife (absolutely no programming knowledge) she would be able to tell me what the Selenium code does. The rest would be gibberish to her.

    I would totally agree with your conclusion.

    ReplyDelete

Post a Comment

No spam only genuine comments :)

Popular posts from this blog

Appium and android mobile app automation

Next appium and Android mobile app automation video tutoria l is live. If you are new to appium then please check - appium-tutorial This video tutorial covers - Start vysor (Just for this session and not mobile automation :)) Start appium and start appium inspector Desired Capabilities platformName - Android deviceName - L2N0219828001013 (as seen on "adb devices") Saved Capability Sets Start Session Scan app elements using appium inspector Get appPackage and appActivity using "APK info" app Install "APK info" app and open app whose appPackage and appActivity are required i.e. calculator Check top section of app icon com.android.calculator2 is app package com.android.calculator2.Calculator is app activity testng.xml file settings for running Android app tests Test details com.seleniumtests.tests.mobile.AndroidAppTest and CalculatorScreen class View beautiful STF test report  

Return only first or last element from webelements collection

Note: If you are new to java and selenium then start with selenium java training videos .     We often come across situation when there are multiple elements on a page and we probably like to exercise only a few of them using selenium webdriver. May be just first and last element. For example on a search result page we may like to click on only first and last link and not all. This is when Iterables API comes handy. (By the way I am assuming that you have already completed watching selenium training videos :)). Once we have collection of web element then we can use Iterables to get only first or last element as following - Consider that we fetch collection of element as - List< WebElement > webElements = getDriver().findElements(By. id ( "htmlID" ));   Now we can get the first web element from this collection as -  WebElement firstElement = Iterables. getFirst (webElements,  getDriver().findElement(By. id ( "defaultElement" )));   Herein second

Using chrome console to test xPath and css selectors

Note: If you are new to java and selenium then start with selenium java training videos .       Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously wri