Java Real Time Interview Questions-Selenium WebDriver - Total-QA

Execute Selenium WebDriver Tests from Jenkins 2.0 Pipeline

total-qa June 5, 2019 No Comments

Pipelines allows Jenkins to support continuous integration (CI) and Continous Delivery (CD). Pipeline are nothing but the Jenkins jobs the simple text scripts are based on Groovy Programming language. Pipeline terms such as “Step”, “Node” and “Stage” are subset of vocabulary using in Jenkins.

Step:
It defines the Single task which is part of the sequence tell Jenkins what to do.

Node:
A “node” means any computer that is part of your Jenkins installation.

Stage:
A “stage” is comprised of one or more build steps.

Pre-requisites:
Download Jenkins 2.0 from this link https://jenkins.io/download/ which is recommended.
Core Pipeline Plugin

Plugin Name – Pipeline:
In this tutorial we will learn about using Pipeline plugin and its usage.
It allows Jenkins to execute the Pipeline API and Basic Steps.
Download the Pipeline Plugin from this link https://wiki.jenkins.io/display/JENKINS/Pipeline+Plugin

SCM’s:
Git Plugin

Cloud Plugins{optional}:
Docker
ec2
Jenkins Environmental Variables:
echo “BUILD_NUMBER” :: $BUILD_NUMBER
echo “BUILD_ID” :: $BUILD_ID
echo “BUILD_DISPLAY_NAME” :: $BUILD_DISPLAY_NAME
echo “JOB_NAME” :: $JOB_NAME
echo “JOB_BASE_NAME” :: $JOB_BASE_NAME
echo “BUILD_TAG” :: $BUILD_TAG
echo “EXECUTOR_NUMBER” :: $EXECUTOR_NUMBER
echo “NODE_NAME” :: $NODE_NAME
echo “NODE_LABELS” :: $NODE_LABELS
echo “WORKSPACE” :: $WORKSPACE
echo “JENKINS_HOME” :: $JENKINS_HOME
echo “JENKINS_URL” :: $JENKINS_URL
echo “BUILD_URL” ::$BUILD_URL
echo “JOB_URL” :: $JOB_URL

Note:
Any of the Jenkins Environmental Variables are used in the Pipeline Script in the following way:
echo ${env.BUILD_NUMBER}

Creating a Simple Pipeline Script:

1. Open the Jenkins Home Page URL. Click on New Item in Jenkins home Page.

2. Provide the new item name. Select the Pipeline option. Click on OK button.

Jenkins Pipeline Script Example

3. Open the Jenkins job created in Step2. Click on Configure->Pipeline Syntax link to generate the Script automatically.

Pipeline Syntax Example

3. Create a Jenkinsfile with the pipeline script mentioned below:

Github Repository-> Link

pipeline {
  agent any
  stages {
    stage('Execute Selenium Tests from Github Repo Using Jenkins 2.0 Pipeline') {
      steps {
        echo 'Execute Tests'
        echo "Running ${env.BUILD_ID} on ${env.JENKINS_URL}"
        echo "Jenkins Workspace ${env.WORKSPACE}"
        bat "mvn -f openmrs clean"
        bat "mvn -f openmrs test -P QA"
      }
    } 
  }
}
}

