Software Testing Tutorials

QTP Introduction

2013-03-02T19:38:00.003-06:00

Quick Test Professional:

1. Mercury Interactive commercial Product. Now it’s take over by HP.

2. Functionality Testing Tool.

3. Used for Regression Testing.

4. Available in various versions like 6.5, 8.2, 9.0, 9.1, 9.2, 9.5, 10.0 and 11.0.

5. It supports Functional Testing of all popular environments, including Windows,

Web, .Net, Visual Basic, ActiveX, Java, SAP, Siebel, Oracle Applications and

PeopleSoft.

6. It supports 100% dynamic testing.

7. QTP Support for Both window and Web Application

8. QTP run only on windows.

Add ins

Default Add ins

ActiveX
Visual Basic
Web

Available Add ins

Java
.Net
SAP

Quality Center - Basic Introduction

2013-02-28T20:52:00.002-06:00

HP Quality Center is a Test management & Bug tracking tool.

Features of Quality Center:

It is a liscenced tool from HP company.
It offers an organized framework for testing applications.
Quality center is a web based application which provides all the requirements from Software Testing Life Cycle such as

- BRD documentation

- Test case creation

- Test case management

- Test case execution

- Defect tracking

- Report analysis

- Graphic report generation

Quality center provides entire framework related to Software Testing Life cycle
It helps maintain a project database of tests that cover all aspects of application functionality.

Advantages:

Defects can be directly imported from an excel sheet to Quality center tool
Saves lot of time by user friendly framework
Quality center can be integrated with other tools like QTP, HP LoadRunner
Graphs and reports can be generated to analyze the information.

Why to choose Quality Center?

One stop shop for all testing related tasks.
Coherence of different tasks.
Better analysis and management.
Easy to track

Quality Center now modified to Application Life Management Lifecycle[ALM 11] with more features.

Avoid these mistakes in Interview

2013-02-28T17:18:00.002-06:00

1. Don't be Late

2. Dont be blank on unknown questions

3. Not asking questions in return if chance is given to ask

4. Not dressing professionally.

5. Turn off the mobile

6. Dont ask the salary

7. Eye to eye contact

8. Less communication/Interaction

9. Saying "I don't know" with out trying for any question.

10. Not remembering the past projects or past companies worked for.

11. Not having enough Resume copies or passport photo copies

12. Not carrying a pen

13. Dont mention the skill set you are not aware of.

Difference between Test scenario and Test case

2013-02-27T13:34:00.003-06:00

Every one believes that Test scenario and Test case are both one and same.

Test scenario is different from Test case.

Consider below example

If we have requirement to test the "Facebook login"

Here this is a scenario where we can test with some test conditions with multiple probabilities like

Wrong email id and correct password
Correct email id and wrong Password
Wrong email id and wrong password
Correct email id and correct password

Each condition above is called a Test case and the above statement for testing the login of Facebook login is called a Test Scenario.

So, Test scenario consists of multiple test condition which are called as test cases.

Test scenarios will be listed in a Use case document.

Selenium Webdriver Mostly used Commands

2013-02-02T14:58:00.000-06:00

Selenium Webdriver Mostly used Commands:

Get();

Load a new web page in the current browser window.

getCurentURl();

Get a string representing the current URL that the browser is looking at.

getTitle()
The title of the current page

getPageSource()

Get the source of the last loaded page.

Quit();

Quits this driver, closing every associated window.

Close();

Close the current window, quitting the browser if it’s the last window currently open.

Sample code which covers functionality for CheckBoxes:

