July 23, 2018

Sample java program for PhantomJS

PhantomJs Driver Executable

Download PhantomJs driver here

Sample Java Program:

POM.xml

January 19, 2018

Writing Your First Selenium Test Script

Fundamentally, Selenium works with two pieces of information — the element on a page you want to interact with and what you want to do with it. This one-two punch will be repeated over and over until you achieve the outcome you want in your application, at which point you will perform an assertion to confirm that the result is what you intended.

Let’s take logging into a website as an example. With Selenium you would:

1. Visit the login page of a site
2. Find the login form’s username field and input the username
3. Find the login form’s password field and input the password
4. Find the submit button and click it

Selenium is able to find and interact with elements on a page by way of various “locator strategies”. The list includes (sorted alphabetically):

• Class
• CSS Selector
• ID
• Link Text
• Name
• Partial Link Text
• Tag Name
• XPath

While each serves a purpose, you only need to know a few to start writing effective tests.

How To Find Locators

The simplest way to find locators is to inspect the elements on a page. The best way to do this is from within your web browser. Fortunately, popular browsers come pre-loaded with development tools that make this easy to accomplish.

When viewing the page, right-click on the element you want to interact with and click Inspect Element. This will bring up a small window with all of the markups for the page but zoomed into your highlighted selection. From here you can see if there are unique or descriptive attributes you can work with to write a locator.

How To Find Quality Elements

You want to find an element that is unique, descriptive, and unlikely to change.

Ripe candidates for this are id and class attributes. Whereas copy (e.g., text, or the text of a link) is less ideal since it is more apt to change. This may not hold true for when you make assertions, but it’s a good goal to strive for.

If the elements you are attempting to work with don’t have unique id or class attributes directly on them, look at the element that houses them (a.k.a. the parent element). Often-times the parent element has a unique element that you can use to start with and drill down to the child or descendent element you want to use.

When you can’t find any unique elements, have a conversation with your development team letting them know what you are trying to accomplish. It’s generally a trivial thing for them to add helpful, semantic markup to make the application more testable. This is especially true when they know the use case you’re trying to automate. The alternative is for you to muddle through it in a lengthy, painful process which will probably yield working test code (but it will be brittle and hard to maintain test code).

Once you’ve identified the target elements for your test, you need to craft a locator using one of Selenium‘s strategies. Let’s step through an example of this as we write our first test.

An Example

Part 1: Find The Elements And Write The Test

Here’s the markup for a standard login form (pulled from the login example on the-internet).

<form name="login" id="login" action="/authenticate" method="post">
   
<div class="row">
    
<div class="large-6 small-12 columns">
      <label for="username">Username</label>
      <input type="text" name="username" id="username">
    </div>

  </div>

  
<div class="row">
    
<div class="large-6 small-12 columns">
      <label for="password">Password</label>
      <input type="password" name="password" id="password">
    </div>

  </div>

    <button class="radius" type="submit"><i class="icon-2x icon-signin"> Login</i></button>
</form>

Note the unique elements on the form. The username input field has a unique id, as does the password input field. The submit button doesn’t, but it’s the only button on the page, so we can easily find it and click it.

Part 2: Figure Out What To Assert

Here is the markup that renders on the page after logging in.

<div class="row">
  
<div id="flash-messages" class="large-12 columns">
    
<div data-alert="" id="flash" class="flash success">
      You logged into a secure area!
      <a href="#" class="close">x</a>
    </div>

  </div>

</div>



<div id="content" class="large-12 columns">
  
<div class="example">
    
<h2><i class="icon-lock"></i> Secure Area</h2>

    
<h4 class="subheader">Welcome to the Secure Area. When you are done click logout below.</h4>

    <a class="button secondary radius" href="/logout"><i class="icon-2x icon-signout"> Logout</i></a>
  </div>

</div>

There are a couple of elements we can use for our assertions in this markup. There’s the flash message class (most appealing), the logout button (appealing), or the copy from the h2 or the flash message (least appealing).

Since the flash message class name is descriptive, denotes a successful login, and is less likely to change than the copy, let’s go with that.

class="flash success"

When we try to access an element like this (e.g., with a multi-worded class) we will need to use a CSS selector or an XPath.

NOTE: Both CSS selectors and XPath work well, but the examples throughout this course will focus on how to use CSS selectors.

A Quick Primer on CSS Selectors

In web design, CSS (Cascading Style Sheets) are used to apply styles to the markup (HTML) on a page. CSS is able to do this by declaring which bits of the markup it wants to alter through the use of selectors. Selenium operates in a similar manner but instead of changing the style of elements, it interacts with them by clicking, getting values, typing, sending keys, etc.

CSS selectors are a pretty straightforward and handy way to write locators, especially for hard to reach elements.

For right now, here’s what you need to know. In CSS, class names start with a dot (.). For classes with multiple words, put a dot in front of each word, and remove the spaces (e.g., .flash.success for class='flash success').

For a good resource on CSS Selectors, I encourage you to check out Sauce Labs’ write up on them.

Part 3: Write The Assertion And Verify It
Now that we have our locator, let’s add an assertion that uses it.

Sample 1

 ' Set the Test Object
        Set tstInstance = TestList(i)
        tstInstance.Status = "No Run" 
        tstInstance.Post 
         'Create a run of the test instance 
        'runName = testName
        Set RunF = tstInstance.RunFactory 
        Set theRun = RunF.AddItem(Null) 
        theRun.Status = testStatus
        theRun.Name = testName
        theRun.Post 
         'Get the design step created above for the test 
         ' to be associated with this test run 
        theRun.CopyDesignSteps 
        theRun.Post 
         'Add the steps to run and fail them 
        Set runStepF = theRun.StepFactory 
        Set lst = runStepF.NewList("") 
        For Each Item In lst 
            Set runStep2 = Item 
            runStep2.Status = testStatus 
            runStep2.Post 
        Next 

