Testing Automation – Page 5

May 13, 2018May 17, 2020

QA Automation Interview questions

Differentiate final , finally, finalize (Short Ans: final method can’t be overridden, final variable can’t be changed, finally goes with try/catch, finalize is garbage collector)
how to handle exceptions in java (Ans: try catch, throws, etc)
how to use parameters in cucumber/testNG (Ans: scenario outline,tidy gherkin plugin, vs testng.xml-suite,test,class,method;)
compare TestNG and Cucumber BDD (Ans: testng.xml, POM,vs feature file,Junit testrunner,stepDefention, POM)
how to validate flatfiles , db using Java (Ans: input filestream, driver class connection, server name, instance , authentication, sql statement)
how to skip method/test in TestNG, Cucumber BDD (Ans: testng.xml, annotation, cucumber tags on testrunner)
differentiate encapsulation , abstraction
what are interface and explain the methods – webdriver interface, driver object reference, FF/IEdriver class (Since interface can not be instantiated)
write programs – sort array, print number in reverse, print string reverse, etc
how does SSL works , public key-private key, session encryption etc
method overridden vs method overloading (super class methods are overridden by child class when both has same methods, overload – one class has multiple methods with same method name but different parameters)
Selenium automation challenges (ajax – webdriver wait methods, frames switch, alert.accept, multiple windows handlers, pdf in webpage, alert vs modal confuse, dynamic id,name-use xpath contains, etc)
handle dropdown – select class
feature file extension
bufferbuilder usage
what is background, scenarios outline, before/afterhooks vs tags,
usage of autoit, robotclass, javascript executor,
Jenkins schedule batch, report generation,
grid setup, hub and node, run on dos prompt, or use JSON file to configure nodes and run JSON on commandline..then connect in Jenkins
how to manage Git versions between two teams
What is data structure and use of it test automation

December 9, 2017May 17, 2020

Summary of Web services and API testing using UFT

Web services

Demand of Web services is already high in the new internet era since applications are built in different technology / databases and connected through internet. So communication between is only possible through a commonly accepted media which are Web services

Web services are XML format based services which use media as HTTP to communicate and it is loosely coupled where there no hard binding with client.

WSDL

WSDL is a document in XML format which describes a web service and defines which transactions are available and data should be structured to send to those transactions.

WSDL (Web services description language) helps client to initiate the correct web service

Webserver client needs WSDL to initiate Web services and Web server providers generates WSDL.

UDDI

UDDI is the online directory which has all the WDSL available and all web services client gets that from UDDI.

Web services has two implementations.

1. SOAP

2. REST

SOAP

SOAP is the XML based implementation for web service and it has 3 main components which are

a. Envelope – represents root elements

b. Header – stores authentication, routing id for web service transaction.

c. Body – stores all data which are intended to transfer to webservice client.

SOAP uses HTTP as media for transferring data. Format used in XML.

REST

REST is more flexible implementation as it uses text format and media other than HTTP as well.

API testing using UFT

UFT is a software automation tool. Apart from automation test scenarios it supports API testing. Following AP testing are supported.

Web service

REST

In UFT user can create a new API project by clicking File > New > Test..

Select the API Test type

Then navigate to tool box in the left

Click on Network once it’s exploded,

Drag HTTP Request to Test flow

Right click and select the properties

Fill the URL, select HTTP method as GET

Also you can configure the checkpoints.

December 2, 2017February 23, 2020

Maven TestNG framework with reporting features and switching pages

1. Setup a Maven project in Eclipse with POM file as below

Refer the Post-Man plugin highlighted below in yellow

Refer the reporting directory path highlighted below in yellow

POM file sample as below – you can copy paste this contents for any Maven TestNG project.

<groupId>MavenProject</groupId>

<artifactId>MavenProject1</artifactId>

<version>0.0.1-SNAPSHOT</version>

<groupId>junit</groupId>

<artifactId>junit</artifactId>

</dependency>

<groupId>org.testng</groupId>

<artifactId>testng</artifactId>

</dependency>

<groupId>com.relevantcodes</groupId>

<artifactId>extentreports</artifactId>

</dependency>

<groupId>org.seleniumhq.selenium</groupId>

<artifactId>selenium-java</artifactId>

</dependency>

<groupId>net.sourceforge.jexcelapi</groupId>

</dependency>

<groupId>org.apache.poi</groupId>

</dependency>

</dependencies>

</dependency>

