Selenium Project Setup :

Prerequisite for Converting a Selenium Project in to Maven Project:

1. Elipse IDE
2. Java SE 8
3. TestNg Framework
4. Windows 10 64bits/Mac
5. Chrome, Firefox, IE driver.

Set Up Eclipse and Selenium :

Install Java JDK SE 8 for Windows x64 :

Go to the Java SE Development Kit page and download the Windows x64 version. After finishing downloading, install Java JDK and configure the Java system variables.

Install Eclipse IDE for Java Developers :

Go to the Eclipse IDE Downloads page and download the 64-bit version for Java Developers. Unzip the Eclipse package in a folder of your choice. We encourage you to use "c:\eclipse".

Download Chrome Driver/Firefox Driver/IE Driver :

In order to automate test cases using Google Chrome/Firefox web browser, you should download Chrome/Firefox Driver. Go to the Chrome Driver download/Firefox Driver downloads page and select the latest version. After downloading the package, unzip it once again in a folder of your choice.Put it on "broswersetup" folder in the project.

Note : On the basis of your machine download browser driver, if windows machine(.exe) file and also for Mac download.

Maven Setup:

Step 1: To setup Maven, download the maven’s latest version form Apache depending upon different OS.

Step 2: Unzip the folder and save it on the local disk.

Step 3: Create environment variable for MAVEN_HOME. Follow the below step:

Navigate to System Properties ->Advanced System Settings>Environment Variable ->System Variable ->New ->Add path of Maven folder

Step 4: Edit path variable and provide the bin folder path.

Step 5: Now verify the maven installation using command prompt and don’t forget to setup                JAVA_HOME.

 Use mvn –version to verify maven version and output comes like below.

Install maven IDE in Eclipse:

Maven provides IDE to integrate with eclipse. I am using eclipse Juno here.

Navigate to Help->Eclipse Marketplace-> Search maven ->Maven Integration for Eclipse ->INSTALL

After installation, you have to restart eclipse.

Then right-click on pom.xml and verify all the options are available like below.  

Import Maven project:

1. Download project source code and unzip it into a folder location. Lets assume that we have the Maven project on D:\abc\Workspace.
2. From Eclipse, Project Explorer -> Right click -> Select Import Menu and Import.
3. Expand Maven menu And click Existing Maven Projects.

1. Click next and browse the location where you have the Maven project source code. (browse  the project location in your machine)
2. Click next, Eclipse will recognize the Maven project and it will show you a list of all possible Maven projects located there.

1. Just select the project and click next.
2. Eclipse will show you a Maven Build message. Just click finish.
3. The Maven project is successfully imported into Eclipse IDE.

Build the Project:

The project can be built by both using IDE and command prompt.

Using IDE you have to right click on POM-Run As-Maven Build(Give name as test in Goals).

1. Enter goals like clean install etc. and click Run.
2. Same can be done using a command prompt. Navigate to project folder where pom.xml lies.
3. And use below commands to clean, compile and install

• For clean: mvn clean
• For compile: mvn compile
• For Install: mvn install
• Below is the info which is displayed when you clean any project and shows “BUILD SUCCESS”.

Project Description :

CommonUtilies Package :

1.  BasePage.java                                                                                                                                       In this class we created General methods which can be used any of the projects and for reading elements we are using Fluent Wait.

Fluent Wait :

When using the FluentWait instance, we can specify:

1. The frequency with which FluentWait has to check the conditions defined.
2. Ignore specific types of exception waiting such as NoSuchElementExceptions while searching for an element on the page.
3. The maximum amount of time to wait for a condition.  

2. Data_Provider.java :

       Data Provider methods which can receive two types of parameters methods. This is useful if you want to use the same Data Provider but want different data sets returned, based on the test method being invoked or the test suite/test type it belongs to.You can specify just the method parameter or both the parameters. Based on the parameters used, TestNg will set the parameter values before invoking the  Data Provider method.