sample 2

Sub ConnectToQualityCenter()


'-----------------------------------------------------Connect to Quality Center --------------------------------------------------------


MsgBox "Starting Connectinon"
Dim qcURL As String
Dim qcID As String
Dim qcPWD As String
Dim qcDomain As String
Dim qcProject As String
Dim tdConnection As Object
Dim TestSetFact, tsTreeMgr, tSetFolder, TestSetsList, theTestSet
Dim TestSetIdentifier, TSTestFact, TestSetTestsList, testInstanceF, aFilter
Dim lst, tstInstance

On Error GoTo err
   qcURL = "Server Details/qcbin"
   qcID = "UserName"
   qcPWD = "Password"
   qcDomain = ""
   qcProject = ""

'Display a message in Status bar
 Application.StatusBar = "Connecting to Quality Center.. Wait..."
'Create a Connection object to connect to Quality Center
  Set tdConnection = CreateObject("TDApiOle80.TDConnection")
'Initialise the Quality center connection
   tdConnection.InitConnectionEx qcURL
'Authenticating with username and password
   tdConnection.Login qcID, qcPWD
'connecting to the domain and project
   tdConnection.Connect qcDomain, qcProject
'On successfull login display message in Status bar
  Application.StatusBar = "........QC Connection is done Successfully"
  MsgBox "Connection Established"


'---------------------------------------Connection Established --------------------------------------------------------------------------

'
' Get the test set tree manager from the test set factory
'tdconnection is the global TDConnection object.
Set TSetFact = tdConnection.TestSetFactory
Set tsTreeMgr = tdConnection.testsettreemanager
' Get the test set folder passed as an argument to the example code
nPath = Trim("Your Test Set Folder Path")

Set tsFolder = tsTreeMgr.NodeByPath(nPath)
--------------------------------Check if the Path Exists or NOt ---------------------------------------------------------------------
If tsFolder Is Nothing Then  
Msgbox "Error"
End If

' Search for the test set passed as an argument to the example code
Set tsList = tsFolder.FindTestSets("Test Set Name")
----------------------------------Check if the Test Set Exists --------------------------------------------------------------------
If tsList Is Nothing Then
Msgbox "Error"
End If

'---------------------------------------------Check if the TestSetExists or is Duplicated ----------------------------------------------

If tsList.Count > 1 Then
MsgBox "FindTestSets found more than one test set: refine search"
Exit Sub
ElseIf tsList.Count < 1 Then
MsgBox "FindTestSets: test set not found"
Exit Sub
End If

-------------------------------------------Access the Test Cases inside the Test SEt -------------------------------------------------

Set theTestSet = tsList.Item(1)

For Each testsetfound In tsList
Set tsFolder = testsetfound.TestSetFolder
Set tsTestFactory = testsetfound.tsTestFactory
Set tsTestList = tsTestFactory.NewList("")

For Each tsTest In tsTestList
MsgBox tsTest.Name
testrunname = "Test Case name"
If tsTest.Name = "Test case Name" Then

--------------------------------------------Accesss the Run Factory --------------------------------------------------------------------
Set RunFactory = tsTest.RunFactory
Set obj_theRun = RunFactory.AddItem(CStr(testrunname))
obj_theRun.Status = "Passed" '-- Status to be updated
obj_theRun.Post
End If
Next tsTest
Next testsetfound
'

'------------------------------------------------------Disconnect Quality Center -----------------------------------------------------------------

tdConnection.Disconnect
tdConnection.Logout
tdConnection.ReleaseConnection
MsgBox ("Logged Out")

-----------------------------------------Error Function to Display the Error in teh Excel Status Bar ---------------------------------------------

err:
'Display the error message in Status bar
Application.StatusBar = err.Description
 MsgBox "Some Error Pleas see ExcelSheet"


End Sub

December 31, 2017

The First Things You Need To Know

Selenium is really good at a specific set of things. If you know what those are and stick to them then you will be able to easily write reliable, scalable, and maintainable tests that you and your team can trust.

But before we dig in, there are a few things you’ll want to know before you write your first test.

Define a Test Strategy

A great way to increase your chances of automated web testing success is to focus your efforts by mapping out a testing strategy. The best way to do that is to answer four questions:

1. How does your business make money (or generate value for the end-user)?
2. How do your users use your application?
3. What browsers are your users using?
4. What things have broken in the application before?

After answering these, you will have a good understanding of the functionality and browsers that matter most for the application you’re testing. This will help you narrow down your initial efforts to the most important things.

From the answers you should be able to build a prioritized list (or backlog) of critical business functionality, a short list of the browsers to focus on, and include the risky parts of your application to watch out for. This prioritized list will help you make sure you’re on the right track (e.g., focusing on things that matter for the business and its users).

Pick a Programming Language

In order to work well with Selenium, you need to choose a programming language to write your acceptance tests in.

Conventional wisdom will tell you to choose the same language as what the application is written in. That way if you get stuck you can ask the developers on your team for help. But if you’re not proficient in this language (or new to development) then your progress will be slow and you’ll likely end up asking for more developer help than they have time for — hindering your automation efforts and setting you up for failure.

A great way to determine which language to go with is to answer one simple question: Who will own the automated tests?

Also, as you are considering which language to go with, consider what open source frameworks already exist for the languages you’re eyeing. Going with one can save you a lot of time and give you a host of functionality out of the box that you would otherwise have to build and maintain yourself — and it’s FREE.

You can see a list of available open source Selenium frameworks here.

Choosing a programming language for automated testing is not a decision that should be taken lightly. If you’re just starting out (or looking to port your tests) then considering and discussing these things will help position you for long term success.

Installation