List<WebElement>rad=driver.findElements(By.xpath(“//input[@type='radio']“));

rad.get(0).click();

System.out.println(rad.size());

driver.findElement(By.xpath(“.//*[@id='info_ataglance_input']/input”)).click();

-->

Identifying Web Elements on Webpages of Application: Selenium

2013-01-29T15:10:00.000-06:00

Identifying Web Elements on Webpages of Application:

As humans we know where to click , where to enter data in the application for Testing. For Automation tool what ever we mention in the Automation programs it will perform those steps.

Identifying the elements in a Webpage is the most challenging part of Automation for any tool.

Different Ways to Identify the Webelements/ Locator techniques:

ID
ClassName
TagName
Xpath
CSS

Application may be designed by any technology like Java, JQuery , .Net

The application will have HTML part for building objects on webpage.

Common Web Elements for any Application:

Text Box
Link
DropDown
TextArea
CheckBox
RadioButton
Frames
Pages
Alerts
PopUp’s

Refer below screenshot for looking html part of the application:

In the above screenshot you can see the various locators & attributes like ID, ClassName, tagName & Input,Select.

Use appropriate locator techniques for identifying web elements for your application

Locator tools for browsers:

Firefox : Firebug
Internet Explorer: IE Developer
Google chrome : Right click on webpage and click on "Inspect element"

Example for finding Xpath :

driver.findElement(By.xpath(“.//*[@id='login_input']”)).type();

-->

Various IT Teams in a project

2013-01-25T19:12:00.000-06:00

This is post is for who are going to start their career in IT field.

Before going to Software Testing we should know about the various teams in a project and their responsibilities.

There are 6 different teams who are involved in complete development of a project and delivering it to client / customers.

Analysis Team - Business Analyst: This team directly contact the customers , manager and client . They collect the data or business requirements related to project and analyze with various domains and projects.
Development Team: Developers are those who give a shape to the project i.e; Graphical user interface. They use various technologies to develop the application depending upon the requirements. Developers play a key role in the project.
QA Team : None of the projects will be successful without Software Testing team. Once the application is built the Testing qualifies the application to meet its business requirements , functionality and non functionality requirements and ensures that the application is defect less.
DBA[Data Base Administration ] : All the data related to application will be stored in Data Base. Any text , data, information , pages, module etc on an application will be stored in Data Base. DBA Team responsibility is to ensure that application is always up and running. DBA team needs to make sure that Data Integrity , Data Consistency is maintained around the environment.
Network Administrators: Data base will be installed on a server and all other involved in a project needs server . Servers act like a containers to hold. Server is a physical computer dedicated to run one or more services to serve the need of users on network. Administrators are even responsible for security of an application.
Support Team [ Customer support ] : Once application is released the end user will use it and may face issues at any time. Support team run the business anytime by receiving the issues from direct users and reporting them to other teams in the project.

Any IT person will face all above teams in any IT project.

-->

Kick-Off Meeting

2012-01-25T09:30:00.000-06:00

Kick of meeting:-

Kick-Off meeting is the firs legal meeting conducted between Project team & Client of that project.
The main purpose of this meeting is to decide and discuss the elements as Schedule, Deadlines, Role of each team member & challenges
or risks which may lead to the expansion of Time estimation etc.

Participants:
1. Client
2. Project Team
3. StakeHolder

Best practise for making Kickoff meeting as success, there should be a prior internal Company meeting where project
manager discuss with Team what needs to be discussed & what Not to be Discussed.

One of the Team member should note all the points and prepare a document prior to the Kickoff meeting to track all the
issues/observations.

Sample KickOff meeting profile documnet:

First program in Selenium Webdriver

2012-01-24T10:33:00.000-06:00

After setting up the necessary environment(Eclipse with required Jar's) with Selenium WebDriver for test case execution.

Pre-requisite:
Basics of Java language is needed for writing a program ( If Java is used ).

Program structure:

Should invoke the application URL
Should execute certain set of actions
Should stop the execution.

-------------------------------------------------------------------------------------------------

import org.openqa.selenium.WebDriver;

import org.testng.Assert;

import org.testng.annotations.Test;

import org.openqa.selenium.By;

import org.openqa.selenium.WebElement;

import org.openqa.selenium.firefox.FirefoxDriver;

import org.openqa.selenium.interactions.Actions;

import org.openqa.selenium.support.FindBy;

public class Google {

public WebDriver driver;

public Google(WebDriver driver) {

this.driver = driver;

}

public Google() {

this.driver = driver;

}

@Test(testName = "homeTest", description = "Create a Master & enable the same", timeOut = 300000, enabled = true, groups = { "homeTest" })

public void gmailLogin() throws InterruptedException {

driver = new FirefoxDriver();

driver.get("http://www.google.com");

Thread.sleep(10);

driver.findElement(By.xpath("//input[@id='lst-ib']")).sendKeys(

"Testing");

}

-------------------------------------------------------------------------------------------------
The above program can be executed in 2 ways.

1. As Java application:
After completion of program , right click on the file and select > Run as > Java application.

2. TestNG:

If TestNG plugin is installed in Eclipse, right click on the file and select>> Run as > TestNG >> Select the test name.

Test Plan - What is all about?

2012-01-23T10:18:00.000-06:00

Definition:
Test Plan is a document which defines the Scope, Test design techniques, test environment, Features Can/Cannot be tested , when to stop testing, Entry & exit criteria etc.

What is the purpose of Test plan?
Defining a Test plan in any application improves the thinking and focuses on all areas of features in an Application.

Test plan are easy to track the set of test cases for any feature in the application. As and when new enhancement happens Test Plans can be updated accordingly.

Creation of Test plan involves in describing the solutions to few questions like

What is the Scope of testing?
What are types of Testing techniques needed?
What is the Test environment should be used?
What is the Test strategy ?
What is Entry & Exit criteria?
What are the features Can/Cannot be tested?
What are the risks involved?
What are the test approaches?

Test Plan template IEEE 829 describes all above.
You can find the IEEE 829 Test plan template here .

Test Case Design Techniques

2012-01-22T09:43:00.001-06:00

The types of Testing techniques fall in to 2 types.

Static:
- This type of testing techniques are applied before any test execution on any Software/Application.
- This is also called as "Non-execution" technique.
- Usually Static testing techniques is done in form of Documents with even source code, HLD/LLD documents, Functional specifications etc.
Dynamic:
- This type of testing technique is applied during the test execution on any Software/Application.

Lets see about Dynamic types of testing techniques.
Dynamic types of testing techniques is again sub-divided in to 3 types.

Structure-Based
Experience-Based
Specification-Based

The three specification based techniques are

Equivalence Class Partitioning
Boundary Value Analysis
Decision Table

1. Equivalence Class Partitioning [ECP]:
Testing cannot be done with all possible input conditions for validating any UI element, feature.

For example if a text box needs to tested whether is accepts from 1-60 characters, here testing is not possible with all numbers between 1 & 60.

So, we can divide the range in to partitions, take one from each possible partition and test that particular text box.

ECP is a specification based Black-box testing technique.
The intent of this technique is to divide the set of input conditions int to equal parts which are equal.
Equivalence Partitions are also known as equivalence classes.
This technique requires to take one input from each and if that not works we assume that any other input from that class does not work.

2. Boundary value analysis[BVA]:

In any application it is most likely common that error occurs at boundaries.

Boundary Value Analysis is also a specification based Black-box testing technique. It is mainly based on testing the boundaries between the classes/partitions.

Boundary value is nothing but a edge value, that may be minimum or maximum value of a range.

Example; If a Text box accepts the range of 1-100 characters. Then the boundary values for this range would be 0,1,100,101.

Invalid | Valid | Invalid
0 |1 100| 101

3. Decision Table:

In addition to the above both techniques which mainly focuses on the UI validation, Decision Table with all possible combinations focuses on the Logical values.

Decision Table is a type of Black-Box testing used to design the test cases with different combination of input's.
In this type of testing technique a table is designed with set of combinations and conditions.

Decision table looks like

Software Testing principles

2011-12-26T00:58:00.000-06:00

There are 7 fundamental principles defined in Software Testing to make an Application with Quality and Bug free.
They are listed below:

Testing shows the presence of Defects
Exhaustive testing is impossible.
Early Testing is Good
Defect clustering
Pesticide paradox
Testing is context dependent
Absence of errors facally

WebDriver -Cross browser testing

2011-12-25T00:17:00.000-06:00

WebDriver has 4 API's for executing the same scripts across multiple browser's, They are

FireFox Driver
Chrome Driver
IExplorer Driver
HTMLunit Driver

Following is the code for executing the scripts

public Config() {
if (browser.equalsIgnoreCase("ie"))
driver = new InternetExplorerDriver();
else if (browser.equalsIgnoreCase("firefox"))
driver = new FirefoxDriver();
else if (browser.equalsIgnoreCase("chrome"))
driver = new ChromeDriver();
else if (browser.equalsIgnoreCase("htmlunit"))
{
driver = new HtmlUnitDriver(true);
}

If you pass the browser as parameter through any property file, then you have to replace the browser with required browser at the time of execution

Sample Test case - UI component

2011-12-11T01:45:00.001-06:00

Test case Examples
Scenario: Text box accepts 60 chars with alphanumerics only.

Test Cases should be atomic in nature and should cover even small possibility for any scenario.
Positive:
1. Verify text box accepts chars <60
2. Verify text box accepts chars = 60
3. Verify text box accepts 59 chars(BVA validation)
4. Verify text box accepts numerics
5. Verify text box accepts alphabets
6. Verify text box accepts mixture of alphabets and numerics
7. Verify text box accepts Upper case letters
8. Verify text box accepts lower case letters
9. Verify text box accepts mixture of Upper case & Lower case letters
10. Verify text box accepts the mixture of Uppercase letters and numerics.
11. Verify text box accepts the mixture of Lowercase letters and numerics.
12. Verify text box accepts the mixture of Lowercase letters, Uppercase and numerics.

Negative test cases:

1. Verify text box do not accept Special chars
2. Verify text box do not accept spaces
3. Verify text bx do not accept Tab spaces

Note: There may be more possibilities for the above scenario.

WebDriver API's

2011-11-21T10:43:00.001-06:00

WebDriver:

WebDriver is a API used for Automation testing.It has many advantageous features which helps in interacting with the different browsers and also the applications.
It is not fixed with any framework, it can be integrated with any framework.
Using Webdriver a new framework also can be created.
It has number of libraries which supports many kinds of Operations/Actions on web browser.

WebDriver consist of 4 drivers, they are listed below:

Html Unit driver:
This is the lightweight implementation of Webdriver. is is dependent on purely HtmlUnit.
This is a java based implementation without any GUI.
Firefox Driver:
This emulates a firefox browser. This will uses all the necessary bindings required for the Firefox.
IExplorer:
Similar to Firefox, Iexplorer also gets emulated by using this drivers. This is controlled by a .dll.
Chrome driver:
Chorme driver works with Chrome through the chromedriver binary.
It is slower than HtmlUnit webdriver.
We need to have both Chrome driver and chrome version installed.

Importance of Xpath in Automation for identifying web elemnts

2011-11-02T11:31:00.003-05:00

Importance of Xpath:

Definition:
Xpath is known as the navigation through the html sytax of a webpage to identify a particular element

Identifying WebElemnts:
Any webelement in an application will be assinged with an identifier.
The web elements will have attributes as well as the identifiers listed below
1. ID
2. Name
3. Class

With the above identifiers elements can be identified and can be automated to perform certain set of actions

Reasons to go with Xpath:

1. Some complex applications like AJAX, GWT willdynamically create some identities for the web elements where the
identification becomes difficulty during the automation of an application.

2. In certain scenarios there may be situations where different web elements have same Name and ID even.
where it becomes difficult for any automation tool to perform the actions given.

In above scenarios the alternate solution is "Xpath"

*Xpath is the way of identifying the web elements uniquely.*

Approaches for Xapth:

There are two ways of defining Xpath for web elements, they are listed below
1. Dependency:
Defining the Xapth by just giving the navigation through the html path to the web elements.

Ex: html/body/table/td[2]/tr[4]

The above appoach is good only if there are no new addition of features in the application, but if any new
features added then the xpath fails here.

2. Non-Dependency/Unique :

Defining the Xapth uniquely which works even if any new web elements added to the application anytime

Ex: //div[text()='Ok']

Some commonly used used commands for writing Xpath for webelemnts:
1. // - Selects nodes in the document from the current node that match the selection no matter where they are
2. / - Selects from the root node
3. * - Matches any element node
4. .. - Selects the parent of the current node
5.@ - Selects attributes

Tools used for finding Xpath for web elements:

* Firebug(Add-on for Mozilla browser)
* IEdeveloper(Addon for IE explorer)
* Xpather(Add-on for Mozilla browser)
* XFinder(Add-on for Mozilla browser)

Note:
Reference for learning Xpath :http://www.w3schools.com/xpath/xpath_intro.asp

Performance Testing Template

2011-10-31T06:24:00.000-05:00

The Performance testing is performed against any application to test the response time on performing any actions on the application.

Any application should be stable according to the standards defined in the W3 standards

TestCase Id#	Transaction Time	Expected Response	Actual Response Time	Result
1	Module 1	10 Seconds	8 Seconds	PASS
2	Module 2	2 Seconds	5 Seconds	FAIL
3	Module 3	5 seconds	5 Seconds	PASS
4	Module 4	5 seconds	4 Seconds	PASS
5	Module 5	5 seconds	3 Seconds	PASS

QTP Short Cuts(Keys)

2011-10-30T06:34:00.002-05:00

Sample Load Testing Template

2011-10-30T06:14:00.000-05:00

The Load testing is performed in terms of users. The number of users is increased in steps for measuring the load against the application

Below is the sample template for the Load testing

Test Case Id#	Load Applied	Result	Contents
1	100 users	Pass	P1, P2, P3
2	200 Users	Pass	Login Module
3	300 Users	Fail	List Pages
4	400 Users	Pass	Form
5	500 Users	Pass	Navigations

Selenium Vs WebDriver

2011-10-29T06:51:00.000-05:00

Selenium Vs WebDriver:

Webdriver provides the alternate API's which are not supported by Selenium RC also.
It is advantageous or next version for Selenium RC.
It uses different framework underlyng it from the way Selenium Javascript uses Selenium core.

Webdriver works with the browsers directly rather than through the proxy as the Selenium RC does.

Webdriver doesnot need any server running for running the automation scripts.

Webdriver also works and interacts with different browsers like IE, FireFox etc..

WebDriver:
1. It directly works with the browsers.
2. It has simple API's to work with.
3. It has a interesting feature of Headless execution against application with HtmlUnit drivers.
4. It works with java.
5 It responds faster than the Selenium RC

Selenium:
1. It does not directly interact with the browsers instead creates a proxy.
2. It has support for limited browser version.
3. It supports various scripting languages.

TestNG Annotations - Basic usage

2011-10-26T08:48:00.000-05:00

TestNG is a framework which is invented to cover all tests such as UnitTest, Integration tests, End-End and functional tests.

TestNG is very advantageous framework which makes our coding practices more effective and easy to handle and maintain.

TestNG Annotations:
Few of the annotations used from TestNG are listed below

@BeforeTest
@AfterMethod
@BeforeClass
@Test
@AfterTest

1. @BeforeTest :

Executes the particular code mentioned before the code

---------------------------------------------------------

Ex: @BeforeTest{alwaysRun=True)

setup();

---------------------------------------------------------

2. @AfterMethod:

Executes the particular code after each method where the command is placed

---------------------------------------------------------
Ex: @AfterMethod
tearDown();
---------------------------------------------------------

3. @BeforeClass:

Executes the code after the whole class is executed.
---------------------------------------------------------
Ex: @BeforeClass
login();
---------------------------------------------------------

4.@Test:
Executes the code and can be used to test as unit tests
---------------------------------------------------------
Ex: @Test
login.Gmail();
---------------------------------------------------------

Related Posts:
TestNG

Selenium RC examples

2011-10-24T09:17:00.000-05:00

For running our tests against the browsers we have to code in any language like Java, Python, Perl etc..
The programming largely used is Java.

Eclipse is good IDE or editor for writing and maintaining the scripts written in Java.

Java developers use this editor for coding the applications.
Hence this editor can be used for both developing and automation process.

We have create a new project in Eclipse and add necessary jars.

Now open a new class file and import the required packages.

Below is the sample program for testing the google home page

------------------------------------------------------------------------------------------------------------

import com.thoughtworks.selenium.Selenium;
import com.thoughtworks.selenium.DefaultSelenium;

public class GoogleTesting {

/**
* @param args
*/
public static void main(String[] args) {

Selenium selenium = new DefaultSelenium("localhost", 4444, "*firefox",
"http://www.google.com");
selenium.start();
selenium.open("/");
selenium.stop();

}

}

----------------------------------------------------------------------------------------------------------

Selenium RC Server Start and Stop process

2011-10-23T09:00:00.002-05:00

Selenium RC

Selenium RC is the another flavor of Selenium . Selenium RC allows us to run the tests remotely.

Selenium is a tool which accepts only for automating the Web applications.

Through Selenium RC we can test the application using any programming language like Java, Python, Perl etc..

Selenium RC comes in two types Selenium server and Selenium client drivers for Java, Python etc.

You can find Selenium server here :

Server

The client drivers for different languages here.

Java , Python

Selenium server has the capability of manipulating the supported version of browsers and acts like the client configured proxy between website and browser, which in-turn allows to run Javascript against any application or site.

Using Selenium RC:

After downloading the required jars for server and language client drivers

Open command prompt and type as shown below

Start command:

java -jar selenium-server.jar

On typing the above command and pressing enter it will start the server automatically.

Stop command:

Ctrl+c

Bug Tracking tools : Jira Vs BugZilla

2011-10-19T12:04:00.001-05:00

1. Available version:

Jira is a open source tool with minimum features and as well as paid tool with lots of good

features.

BugZilla is a open source tool.

2. Invention:

Jira is a Atlassian Software Systems product

BugZilla is a product form Mozilla foundation

3. Features:

Jira is used for tracking Bugs, tasks, Projects etc..

BugZilla is only used for Bug Tracking

4. Integration with other tools /Flexibility:

Jira can be easily integrated with other tools like test management tools

BugZilla cannot be integrated.

5. Search option:

Both Jira and BugZilla have advance search.

6.Reporting feature:

Bugzilla has very primitive reporting and has no extensibility.

Jira has extensive reporting.

Advantages of Jira over BugZilla

1. Multi dimensional reporting consists of graphical presentations like Pie charts, Line graphs etc.

2. Easily customizable

3. Supports advanced search

4. Have specialized feature like Project management.

5. Can be easily integrated with any other tools like Attlasian suite, TestLink etc.

6. User friendly in both appearance and usage.

7. Also available as Open source with few features.

8. Can attach files and also link to other jira's(bugs)

Related Posts
Bug logging procedure
Bug Reporting

Webelements involved in a Webpage

2011-10-16T05:39:00.000-05:00

For automating an application it usually involves in few actions like :

Open url
Click on any element
Giving inputs
Submits forms
Selecting options in an list or drop down
Check/Uncheck the Checkboxes and Radio buttons

Hence, if the methods for above actions are defined before starting the automation of any application it would be more easier.

The methods for above actions should be in a generic manner so that they can be reused for any page of a single application and also for any other applications.

The level of identifying the elements on a web page goes on a level shown below

As shown in above flow diagram, for any web element the ID or Name will be given by default.

For complex applications or for the applications made of CSS then elements will not have the ID and Name mostly. Hence “ Xpath ” will be an alternate solution for it.

Attributes:

For the web elements they are defined by some attributes, listed below

If we go in to html level of a webpage then

Text boxes, Radio buttons and Checkboxes will have “input” as attribute
Dropdowns, List boxes will have the “ select” attribute
Links will have “a href” i.e; anchor tags as the attribute
Submit buttons will have “type=submit” as an attributes

Xpath Defenition:

The navigation through the syntax of an html page upto the element which we want to point

Is called “ Xpath”

Ex: //html//body//tr//td//div//”webelement”

Related Posts:

Automation of webelements