pipeline {

agent any

stages {

stage('Execute Selenium Tests from Github Repo Using Jenkins 2.0 Pipeline') {

steps {

echo 'Execute Tests'

echo "Running ${env.BUILD_ID} on ${env.JENKINS_URL}"

echo "Jenkins Workspace ${env.WORKSPACE}"

bat "mvn -f openmrs clean"

bat "mvn -f openmrs test -P QA"

}

4. Configure the Jenkins job created in Step2. Refer to the Jenkinsfile from the Github Repository.

Jenkins Pipeline SCM Configuration

5. Click on Build Now to execute the Job Successfully.

6. Open the JOB Console to view the Results.

JenkinsfileExecution

Uploading the Sonarlint results to SonarQube[Cloud Server]

total-qa June 4, 2019 No Comments

Before getting into this tutorial please read the information about the Sonarlint by clicking on this link.
Sonarlint helps the developer analyzes the code quality on the fly and displays the scan results. Now the Question is, would it be possible to push these results to SonarQube.

What is SonarQube??

SonarQube provides the capability of displaying the results in a Dashboard. And it also helps to configure the Quality Gate to improve the Code Quality. If we want to publish the results from Sonarlint to SonarQube the code does not require any compilation. Once the code scans are done we can push the results directly into SonarQube.

Bind the Sonarlint to SonarQube:

Right click on the project in Eclipse Select Sonarlint->Bind to SonarQube to SonarCloud option as mentioned below:

Binding Sonarlint to SonarQube or SonarCloud

Select the connection type as SonarCloud and click on Next button.

SonarCloud Connection

Provide the Token generated from SonarCloud Server in the mentioned dialog box.

GenerateToken

Access the SonarCloud server URL https://sonarcloud.io/projects as mentioned below.
Click on Analyze new project button and

SonarCloudServer-Analyze New Projects

Provide all the required information and click onSet Up button.

AnalyzeProjects -SonarCloudServer

Click on the Generate button for generating new token.

GenerateToken

Run the analysis on your project.

Sonar Cloud – Run Analysis

Execute the Command from the Command line to push results of Sonarlint to the SonarQube Cloud.

mvn sonar:sonar \
-Dsonar.projectKey=SonarlintScanResults \
-Dsonar.organization=totalqa \
-Dsonar.host.url=https://sonarcloud.io \
-Dsonar.login=5a24ca7f4b56ccabd93da62f36915f08f8517482

Sonarlint-Scan Results

Conclusion

Results generated from Sonarlint are pushed into SonarQube Server Successfully.

Sonarlint-Instant Feedback Selenium,JAVA,Eclipse

total-qa June 1, 2019 1 Comment

Sonarlint helps the developers to identify the issues on the fly when you write the code immediately. It helps to detect the common mistakes and vulnerabilities based on the thousands of rules in various languages such as Java,Javascript,PHP and PHP . It also helps to scan the source code in different IDE’s such as Eclipse IDE,Intellij IDEA,Visual Studio and VS Code. Please find the list of Sonarlint rules from the link mentioned below:

https://rules.sonarsource.com

Vulnerability Examples:

Its a weakness in the code, which can be exploited by an actor to perform unauthorized actions within a computer system.
“public static” fields should be constant:
Noncompliant Code Example:

public class TotalQA{

	public static ClassA a1 = new ClassA();

}

public class TotalQA{

public static ClassA a1 = new ClassA();

}

Compliant Code Example:

public class TotalQA{
	public static final ClassA a1 = new ClassA();
}

public class TotalQA{

public static final ClassA a1 = new ClassA();

}

Bug Example:

Loops should not be infinite:
Noncompliant Code Example:

for (;;) {  // Noncompliant; end condition omitted
  // ...
}

for (;;) { // Noncompliant; end condition omitted

// ...

}

Code Smells:

Nothing but the violation of the Fundamental Design Principals.
Tests Should include Assertions:
Noncompliant Code Example:

Code Smells|Noncompliant Code Example

public void verityTitle() { WebDriver driver = new ChromeDriver(); driver.get("http://www.total-qa.com"); driver.getTitle(); }

1
2
3
4
5
6

public void verityTitle()
{
WebDriver driver = new ChromeDriver();
driver.get("http://www.total-qa.com");
driver.getTitle();
}

default Clauses should be last in the Switch Case

Code Smells|Noncompliant Code Example

switch (param) { case 0: break; default: error(); break; case 1: break; }

1
2
3
4
5
6
7
8
9

switch (param) {
  case 0:
    break;
  default:
    error();
    break;
  case 1:
    break;
}

Code Smells|Compliant Code Example

switch (param) { case 0: break; case 1: break; default: break; }

1
2
3
4
5
6
7
8

switch (param) {
  case 0:
    break;
  case 1:
    break;
   default:
    break;
}

Using Sonarlint in Eclipse:

Download the Sonarlint Plugin from the Eclipse Market Place. During the Development of the Code, the Sonarlint highlights the issues in the editor. It also gives the rule description on the the fly.Once the plugin is installed successfully. Open the Eclipse and write a sample program to verify the rules.
Sonarlint-Eclipse Marketplace

Analyze the Java Source Code using Sonarlint:

Sonarlint-Instant Code Scan

Click on the rule to view the Rule Description

Sonarlint:RuleDescription

Enable the rules in Sonarlint:
Navigate to the Window->Preferences->Sonarlint->Rules Configuration to select the rule configuration for different languages.

Sonarlint-Rules

SonarlintRules_Enable_Disable

Conclusion:

Sonarlint plugin in Eclipse enables the Developers to identify the issues early in the Coding phase to fix the issues during the time of development and fix them on the fly with Compliant Solution.

JAVA Eclipse, InstantFeedback, Java, Sonarlint

Soft Asserts and Hard Asserts in TestNG

total-qa    May 12, 2019 May 12, 2019    No Comments on Soft Asserts and Hard Asserts in TestNG

TestNG is mainly used by the JAVA Developers to perform Unit Testing of the Code. This Framework is used mainly in Selenium as well to verify the outcome of the automation test Scenario. To verify the outcome the assert statements are available in the org.testng.Assert Class used such as

Assert.assertEquals

Assert.assertTrue

Assert.assertFalse

Assert.assertNotNull

.
They are different types of Assert types such as

Hard Assert

Soft Assert

Hard Assert:

In Hard Assert if the assertion is failing the execution stops.
Assert.assertTrue statement fails the test and stops the execution and makes the test case as failing.
Assert.assertFalse statement continues the test, if the element is not present in the Web Application.
Assert.assertFalse statement stops the execution of the test, if the element is present in the Web Application.

package org.totalqa.tests; import org.testng.Assert; import org.testng.annotations.Test; import org.openqa.selenium.chrome.ChromeDriver; import io.github.bonigarcia.wdm.WebDriverManager; public class Totalqa_HardAssert { ChromeDriver driver; @Test public void verifyTitle() { WebDriverManager.chromedriver().setup(); driver = new ChromeDriver(); driver.get("http://total-qa.com/"); String expected = "Total-QA - Future of Software Testing"; String actual = driver.getTitle(); Assert.assertEquals(actual, expected); } }

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

package org.totalqa.tests;
import org.testng.Assert;
import org.testng.annotations.Test;
import org.openqa.selenium.chrome.ChromeDriver;
import io.github.bonigarcia.wdm.WebDriverManager;
public class Totalqa_HardAssert {

ChromeDriver driver;
@Test
public void verifyTitle() {

WebDriverManager.chromedriver().setup();
driver = new ChromeDriver();
driver.get("http://total-qa.com/");
String expected = "Total-QA - Future of Software Testing";
String actual =   driver.getTitle();
Assert.assertEquals(actual, expected);
}
}

Soft Assert:

In Soft Assert if the assertion is failed the execution doesn’t stops. The execution continues to the next step. The org.testng.asserts.SoftAssert object collects all the errors. If you need to throw an exception then you need to use the method assertAll() as the last statement in the @Test. And the execution continues to the next @Test.
assertAll fails the test case if any of the assertions are failed.

package org.totalqa.tests; import org.testng.Assert; import org.testng.annotations.Test; import org.openqa.selenium.chrome.ChromeDriver; import io.github.bonigarcia.wdm.WebDriverManager; public class Totalqa_SoftAssert { ChromeDriver driver; @Test public void verifyTitle() { WebDriverManager.chromedriver().setup(); driver = new ChromeDriver(); driver.get("http://total-qa.com/"); SoftAssert sa = new SoftAssert(); String expectedTitle = "Selenium QA"; String actualTitle = driver.getTitle(); //First Assertion actual is matching as expected //Assertion is failed, continue with the execution sa.assertEquals(actualTitle, expectedTitle); String expectedText ="Advanced Selenium"; String actualText = driver.findElement(By.linkText("Advanced Selenium")).getText(); sa.assertEquals(actualText, expectedText); //Its mandatory to call this statement //If any of the assertions are failed the Test case will fail sa.assertAll(); } }

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

package org.totalqa.tests;
import org.testng.Assert;
import org.testng.annotations.Test;
import org.openqa.selenium.chrome.ChromeDriver;
import io.github.bonigarcia.wdm.WebDriverManager;

public class Totalqa_SoftAssert {

ChromeDriver driver;
@Test
public void verifyTitle() {

WebDriverManager.chromedriver().setup();
driver = new ChromeDriver();
driver.get("http://total-qa.com/");
SoftAssert sa = new SoftAssert();

String expectedTitle = "Selenium QA";
String actualTitle =   driver.getTitle();
//First Assertion actual is matching as expected
//Assertion is failed, continue with the execution
sa.assertEquals(actualTitle, expectedTitle);

String expectedText ="Advanced Selenium";
String actualText = driver.findElement(By.linkText("Advanced Selenium")).getText();
sa.assertEquals(actualText, expectedText);

//Its mandatory to call this statement
//If any of the assertions are failed the Test case will fail
sa.assertAll();
}
}

Summary

It’s important to decide what kind of Assertion is required.
If you want your assert method to fail and stops the execution use the Hard Assert.
If you want your assert method to fail and continues with the execution of the second assert and collect all the results at the end of the test use Soft Assert.

Selenium, TESTNG    assert, assertEquals, assertTrue, hard assert, soft assert

Enabling Writing Tests with in JIRA using Zephyr Plugin

total-qa    April 27, 2019 April 27, 2019    No Comments on Enabling Writing Tests with in JIRA using Zephyr Plugin

Follow this Atlassian Software-JIRA Registration Link to register for a free account for using JIRA. Click on the Link received in your email inbox to verify your email Address.This product is available in the Cloud, free for 7 days .
Login to JIRA by clicking on the Link received in the email.Click on Create Issue to view the Issue Types available. Currently issue types visible in JIRA by default are as follows: Story,EPIC,Task,Bug

JIRA Issue Types-Story,Epic,Task,Bug

To view the Test as Issue type in JIRA a plugin named Zephyr has to be installed.
Follow the Steps to enable the Zephyr plugin in JIRA. JIRA Settings->Apps->Find new Apps

Filter Apps in JIRA

Provide the name to filter the apps named by Zephyr.

ZephyrPlugin

Once the Zephyr plugin is successfully installed the issue Type Test is not visible in the Issue List.
Enabling Test to write Tests with in JIRA using Zephyr Plugin JIRA Settings->Issues->Issue type Schemas->Edit.
Drag and Drop the Issue Type Test from Available Issue Types to the section
Issue Types for Current Schema.

Test Issue Type in JIRA

Click on Save button to save the Issue type Schema.

Zephyr Test Issue

Verify the issue Test is visible in JIRA as mentioned below:

Issue Type Test

Testing    Atlassian, JIRA, Zephyr

Resolving the Git Error current-branch-is-not-configured-for-pull

total-qa    April 6, 2019 April 6, 2019    No Comments on Resolving the Git Error current-branch-is-not-configured-for-pull

Resolution for the Error ->Current Branch is not configured for Pull. No Value for key remote.origin.url found in configuration.
In Github , during the creation of branch we should make sure to select the option configure upstream for push and pull. What happens if this option is not selected?? This causes the “git pull” operation causing the error. In this post we are going to discuss on now fixing the error in Eclipse as follows:

configure upstream for push and pull

Right Click on the project in Eclipse->Team->Git Pull throws the following Error:

Pulling 1 repository
The current branch is not configured for pull
No value for key remote.origin.url found in configuration

How do we resolve this Error now???
Navigate to the Eclipse Menu->Window->Show View->Other->Git Repositories.

GitRepositories

Update the Config File in the Repository as mentioned below:

[branch “PullRequestError”]
remote = origin
merge = refs/heads/PullRequestError

What is the statement **refs/heads/PullRequestError** in the config file refer to ??

The ref in the URL must be formatted as heads/<branch name> for branches and tags/<tag name> for tags. If the ref doesn’t exist in the repository, but existing refs start with ref they will be returned as an array. If the ref doesn’t match an existing ref or any prefixes, a 404 is returned.

DevOps, REST API

Running suite-of-suites Parallely in Testng

total-qa    April 6, 2019 April 6, 2019    1 Comment on Running suite-of-suites Parallely in Testng

TestNG is a java framework useful to execute the Unit Tests in a java project. We can even TestNG to automate the Selenium Tests in the Project.In TestNG xml file, the execution of Tests is managed by setting the “parallel” attribute and “thread-count” attribute in the suite xml as follows:

<suite name=”My suite” parallel=”methods” thread-count=”5″>

<suite name=”My suite” parallel=”tests” thread-count=”5″>

<suite name=”My suite” parallel=”classes” thread-count=”5″>

<suite name=”My suite” parallel=”instances” thread-count=”5″>

Now the question arises that how can we execute multiple Testng xml files in the project. The solution is as follows:

<suite name=”Running Suite Files” verbose=”1″ preserve-order=”true”>
        <listeners>
                <listener class-name=”org.testng.reporters.VerboseReporter”/>
        </listeners>
        <suite-files>
                <suite-file path=”testng1.xml”/>
                <suite-file path=”testng2.xml”/>
        </suite-files>
</suite>

How do we execute these suite-of-suite files parallely?

package org.totalqa.tests; import java.util.ArrayList; import java.util.List; import org.testng.TestListenerAdapter; import org.testng.TestNG; public class ParallelSuites { public static void main(String[] args) { TestNG testng = new TestNG(); TestListenerAdapter adapter = new TestListenerAdapter(); List<String> suites = new ArrayList<String>(); testng.addListener(adapter); suites.add("Suite.xml"); testng.setTestSuites(suites); testng.setParallel("parallel"); testng.setSuiteThreadPoolSize(5); testng.setOutputDirectory(System.getProperty("user.dir")+"//target"); testng.run(); } }

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

package org.totalqa.tests;
import java.util.ArrayList;
import java.util.List;
import org.testng.TestListenerAdapter;
import org.testng.TestNG;
public class ParallelSuites
{
    public static void main(String[] args)
    {
        TestNG testng = new TestNG();
        TestListenerAdapter adapter = new TestListenerAdapter();
        List<String> suites = new ArrayList<String>();
        testng.addListener(adapter);
        suites.add("Suite.xml");
        testng.setTestSuites(suites);
        testng.setParallel("parallel");
        testng.setSuiteThreadPoolSize(5);
        testng.setOutputDirectory(System.getProperty("user.dir")+"//target");
        testng.run();
    }
}

Conclusion::

Execution of the ParallelSuites.java program, stores the Results in the output folder.Make sure the Project is refreshed to view the results as mentioned below:

is-there-a-possible-way-to-run-two-xml-files-in-testng-xml-parallel

REST API, TESTNG    suite, testng, testng.xml

Passing command line arguments for Selenium Maven Testng

total-qa    March 23, 2019 March 23, 2019    1 Comment on Passing command line arguments for Selenium Maven Testng

TestNG allows you to group your tests and also allows to pass Test Parameters using parameter tag in the TestNG xml file.
You can then execute one or more specific groups such as Sanity,Regression or Functional Tests based on the requirement and passing the parameter values to the testng.xml using maven-surefire-plugin via pom.xml the following configuration is helpful.

<plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>3.0.0-M3</version> <configuration> <suitexmlFiles> <suiteXmlFile>testng.xml</suiteXmlFile> </suitexmlFiles> <systemPropertyVariables> <propertyName>urlValue</propertyName> </systemPropertyVariables> <groups>sanity,regression</groups> </configuration> </plugin> </plugins>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

<plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>3.0.0-M3</version>
        <configuration>
          <suitexmlFiles>
<suiteXmlFile>testng.xml</suiteXmlFile>
</suitexmlFiles>
<systemPropertyVariables>
<propertyName>urlValue</propertyName>
</systemPropertyVariables>
          <groups>sanity,regression</groups>
        </configuration>
      </plugin>
</plugins>

Passing the specific group name from the Command Line is achieved by updating the configuration of maven-sure-fire plugin as follows:

<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>3.0.0-M3</version> <configuration> <suitexmlFiles> <suiteXmlFile>Grouping.xml</suiteXmlFile> </suitexmlFiles> <systemPropertyVariables> <propertyName>${url}</propertyName> </systemPropertyVariables> <groups>${groups}</groups> </configuration> </plugin>

1
2
3
4
5
6
7
8
9
10
11
12
13
14

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M3</version>
<configuration>
<suitexmlFiles>
<suiteXmlFile>Grouping.xml</suiteXmlFile>
</suitexmlFiles>
<systemPropertyVariables>
<propertyName>${url}</propertyName>
</systemPropertyVariables>
<groups>${groups}</groups>
</configuration>
</plugin>

Maven Command Line:

Maven Command Line Arguments-Selenium,TESTNG

Steps to achieve is mentioned as follows:

Like our Facebook Page to stay in touch with us. Happy Testing!!!!
https://www.facebook.com/totalqa

1. Create a Testng @Test program as follows.

package org.totalqa.tests; import org.openqa.selenium.WebDriver; import org.openqa.selenium.chrome.ChromeDriver; import org.testng.Assert; import org.testng.annotations.Parameters; import org.testng.annotations.Test; import io.github.bonigarcia.wdm.WebDriverManager; public class GroupingTests{ @Parameters({"url"}) @Test(groups={"sanity","regression"}) public void verifyTitle(String url) { WebDriverManager.chromedriver().setup(); WebDriver driver = new ChromeDriver(); driver.get(url); String actual = driver.getTitle(); String expected = "Total-QA - Future of Software Testing"; Assert.assertEquals(actual, expected); } @Test(groups={"sanity"}) public void test2() { } }

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

package org.totalqa.tests;

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.testng.Assert;
import org.testng.annotations.Parameters;
import org.testng.annotations.Test;

import io.github.bonigarcia.wdm.WebDriverManager;

public class GroupingTests{

@Parameters({"url"})
@Test(groups={"sanity","regression"})
public void verifyTitle(String url)
{
WebDriverManager.chromedriver().setup();
WebDriver driver = new ChromeDriver();
driver.get(url);
String actual = driver.getTitle();
String expected = "Total-QA - Future of Software Testing";
Assert.assertEquals(actual, expected);
}

@Test(groups={"sanity"})
public void test2()
{

}

}

2. Create an Grouping.xml file to invoke the Testng @Test Program.

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd"> <suite name="Suite" verbose="5"> <test name="Test"> <classes> <class name="org.totalqa.tests.GroupingTests" /> </classes> </test>  </suite> 

1
2
3
4
5
6
7
8
9
10

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite" verbose="5">
<test name="Test">

<classes>
     <class name="org.totalqa.tests.GroupingTests" />
</classes>
</test> 
</suite> 

3. Update the pom.xml as follows.

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>org.iit.mmp</groupId> <artifactId>seleniummaven</artifactId> <version>0.0.1-SNAPSHOT</version> <packaging>jar</packaging> <name>seleniummaven</name> <url>http://maven.apache.org</url> <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> </properties> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.8.0</version> <configuration> <verbose>true</verbose> <fork>true</fork> <executable>C:\Program Files\Java\jdk1.8.0_65\bin\javac.exe</executable> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>3.0.0-M3</version> <configuration> <suitexmlFiles> <suiteXmlFile>Grouping.xml</suiteXmlFile> </suitexmlFiles> <systemPropertyVariables> <propertyName>${url}</propertyName> </systemPropertyVariables> <groups>${groups}</groups> </configuration> </plugin> </plugins> </build> <dependencies> <dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium-java</artifactId> <version>3.141.59</version> </dependency> <dependency> <groupId>io.github.bonigarcia</groupId> <artifactId>webdrivermanager</artifactId> <version>3.2.0</version> </dependency> <dependency> <groupId>org.testng</groupId> <artifactId>testng</artifactId> <version>6.8</version> </dependency> </dependencies> </project>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>

<groupId>org.iit.mmp</groupId>
<artifactId>seleniummaven</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>jar</packaging>

<name>seleniummaven</name>
<url>http://maven.apache.org</url>

<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.8.0</version>
<configuration>
<verbose>true</verbose>
<fork>true</fork>
<executable>C:\Program Files\Java\jdk1.8.0_65\bin\javac.exe</executable>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M3</version>
<configuration>
<suitexmlFiles>
<suiteXmlFile>Grouping.xml</suiteXmlFile>
</suitexmlFiles>
<systemPropertyVariables>
<propertyName>${url}</propertyName>
</systemPropertyVariables>
<groups>${groups}</groups>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-java</artifactId>
<version>3.141.59</version>
</dependency>
<dependency>
<groupId>io.github.bonigarcia</groupId>
<artifactId>webdrivermanager</artifactId>
<version>3.2.0</version>
</dependency>
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<version>6.8</version>
</dependency>
</dependencies>
</project>

4. Download the apache maven software apache-maven-3.6.0-bin.tar.gz from this url https://maven.apache.org/download.cgi.

5. Set the classpath as follows.

Apache Maven Software Classpath

6. Execute the following command from the command line.

Maven Command Line Arguments-Selenium,TESTNG

Conclusion:

Passing the command line arguments is possible by using apache maven via pom.xml to the TestNG.xml

Selenium, TESTNG    -Dgroups, -Durl, maven, maven-surefire-plugin, pom.xml, selenium

Headless Browser in Selenium using PhantomJS-Pros and Cons

total-qa    February 10, 2019 February 10, 2019    No Comments on Headless Browser in Selenium using PhantomJS-Pros and Cons

PhantomJS is a headless web browser scriptable with JavaScript which is similar to HTMLUnitDriver. Click on this link to view the examples of the HTMLUnitDriver.

PhantomJS runs on Windows, macOS, Linux, and FreeBSD. Currently the PhantomJS development is stopped due to less support from the group.

Pros of Headless Browser:

Headless browser executes the scripts faster then the real browser.

Helps us in improves the performance execution of the scripts.
Headless browser saves time.

Cons of Headless Browser:

Headless browser does not mimic the real execution of the test-cases.

It not possible to view the steps visually during the execution of the test-cases.

Like our Facebook Page to get frequent updates->

https://www.facebook.com/totalqa

Selenium WebDriver Code

1. Add the following dependency in the pom.xml to add the PhantomJS Library to the build path:

<dependency> <groupId>com.github.detro.ghostdriver</groupId> <artifactId>phantomjsdriver</artifactId> <version>1.0.3</version> </dependency>

1
2
3
4
5

<dependency>
<groupId>com.github.detro.ghostdriver</groupId>
<artifactId>phantomjsdriver</artifactId>
<version>1.0.3</version>
</dependency>

2. Instead of the setting the path to the Phantom JS executable. Use the WebDriverManager class ensure the following depedency is added in the maven project object model (pom.xml) file.

<dependency> <groupId>io.github.bonigarcia</groupId> <artifactId>webdrivermanager</artifactId> <version>3.2.0</version> </dependency>

1
2
3
4
5

<dependency>
       <groupId>io.github.bonigarcia</groupId>
<artifactId>webdrivermanager</artifactId>
<version>3.2.0</version>
</dependency>

3. Execute the below code in eclipse and verify the results.

import org.openqa.selenium.WebDriver; import org.openqa.selenium.chrome.ChromeDriver; import org.testng.Assert; import org.testng.annotations.Test; import io.github.bonigarcia.wdm.WebDriverManager; public class GoogleTests { @Test public void verifyTitle() { WebDriverManager.chromedriver().setup(); WebDriver driver = new ChromeDriver(); driver.get("http://www.total-qa.com"); String actual = driver.getTitle(); String expected="Total-QA - Future of Software Testing"; Assert.assertEquals(actual,expected); } }

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.testng.Assert;
import org.testng.annotations.Test;
import io.github.bonigarcia.wdm.WebDriverManager;

public class GoogleTests {

@Test
public void verifyTitle()
{

WebDriverManager.chromedriver().setup();
WebDriver driver = new ChromeDriver();
driver.get("http://www.total-qa.com");
String actual = driver.getTitle();
String expected="Total-QA - Future of Software Testing";
Assert.assertEquals(actual,expected);
}
}

Conclusion

Selenium Code executed successfully without launching the Browser.

HeadLess Browser using the PhantomJS Driver

Selenium, TESTNG    Driver, headless, PhantomJSDriver, selenium, webdriver, WebDriverManager

using WebDriverManager class in Selenium WebDriver

total-qa    February 9, 2019 September 21, 2020    No Comments on using WebDriverManager class in Selenium WebDriver

Selenium WebDriver automation tool is mainly useful to run tests against multiple Browsers such as Chrome Browser,Firefox Browser,Internet Explorer Driver.Running the tests against multiple browsers is known as Cross Browser Testing.
To launch the Browser in Selenium WebDriver we need to set the path of the executable available in the laptop. Following that we have to instantiate the driver instance based on the Driver instance. In order to avoid these steps we can use the WebDriverManager class.

WebDriverManager

WebDriverManager allows to automate the management of the binary drivers (e.g. chromedriver, geckodriver, etc.) required by Selenium WebDriver.
Using WebDriverManager its not required to maintain the below lines of the code for launching the browser.

System.setProperty(“webdriver.chrome.driver”, “executable path”);
System.setProperty(“webdriver.gecko.driver”, “executable path”);
System.setProperty(“webdriver.opera.driver”, “executable path”);
System.setProperty(“phantomjs.binary.path”, “executable path”);
System.setProperty(“webdriver.edge.driver”, “executable path”);
System.setProperty(“webdriver.ie.driver”, “executable path”);

WebDriverManager Maven Depdendency

To use the WebDriverManager class ensure the following depedency is added in the maven project object model (pom.xml) file.

<dependency> <groupId>io.github.bonigarcia</groupId> <artifactId>webdrivermanager</artifactId> <version>3.2.0</version> </dependency>

1
2
3
4
5

<dependency>
       <groupId>io.github.bonigarcia</groupId>
<artifactId>webdrivermanager</artifactId>
<version>3.2.0</version>
</dependency>

Like our Facebook Page to get frequent updates->

https://www.facebook.com/totalqa

Selenium WebDriver Code

Execute the below code in eclipse and verify the results.

import org.openqa.selenium.WebDriver; import org.openqa.selenium.chrome.ChromeDriver; import org.testng.Assert; import org.testng.annotations.Test; import io.github.bonigarcia.wdm.WebDriverManager; public class GoogleTests { @Test public void verifyTitle() { WebDriverManager.chromedriver().setup(); WebDriver driver = new ChromeDriver(); driver.get("http://www.total-qa.com"); String actual = driver.getTitle(); String expected="Total-QA - Future of Software Testing"; Assert.assertEquals(actual,expected); } }

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.testng.Assert;
import org.testng.annotations.Test;
import io.github.bonigarcia.wdm.WebDriverManager;

public class GoogleTests {

@Test
public void verifyTitle()
{

WebDriverManager.chromedriver().setup();
WebDriver driver = new ChromeDriver();
driver.get("http://www.total-qa.com");
String actual = driver.getTitle();
String expected="Total-QA - Future of Software Testing";
Assert.assertEquals(actual,expected);
}
}

JAVA, Selenium    AbstractClass, IllegalStateException, SelenniumWebdriver, SessionNotCreatedException, WebDriverManager

Posts pagination

« Previous 1 2 3 4 5 … 10 Next »