3. ExcelReaderExpected.java :

      In this class we Reading the Excel file to input the data in text field or matching the Results.

4. GenericsMethods.java :

       In this class we are reading the Properties.file(key value pairs format) and implemented Robot class to upload file.

5. JSONReader.java :

       In this class we are reading the .json file for UI web pages elements and page url.

6. Listner.java :

    In this class we integrate Listener class,  Listeners are required to generate logs or customize TestNG reports in Selenium Webdriver.

• There are many types of listeners and can be used as per requirements.Listeners are interfaces used in selenium web driver script
• Demonstrated the use of Listener in Selenium
• Implemented the Listeners for multiple classes

7. Log4jReport.java :

What is log4j ?

 Log4j is an open source logging framework. With log4j – logging behavior can be controlled by editing a configuration file only without touching the application binary and can be used to store the Selenium Automation flow logs. It equips the user with detailed context for application failures.

log4j has 3 major components:

Loggers – It is used for logging information. To use loggers we need to take care of things mentioned below:

1. Create object of logger class: Logger class is a Java-based utility which has all the generic methods in it to use log4j (To use Logger class we need to Import org.apache.log4j.Logger)
2. Define the log level: We can define the log levels in multiple forms and levels available are:
1. All – This level of logging will log everything, it is intended to turn on all logging.
2. DEBUG – It saves the debugging information and is most helpful to debug an application.
3. INFO – It prints informational message that highlights the progress of the application.
4. WARN – It designates potentially harmful situations.
5. ERROR – It designates error events that might still allow the application to continue running.
6. FATAL – It designates very severe error events that will presumably lead the application to crash
7. OFF – It is intended to turn off logging.

Appenders – In log4j, an output destination is called an appender. It allows the destination where the logs would get saved. It supports the following types of appenders:-

1. ConsoleAppender – It logs to some standard output.
2. File appender – It prints logs to some file at a particular destination.
3. Rolling file appender – It is used to for a log file with maximum size.

Layouts – It is used to format the logging information in different style.

8. ProjectSetup.java :

  In this class we setup the project ,on which browser we need to run the code and url set up.

Note For windows machine we need to give this path for browser driver:

1. Chromedriver : System.setProperty("webdriver.chrome.driver",
   System.getProperty("user.dir")+ "/broswersetup/chromedriver");
2. Frefoxdriver:System.setProperty("webdriver.gecko.driver",         System.getProperty("user.dir") + "/broswersetup/geckodriver.exe");

9. ProfileSetUp.properties:

In this properties file ,we set up the url and in which browser we want to run the code.

10. HomePage.java :

 In this class , we are creating methods for the UI elements present in the home page and reading the elements from the .json file.

JSON.FILE :

11. TestSnapdeal.java :

It is the test class where we can run the code for the application or pages, here we integrate testNg parameters to run the code.

Notice the following. 

• TestNG does not require you to have a main() method.
• Methods need not be static.
• We used the @Test annotation. @Test is used to tell that the method under it is a test case. In this case, we have set the verifyHomepageTitle() method to be our test case, so we placed an '@Test' annotation above it.
• Since we use annotations in TestNG, we needed to import the package org.testng.annotations.*.
• We used the Assert class. The Assert class is used to conduct verification operations in TestNG. To use it, we used the SoftAssertions for customise reporting.

You may have multiple test cases (therefore, multiple @Test annotations) in a single TestNG file. This will be tackled in more detail later in the section "Annotations used in TestNG." 

Running the Test

To run the test, simply run the file in Eclipse as you normally do. Eclipse will provide two outputs – one in the Console window and the other on the TestNG Results window. 

Checking reports created by TestNG

The Console window in Eclipse gives a text-based report of our test case results while the TestNG Results window gives us a graphical one. 

Generating HTML Reports

TestNG has the ability to generate reports in HTML format. 

Step 1: After running our FirstTestNGFile that we created in the previous section, right-click the project name (FirstTestNGProject) in the Project Explorer window then click on the "Refresh" option. 

