Showing posts with label Software testing. Show all posts
Showing posts with label Software testing. Show all posts

Monday, May 8, 2017

Types of locators in selenium with Simple examples

Locators in selenium are used to locate the web elements in page. Identification of correct expected web element and to perform some action on it will be the expectation in Automation. Selenium IDE is the plugin that will be more helpful to identify the locate the elements in GUI page. We can use that locator value while doing the scripting. Each and every web element are presented in HTML tag with open and End tag will be identified through its attributes.

Different types of locators in selenium are listed below.

  • ID
  • Name
  • Link
  • CSS Selector
  • Xpath
  • DOM


Target Area - IDE

Locating by ID:

Always ID is the attribute present in html tag of the web element will be unique. Some of the web elements will not have the ID attribute.

Syntax :

 id= value of Id of that Specific element

Locating by Name:
Name attribute will be used to identify the element using the name attribute of element.

Syntax :

Name = Value of Name attribute of that specific element


Locating by Link:

It used to identify the hyperlink element in the webpage.

Syntax :

Link = linktext

Locating by CSS Selector:

It is used to identify the web elements using string patterns. When an element doesn’t have usual attributes with unique values such as ID,Name, Class name etc, we can make use of it.
It will be very fast in accessing the web elements comparing to other locators.

Syntax and its CSS types:

  • Tag and ID   ----> css=Tag#id
  •  Tag and class ----> css= Tag.class
  •  Tag and attribute ----> css= tag[attribute = Value]
  • Tag, class, and attribute ----> css=tag.class[attribute = value]
  •  Inner text ---> Tag:contains("text")


When using this strategy, we always prefix the Target box with "css=" as will be shown on the following examples.

Locating by Xpath:

XPath is the language used when locating XML (Extensible Markup Language) nodes. There are two types in Xpath.

Absolute path – Full path
          Relative path – Reference path


Syntax and its Xpath types:

  • Using Single attribute  -//Tag[@attribute = ‘value’] 
  • Using Multiple attribute-//Tag[@attribute1=’value1’] [@attribute2=’value2’]
  • Using Contains method   -//Tag[contains(@attribute,’value’)]
  • Using Starts-with       -//Tag[starts-with(@attribute,’value’)]
  • Using Following         -//Tag[@attribute =’value’]/following::Tag/
  • Using Preceding         -//Tag[@attribute =’value’]/preceding::Tag/
  • Parent                  -//Tag[@attribute ='value']/parent::*---->
  • Child                   -//child::tag
  • Siblings                -//Tag[@attribute =’value’]/preceding-sibling::Tag/
  • Siblings                -//Tag[@attribute =’value’]/following-sibling::Tag/


Document Object Model (DOM)

HTML elements are structured. Selenium IDE is able to use the DOM in accessing page elements.

Syntax for DOM:

  •      document.getElementById("pass")
  •      document.getElementsByName("servClass")[1]
  •      document.forms["home"].elements["userName"]   ----> Only applicable when having forms
  •      document.forms[0].elements[3]



Tuesday, April 25, 2017

Software testing Lifecycle - Simple article

Phases in Software testing life cycle will be listed below. This cycle later phases will get changed based on traditional development life cycle and latest agile methodology or Scrum framework

Requirement Analysis:

This phase deals with analysing the requirements through SRS(System requirement) and BRS(Business requirement) documents. Traditional SDLC like Waterfall, Prototype and spiral will have late testing is due to this that we will cover on principles of testing. Analysing the requirements at later stage and identifying the requirement issues at later stage will cause major impacts to the application in sense of business. Outcome of requirement analysis phase is Strategy document.

Test Strategy Document -  Test Manager – Static Document
1.       Business priorities
2.       Risk and its mitigation
3.       Testing tools
4.       Automation testing needed or not
5.       Process of test execution
6.       Type of testing
7.       Training needed or not


Test Planning:

Test Plan Document - Test Manager/ Test lead – Dynamic document

It will change throughout the testing lifecycle and also it will answers the below questions with planning.

1.      When- When the testing for the feature or module is going to be performed?
2.      What - What are the expectation in the functionality or feature?
3.      Where - Where refers the test environment includes os and browser.
4.       How - How means the approach or type of testing going to be performed for that feature.
5.       Who -Who means the resource person going to execute the specific feature or functionality as per plan.

Test Case Development:

1.       Preparing test cases
2.       Test data Preparation
3.       Automation Framework Selection

Environment Setup:

1.       Test case review - Review the prepared test cases and ensure with the team that the scope is covered in the test case.
2.       Updating of test cases based on the feedback received from the peers.

Test Execution:

1.       Executing the test cases and identifying potential bugs
2.       Assigning bugs to appropriate developers and follow-up for its closure
3.       For Agile, It will happen in parallel cycles in every build

Test Cycle Closure:

1.       Preparing the test report
2.       Sent it to appropriate distribution list daily, weekly or bi weekly manner.


Wednesday, March 15, 2017

Software testing and its objectives

This post mainly covers the basic information about what is testing and the main objectives of the testing team

  What is Testing?
   It is a process of verifying are we developing the right product or not and also validating does the
  Developed product is right or not.

  Software testing = Verification(QA Process) + Validation(QC Process)

 What is Verification?

    It is a process of verifying: Are we developing the right product or not.  This is also known as static testing. It will define the process and also ensure that the team is following the process as expected.

 What is Validation?

    It is a process of validating: Does the developed product is right or not. This is called as dynamic testing. It is termed as real test execution. That may be manual testing or automation testing

 Objectives of Testing:   

  1. To confirm whether the application is developed according to customer requirements or not
  2. Finding defects
  3. To make sure all problems are resolved and close.
  4. Finally testing is helpful to deliver a quality product and risk-free product to the customer