</dependencies>

</dependencyManagement>

<build>

<!– Suirefire plugin to run xml files –>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven–surefire–plugin</artifactId>

<!– TestNG suite XML files –>

<suiteXmlFile>testng.xml</suiteXmlFile>

</suiteXmlFiles>

</configuration>

</plugin>

<!– Post-Man plugin –>

<groupId>ch.fortysix</groupId>

<artifactId>maven-postman-plugin</artifactId>

<id>send an email</id>

<phase>testEmail</phase>

<goals>

<goal>send-an-email</goal>

</goals>

<!– From Email address –>

<from>[email protected]</from>

<!– Email subject –>

<subject>Test Report</subject>

<!– Fail the build if the mail doesnt reach –>

<!– host –>

<mailhost>smtp.gmail.com</mailhost>

<!– port of the host –>

<!– Email Authentication(USername and Password) –>

<mailuser>[email protected]</mailuser>

<!– To Email address –>

<receiver>[email protected]</receiver>

</receivers>

<!– Report directory Path –>

<directory>C://Projects//Eclipse//workspace//Mavenproject//Reports</directory>

<!– Report file name –>

</includes>

<!—as mentioned above Regular Expression **/*.html to send all the html files reports–>

</fileSet>

</fileSets>

</configuration>

</execution>

</executions>

</plugin>

</plugins>

</build>

</project>

2. Setup a Page factory package where all the object locators are stored. E.g. code like this below.

package ProjectPageFactory;

import java.io.File;

import java.io.FileInputStream;

import java.io.FileOutputStream;

import java.io.FileReader;

import java.util.Iterator;

import java.util.List;

import java.util.NoSuchElementException;

import static org.testng.AssertJUnit.assertEquals;

import java.io.FileInputStream;

import org.openqa.selenium.By;

import org.openqa.selenium.WebDriver;

import org.openqa.selenium.WebElement;

import org.openqa.selenium.firefox.FirefoxDriver;

import org.openqa.selenium.ie.InternetExplorerDriver;

import org.openqa.selenium.support.CacheLookup;

import org.openqa.selenium.support.FindBy;

import org.openqa.selenium.support.PageFactory;

import org.openqa.selenium.support.ui.Select;

import org.testng.annotations.BeforeSuite;

import org.testng.annotations.BeforeTest;

import org.testng.annotations.Test;

import org.openqa.selenium.support.ui.WebDriverWait;

import org.testng.annotations.Test;

public class yourFirstpageofApplication { // this is were you can build the locators repository.

WebDriver driver;

@FindBy(linkText=”LocatorHyperlinkTextName”) // type the Locator Hyperlink Text Name

@CacheLookup // use CacheLookup for any non dynamic objects , this will improve exection performance.

WebElement Hyperlink1;

@FindBy(xpath=”html/body/form/divXXXXXXX/xxxx”)

// @CacheLookup – do not use CacheLookup for any dynamic objects

WebElement objectName1;

2. Setup a test script code that communicates to Pageobject repository

public class applicationPageName extends initialiseDriver // refer step 3 for initialiseDriver example.

{

//WebDriver driver;

yourFirstpageofApplication AppObj;

@Test(priority = 1)

public void Excel() throws Exception

{

AppObj = new yourFirstpageofApplication(driver);

AppObj.ordinqclick(); // this will navigate to PageObject repository code and do action on application.

Note: Basically both classes (Test scripts and Pageobject repository script) will communicate.

3. Reporting code

package TestscriptProject;

import java.io.File;

import java.io.FileInputStream;

import java.util.List;

import java.util.concurrent.TimeUnit;

import org.openqa.selenium.By;

import org.openqa.selenium.WebElement;

import org.openqa.selenium.ie.InternetExplorerDriver;

import org.openqa.selenium.support.ui.Select;

import org.openqa.selenium.WebDriver;

import org.testng.annotations.AfterClass;

import org.testng.annotations.AfterTest;

import org.testng.annotations.BeforeTest;

import org.testng.annotations.Test;

import org.testng.asserts.SoftAssert;

import com.relevantcodes.extentreports.ExtentReports;

import com.relevantcodes.extentreports.ExtentTest;

import com.relevantcodes.extentreports.LogStatus;

import org.apache.poi.hssf.usermodel.HSSFRow;

import org.apache.poi.hssf.usermodel.HSSFSheet;

import org.apache.poi.hssf.usermodel.HSSFWorkbook;

import PageFactoryProject.ApplicatonPageScriptClass; // make sure you import that to this class

public class orderInquiryPage extends driverInitialise

{

//WebDriver driver;

yourFirstpageofApplication AppObj;

ExtentReports report;

ExtentTest logger;

@Test(priority = 1)

public void Excel() throws Exception

{

report = new ExtentReports(“./Reports/OrderInquiryReport.html”);

logger = report.startTest(“csvFile”);

logger.log(LogStatus.INFO, ” test case started”);

//Pass the test in to report

logger.log(LogStatus.PASS,”Test verified Pass for particular functionality”);

//End of the test

report.endTest(logger);

//clear the data in report

report.flush();

4. Switching between child window/page and parent window/page

To switch to a child window or page

public void childWindowHandle()

{

childHandle = driver.getWindowHandles().toArray()[y].toString(); // y = 1

driver.switchTo().window(childHandle);

}

To switch to a parent window or page

public void parentWindowHandle()

{

parentHandle = driver.getWindowHandles().toArray()[x].toString(); // x = 0

driver.switchTo().window(parentHandle);

}

December 2, 2017May 17, 2020

Cucumber Scenario data table and Scenario Outline data table

What is TestRunner in Cucumber?
Cucumber – Behavior driven development (BDD)

Cucumber Scenario data table and Scenario Outline data table

1.Cucumber Scenario data table

Sample feature file contents as below:

Feature: Login and Logout Action

Scenario: Successful Login with Valid Credentials

Given User is on Application Home Page

When User Navigates to Application LogIn Page

And User enters UserName and Password and click submit button

|UserName|Pwd |

|abc | 123 |

Then Message displayed as Login Successfully

Corresponding Selenium script contents as below:

@When(“^User enters UserName and Password and click submit button$”)

public void user_enters_UserName_and_Password_and_click_submit_button(DataTable table) throws Throwable {

// Write code here that turns the phrase above into concrete actions

List<List<String>> data = table.raw();

driver.findElement(By.id(“IDTokenA1”)).sendKeys(data.get(1).get(0));

driver.findElement(By.id(“IDTokenB1”)).sendKeys(data.get(1).get(1));

driver.findElement(By.name(“Login.Submit”)).click();

// throw new PendingException();

}

2.Cucumber Scenario Outline data table

Sample feature file contents as below:

Scenario Outline: Login functionality for a website.

Given User navigates to Login page

When user enters Username as “<username>” and Password as “<password>”

Then login should be unsuccessful

Examples:

| username | password |

| ABC | 123 |

Corresponding Selenium script contents as below:

@When(“^user enters Username as \“([^\”]*)\” and Password as \”([^\”]*)\”$”)

public void user_enters_Username_as_and_Password_as(String arg1, String arg2) {

driver.findElement(By.id(“IDTokenA1“)).sendKeys(arg1);

driver.findElement(By.id(“IDTokenB1“)).sendKeys(arg2);

driver.findElement(By.id(“Login.Submit“)).click();

}

3.TestRunner sample code

package cucumberTestRunnerTest;

* cucumberTestRunner sample code below

import org.junit.runner.RunWith;

import cucumber.api.junit.Cucumber;

import cucumber.api.CucumberOptions;

@RunWith(Cucumber.class)

@CucumberOptions(~~format~~={“pretty”}

,features = “Feature” // refer the above feature file sample

,glue={“stepDefinition”} // note: need to create a package stepDefinition and create a regression scriptclass

,dryRun = false)

public class TestRunnerTest {

}

Note: JUnit runner uses the JUnitframework to run Cucumber using annotation – you could see in the above code that single empty class with annotation.

4.Maven pom.xml file sample needs the following dependencies if you want to use Maven for build automation.

<groupId>junit</groupId>

<artifactId>junit</artifactId>

</dependency>

<groupId>info.cukes</groupId>

<artifactId>cucumber-java</artifactId>

</dependency>

<groupId>info.cukes</groupId>

<artifactId>cucumber-junit</artifactId>

</dependency>

<groupId>info.cukes</groupId>

<artifactId>cucumber-testng</artifactId>

</dependency>

</dependencies>

5.If you do not want to use Maven for build automation, you can attach the following jars to your project Java Build path.

cucumber-java

cucumber-core

cucumber-junit

cucumber-jvm-deps

cucumber-reporting

gherkin

junit

mockito-all

cobertura

6.Regression test case script will be like this (refer the Test runner sample code point #3 above)

package stepDefinition;

import java.util.List;

import java.util.concurrent.TimeUnit;

import org.openqa.selenium.By;

importorg.openqa.selenium.firefox.FirefoxDriver;

import org.openqa.selenium.ie.InternetExplorerDriver;

import org.openqa.selenium.WebDriver;

import cucumber.api.DataTable;

import cucumber.api.PendingException;

import cucumber.api.java.en.Given;

import cucumber.api.java.en.Then;

import cucumber.api.java.en.When;

public class RegressionTest { // refer the Test runner sample code point #3 to see how the this code is mapped

WebDriver driver;

// run TestRunner.java file and get the out put from Console and copy/paste below:

@Given(“^User is on Application Login Page$”)

public void user_is_on_Application_Home_Page() throws Throwable {

// Write code here that turns the phrase above into concrete actions

driver = new InternetExplorerDriver();

driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);

//throw new PendingException();

}

7. If you do not want to use the DataTable from feature file, always you can pull the data from XLS file using the logic below.

package yourpagename;

import org.apache.poi.hssf.usermodel.HSSFRow;

import org.apache.poi.hssf.usermodel.HSSFSheet;

import org.apache.poi.hssf.usermodel.HSSFWorkbook;

import java.io.File;

import java.io.FileInputStream;

importjava.util.List;

importjava.util.concurrent.TimeUnit;

importorg.openqa.selenium.By;

importorg.openqa.selenium.WebElement;

importorg.openqa.selenium.ie.InternetExplorerDriver;

importorg.openqa.selenium.support.ui.Select;

importorg.openqa.selenium.WebDriver;

importorg.testng.annotations.AfterClass;

importorg.testng.annotations.AfterTest;

importorg.testng.annotations.BeforeTest;

import org.testng.annotations.Test;

import Package.AnyotherClass; // if needed

public class AnyotherClassPage extends InitialClass

{

//WebDriver driver;

AnyotherClass ObjectName;

@Test(priority = 1)

public void Excel() throws Exception

{

ObjectName = new AnyotherClass (driver);

ObjectName.objectclick();

System.out.println(“Started executing Test Cases”);

// load excel file

File filePath = new File(“C:\\xxxxx\\ExcelFileName.xls”);

FileInputStream FS = new FileInputStream(filePath);

HSSFWorkbook WB = new HSSFWorkbook(FS);

HSSFSheet sheet = WB.getSheetAt(0);

int rowcount = sheet.getLastRowNum() – sheet.getFirstRowNum();

int colcount = sheet.getRow(0).getLastCellNum();

int a =0 ;

System.out.println(“Number of rows” + rowcount);

System.out.println(“Number of columns” +colcount);

for(int b=1;b<rowcount;b++)

{

HSSFRow row = sheet.getRow(b);

//for(int j=0;j<colcount;j++)

//{

//HSSFCell cell = row.getCell(j);

String excelCell1 = row.getCell(a).getStringCellValue();

String excelCell2 = row.getCell(a+1).getStringCellValue();

System.out.println(“XLS Values are — “ + excelCell1 + “—“ + excelCell2);

//}

ObjectName.NewMethod1(excelCell1);

ObjectName.NewMethod2(excelCell2); // code continues … …

What is TestRunner in Cucumber

TestRunner is a program used in Cucumber to access Feature file as copied in the picture below.

Feature file is something that has user requirement scenarios written in English which gives more readability and understandability of the requirement which is called Gherkin language.

So any roles in the company like Tester, developer, end user, and techno functional person can read it and understand it. Also this will reduce the complication in terms of missing requirement or misrepresenting or misunderstanding requirements between different roles like Developer , tester, and end user,

In order to link Cucumber with Selenium WebDriver, you need to start a Java project in eclipse IDE.

Then, add both Cucumber and Selenium jar files

Write test runner code and execute the same . Please refer BDD testing details on Selenium Cucumber

Sample Test runner code:

Testrunner

**Automaton testing using Cucumber – Behavior driven development (BDD)**

Application behavior is the main focus on BDD. The requirements are written in English which gives more readability and understandability of the requirement.

So any roles in the company like Tester, developer, end user, and techno functional person can read it and understand it. Also this will reduce the complication in terms of missing requirement or misrepresenting or misunderstanding requirements between different roles like Developer , tester , end user etc.

Gherkin is a business readable language, refer below for an example. Below feature file is integrated with Selenium and are having user stories as below.

Please refer below – “feature, Scenario, Given, When, And, Then “are the Keywords below to understand on how to write a feature file…

**What is Feature file in Cucumber test and how to create a feature file.**

Feature file is a part of Cucumber framework and it contains descriptions in English language.

Follow below path to create a feature file

create feature file

**One sample transaction as below:**

**One sample transaction example as below:**

sample feature file transaction

November 30, 2017June 13, 2020

Summary about Jmeter and performance testing

Jmeter recording

How to create Jmeter scripts?

Recording Jmeter scripts using Jmeter’s HTTP(S) Test Script recorder. There are two ways

1) Manually adding scripts ( Test plan >> Tread Group >> Add>> Sampler >> HTTP Request )

2) Recording using Jmeter’s HTTP(S) Test Script recorder

How to record Jmeter scripts using HTTP(S) Test Script recorder

Prior doing that we need to configure browser and learn about the Proxy setup

Jmeter to Application server communication need to be routed through a browser Proxy for this recording purpose. For that you may need to select the Browser (here we can use Firefox browser”

1) Navigate to Firefox >> Tools >> options >> Advanced >> Network >> Settings

2) Select Manual Proxy configuration >> HTTP Proxy = localhost & Port = 8080

How to run Jmeter in Jenkins

steps:

Jenkins setup and performance plugin setup:
1) copy performance plugin into Jenkin’s home directry before you start the test.
2) to do that – you can download the performance plugin “performance.hpi” from the site https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin
3) how to find the home directry of jenkins – to do that you can navigate to jenkins home page (localhost:8080) and then
4) click on “Manage Jenkins” and then click on “Configure system” the you will notice “Home directy” path in there.

Configure Jmeter and create a basic script in Jmeter:
5) download Jmeter Binary zip file from Jmeter site http://jmeter.apache.org/download_jmeter.cgi
6) unzip it and go to the “bin” directory of the Jmeter folder, wherre you will notice “user.properties” file.
7) open the file in notepad or notepad++ or any other text editor
8) add a line “jmeter.save.saveservice.output_format=xml” to that. Save and close the “user.properties” file
9) create a Jmeter script and make sure you can run it in non GUI mode i.e either in DOS mode or using shell scripts in MAC (note down the commands used in respective OS and it could be used in Jenkins job setup)
Note: for windows command line run, you can use the following commands

C:\[JMETER BIN directory]\jmeter.bat -Jjmeter.save.saveservice.output_format=xml -n -t C:\[JMETER script “.jmx” file] -l Jmeter_test_results.jtl

Note 1: For detailed topics on Jmeter scripts creation , please visit Jmeter , Jmeter recording

setup Jenkin’s job to run Jmeter scripts
9) go to Jenkins home page (localhost:8080) and then click on “New Item” on “Freestyle project”
10) in the “New item” page, give some name in the item name field and go to below to section “Build” and add build step
11) add build step can be either a) “execute windows batch command” for windows or b) “Execute shell” for MAC
12) provide your command in there and save.
13) Click on “Build now” which would call the Jmeter (jmx) file and run the program
14) after the run, you can verify the Jenkins console to review the results.

QA Automation Interview questions

Summary of Web services and API testing using UFT

Web services

WSDL

UDDI

SOAP

REST

API testing using UFT

Web service

REST

Maven TestNG framework with reporting features and switching pages

1. Setup a Maven project in Eclipse with POM file as below

2. Setup a Page factory package where all the object locators are stored. E.g. code like this below.

2. Setup a test script code that communicates to Pageobject repository

3. Reporting code

4. Switching between child window/page and parent window/page

Cucumber Scenario data table and Scenario Outline data table

1.Cucumber Scenario data table

Corresponding Selenium script contents as below:

2.Cucumber Scenario Outline data table

Corresponding Selenium script contents as below:

3.TestRunner sample code

4.Maven pom.xml file sample needs the following dependencies if you want to use Maven for build automation.

5.If you do not want to use Maven for build automation, you can attach the following jars to your project Java Build path.

6.Regression test case script will be like this (refer the Test runner sample code point #3 above)

7. If you do not want to use the DataTable from feature file, always you can pull the data from XLS file using the logic below.

What is TestRunner in Cucumber

Automaton testing using Cucumber – Behavior driven development (BDD)

Summary about Jmeter and performance testing