Step 2: Notice that a "test-output" folder was created. Expand it and look for an index.html file. This HTML file is a report of the results of the most recent test run. 

Step 3: Double-click on that index.html file to open it within Eclipse's built-in web browser. You can refresh this page any time after you rerun your test by simply pressing F5 just like in ordinary web browsers. 

For Complete Code : https://github.com/arunksahoo/AutomationFramework

For understang of Framework Designing : https://www.linkedin.com/pulse/hybrid-framework-designing-usingpom-data-driven-arun-sahoo/
or https://seleniumautomation-by-arun.blogspot.com

Hybrid Framework Designing by using(POM, Data Driven and Keyword-Driven) :

Why POM?

Page Object Model Framework has nowadays become very popular test automation framework in the industry and many companies are using it because of its easy test maintenance and reduces the duplication of code. 

The main advantage of Page Object Model is that if the UI changes for any page, it doesn’t require us to change any tests, we just need to change only the code within the page objects (Only at one place). Many other tools which are using selenium, are following the page object model.

As you can observe, all we are doing is finding elements and filling values for those elements. 

This is a small script. Script maintenance looks easy. But with time test suite will grow. As you add more and more lines to your code, things become tough. 

The main problem with script maintenance is that if 10 different scripts are using the same page element, with any change in that element, you need to change all 10 scripts. This is time-consuming and error-prone. 

A better approach to script maintenance is to create a separate class file which would find web elements, fill them or verify them. This class can be reused in all the scripts using that element. In future, if there is a change in the web element, we need to make the change in just 1 class file and not 10 different scripts. 

This approach is called Page Object Model(POM). It helps make the code more readable, maintainable, and reusable.

What is POM?

• Page Object Model is a design pattern to create the Object Repository for web UI elements.
• Under this model, for each web page in the application, there should be a corresponding page class.
• This Page class will find the WebElements of that web page and also contains Page methods which perform operations on those WebElements.  
• 

What is Page Object Model Design Patten (POM):

• Page Object Model is a Design Pattern which has become popular in Selenium Test Automation. It is widely used design pattern in Selenium for enhancing test maintenance and reducing code duplication. Page object model (POM) can be used in any kind of framework such as modular, data-driven, keyword driven, hybrid framework etc.  A page object is an object-oriented class that serves as an interface to a page of your Application Under Test(AUT). The tests then use the methods of this page object class whenever they need to interact with the User Interface (UI) of that page. The benefit is that if the UI changes for the page, the tests themselves don’t need to change, only the code within the page object needs to change. Subsequently, all changes to support that new UI is located in one place.

What is Page Factory:

We have seen that "Page Object Model" is a way of representing an application in a test framework. For every "page" in the application, we create a Page Object to reference the "page" whereas a "Page Factory" is one way of implementing the "Page Object Model".

What is the difference between Page Object Model (POM) and Page Factory:

Page Object is a class that represents a web page and hold the functionality and members.
Page Factory is a way to initialize the web elements you want to interact with within the page object when you create an instance of it.

Advantages of Page Object Model Framework:

• Code reusability – We could achieve code reusability by writing the code once and use it in different tests.
• Code maintainability – There is a clean separation between test code and page specific code such as locators and layout which becomes very easy to maintain code. Code changes only on Page Object Classes when a UI change occurs. It enhances test maintenance and reduces code duplication.
• Object Repository – Each page will be defined as a java class. All the fields in the page will be defined in an interface as members. The class will then implement the interface.
• Readability – Improves readability due to the clean separation between test code and page specific code.

Creating a Page Object Model with Page Factory in Selenium WebDriver:

Here I will take the Snapdeal Application to showcase implementation of Page Object Model Design Pattern with Page Factory using Selenium with Java.

Scenario: Navigate to snapdeal URL then verify if SignIn button is present or not, search product in product search bar.

Complete Code : https://github.com/arunksahoo/AutomationFramework