Author: vibssingh

vibssingh

How to handle multiple windows in Robot Framework 

Last Updated On

HOME

In this tutorial, we will automate the switching of Windows in Robot Framework.

Table of Contents

  1. Prerequisite
  2. Implementation Steps
    1. Create a new Python Project
  3. How to create a test to automate the switching of the windows in Robot Framework?
    1. Create a new directory in the new project
    2. Download ChromeBinaries from the below location
    3. Automate the switching of windows
    4. Execute the tests
    5. View Report and Log
  4. Multiple Window Switch
    1. Execute the tests
    2. View Report and Log

    Prerequisite:

    1. Install Python
    2. Install PIP
    3. Install Robot Framework
    4. Install Robot framework Selenium Library
    5. Install PyCharm IDE

    Please refer to this tutorial to install Robot Framework – How to install and setup Robot Framework for Python.

    Implementation Steps:

    Step 1 – Create a new Python Project

    Step 1.1 – Open PyCharm and create a new project. Go to File and select New Project from the main menu.

    Step 1.2 – Choose the project location. Click the “Browse” button next to the Location field and specify the directory for your project.

    Deselect the Create a main.py welcome script checkbox because you will create a new Python file for this tutorial.

    Click on the “Create” Button.

    Step 1.3 – A new dialog appears asking to open the project using any one of the given options. I have selected New Window as I like to have separate windows for each project.

    Below is the image of the new project created in PyCharms.

    How to create a test to automate the switching of the windows in Robot Framework?

    Step 2 – Create a new directory in the new project

    Right-Click on the project, select New->Directory and provide name as Tests

    Below is the image of the new directory.

    Right-click on the new directory and select New File and provide the name as SwitchWindow_Demo.robot as shown below:

    Step 3 – Download ChromeBinaries from the below location

    The tests are going to use the Chrome browser, so we need to download the ChromeBinaries to open a blank browser in Chrome. Similarly, you can use Firefox, edge, safari, and many more browsers.

    https://chromedriver.chromium.org/

    The chromedriver and geckodriver are placed in a folder name drivers in the RobotFramework_Demo project. I have renamed chromedriver to Chrome and geckodriver to Firefox.

    Step 4 – Automate the switching of windows

    We are now going to write test cases. The test case details will be as follows −

    To work with Windows, we need a locator. A locator is an identifier for the textbox like id, name, class, xpath, css selector, etc.

    To know more about locators, refer to these Selenium Tutorials:

     Locators in Selenium – Locate by ID, ClassName,  Name, TagName,  LinkText, PartialLinkText

    Dynamic XPath  in Selenium WebDriver

    CSS Selector in Selenium WebDriver

    The below page shows that when we click on “Open New Separate Windows”, then click on the “click” button, a new child window opens – Selenium.dev.

    Let us inspect the locator of the NEW Window.

    Below is an example of switching windows in Robot Framework.

    *** Settings ***
Documentation    To validate the switching of windows
Library     SeleniumLibrary
Test Teardown    Close Browser

*** Variables ***
${mainPageText}    xpath://div[@class='col-sm-8 col-xs-8 col-md-8']/h1

*** Test Cases ***
Switch windows
    Open the Browser with URL
    Select the button to switch to child window
    Verify the child window is opened
    Verify the user is switched back to parent window

*** Keywords ***
Open the Browser with URL
    Create Webdriver    Chrome  executable_path=/Vibha_Personal/RobotFramework/drivers/chromedriver_linux64
    Go To    https://demo.automationtesting.in/Windows.html
    Maximize Browser Window
    Set Selenium Implicit Wait    2

Select the button to switch to child window
    Click Element    xpath://div[@class='tabpane pullleft']/ul/li[2]/a
    Click Button    css:.btn-primary


Verify the child window is opened
    Switch Window    NEW
    Page Should Contain    Selenium automates browsers


Verify the user is switched back to parent window
     Switch Window    MAIN
     Element Text Should Be     ${mainPageText}    Automation Demo Site

    All the below-mentioned keywords are derived from SeleniumLibrary. The functionality of keywords mentioned above:

    1. Create Webdriver − The keyword creates an instance of Selenium WebDriver.

    2. Go To – This keyword navigates the current browser window to the provided URL – https://demo.automationtesting.in/Windows.html.

    3. Maximize Browser Window – This keyword maximizes the current browser window.

    4. Set Selenium Implicit Wait – This keyword sets the implicit wait value used by Selenium.

    5. Click Element − This keyword is used to click the element identified by the locator. In this case, it is “Open new seperate windows” link.

    6. Click Button – This keyword is used to click the button identified by the locator. In this case, it is “Click” button.

    7. Switch Window NEW – This keyword is used to switch to the latest opened window.

    8. Page Should Contain – This keyword is used to verify that the current page contains the text specified. Here, we are checking if the newly opened windows contain the text “Selenium automates browsers”.

    9. Switch Window MAIN – This keyword is used to switch to the main window.

    10. Element Text Should Be – This keyword is used to verify that the current page contains the exact text identified by the locator. Here, we are checking if we switched back to the main window and the main window contains the exact text “Automation Demo Site”.

    These keywords are present in SeleniumLibrary. To know more about these keywords, please refer to this document – https://robotframework.org/SeleniumLibrary/SeleniumLibrary.html.

    Step 5 – Execute the tests

    To run this script, go to the command line and go to directory tests. We need the below command to run the Robot Framework script.

    robot SwitchWindow_Demo.robot

    The output of the above program is

    Step 5 – View Report and Log

    We have the test case passed. The Robot Framework generates log.html, output.xml, and report.html by default.

    Let us now see the report and log details.

    Report

    Right-click on report.html. Select Open In->Browser->Chrome(any browser of your wish).

    The Report generated by the framework is shown below:

    Log

    Robot Framework has multiple log levels that control what is shown in the automatically generated log file. The default Robot Framework log level is INFO.

    Right-click on log.html. Select Open In->Browser->Chrome(any browser of your wish).

    Multiple Window Switch

    Selenium WebDriver assigns an alphanumeric id to each window as soon as the WebDriver object is instantiated. This unique alphanumeric id is called a window handle. Selenium uses this unique id to switch control among several windows. In simple terms, each unique window has a unique ID, so that Selenium can differentiate when it is switching controls from one window to the other.

    The below page shows that when we click on “Open Separate Multiple Windows”, then click on the “click” button, 2 new child windows open – Selenium.dev and Demo page.

    Below is an example of switching between multiple windows.

    *** Settings ***
Documentation    To validate the switching between multiple windows
Library     SeleniumLibrary
Test Teardown    Close Browser

*** Variables ***
${mainPageText}    xpath://div[@class='col-sm-8 col-xs-8 col-md-8']/h1

*** Test Cases ***
Multiple Windows switch
    Open the Browser with URL
    Select the button to switch to child window
    Verify child windows are opened
    Verify user switched back to parent window

*** Keywords ***
Open the Browser with URL
    Create Webdriver    Chrome  executable_path=/Vibha_Personal/RobotFramework/drivers/chromedriver_linux64
    Go To    https://demo.automationtesting.in/Windows.html
    Maximize Browser Window
    Set Selenium Implicit Wait    5

Select the button to switch to child window
    Click Element    xpath://div[@class='tabpane pullleft']/ul/li[3]/a
    Click Button    xpath:.//*[@id='Multiple']/button


Verify child windows are opened
    @{windowHandle}=    Get Window Handles

    Switch Window   title:Selenium
    Page Should Contain     Selenium automates browsers. That's it!

    Switch Window   title:Index
    Page Should Contain Textfield      id:email


Verify user switched back to parent window
     Switch Window    MAIN
     Element Text Should Be     ${mainPageText}    Automation Demo Site

    All the below-mentioned keywords are derived from SeleniumLibrary. The functionality of keywords mentioned above:

    1. Get Window Handles − The keyword returns all child window handles of the selected browser as a list. Here, it will return 3 window handles.

    2. Switch Window title:Selenium – This keyword is used to switch to the window whose title is identified by the locator “Selenium”.

    3. Page Should Contain Textfield – This keyword verifies the text field identified by the locator found from the current page.

    Step 1 – Execute the tests

    We need the below command to run the Robot Framework script.

    robot MultipleWindows_Demo.robot

    The output of the above program is

    Step 2 – View Report and Log

    Report

    Log

    In the log, we can see that Get Window Handles has 3 alphanumeric id.

    That’s it! Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!!

    vibssingh

    Testing of SpringBoot Application with JUnit5

    Last Updated On

    HOME

    In the previous tutorial, I explained about SpringBoot and how to perform Integration testing of SpringBoot Application. In this tutorial, I will explain about the Testing of the SpringBoot Application with JUnit5.

    Table of Contents

    1. Prerequisite
    2. Dependency List
    3. What is SpringBoot Application?
    4. Project Directory Structure
    5. Implementation Steps
      1. Create a source folder – src/test/resources
      2. Add SpringBoot, and JUnit5 dependencies to the project
      3. Create the Test classes
      4. Create an application.properties file in src/test/resources
      5. Run the tests from JUnit5
      6. Run the tests from the Command Line
      7. Surefire Report Generation

    Prerequisite:

    Spring Boot 3.0.4 requires Java 17 and is compatible with and including Java 19. Spring Framework 6.0.6 or above is also required.

    Explicit build support is provided for the following build tools:

    1. Maven – 3.5+
    2. Gradle – 7.x (7.5 or later) and 8.x

    Dependency List

    1. SpringBoot Starter Parent – 3.1.0
    2. Rest Assured – 5.3.0
    3. Java 17
    4. Maven – 3.8.6

    What is SpringBoot Application?

     Spring Boot is an open-source micro-framework that provides Java developers with a platform to get started with an auto-configurable production-grade Spring application. 

    • Comes with embedded HTTP servers like Tomcat or Jetty to test web applications.
    • Adds many plugins that developers can use to work with embedded and in-memory databases easily. Spring allows you to easily connect with database and queue services like Oracle, PostgreSQL, MySQL, MongoDB, Redis, Solr, ElasticSearch, Rabbit MQ, and others.

    Project Directory Structure

    SpringBoot – 3.1.0-SNAPSHOT contains the JUnit 5 dependencies in it as shown in the below image. So, we don’t need to add them explicitly to the build.gradle.

    Implementation Steps

    Step 1 – Create a source folder – src/test/resources

    Create a source folder – src/test/resources to create test scenarios in the Feature file.

    Right-click on the test directory, select New->Directory and select resources (Maven Source Directories).

    Step 2 – Add SpringBoot, and JUnit5 dependencies to the project

    We have added SpringBootTest, and JUnit5 dependencies to pom.xml.

    <?xml version="1.0" encoding="UTF-8"?>
<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 https://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-parent</artifactId>
		<version>3.1.0-SNAPSHOT</version>
		<relativePath/> <!-- lookup parent from repository -->
	</parent>

	<groupId>com.example</groupId>
	<artifactId>SpringBoot_JUnit5_Demo</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>SpringBoot_JUnit5_Demo</name>
	<description>Demo project for Spring Boot</description>

	<properties>
		<java.version>17</java.version>
		<junit-jupiter.version>5.9.2</junit-jupiter.version>
		<rest.assured.version>5.3.0</rest.assured.version>
		<maven.compiler.plugin.version>3.10.1</maven.compiler.plugin.version>
		<maven.compiler.source.version>17</maven.compiler.source.version>
		<maven.compiler.target.version>17</maven.compiler.target.version>
		<maven.surefire.plugin.version>3.0.0-M9</maven.surefire.plugin.version>
		<maven.failsafe.plugin.version>3.0.0-M9</maven.failsafe.plugin.version>
		<maven.site.plugin.version>3.12.0</maven.site.plugin.version>
		<maven.surefire.report.plugin.version>3.0.0-M6</maven.surefire.report.plugin.version>
	</properties>

	<dependencies>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter</artifactId>
		</dependency>

		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-test</artifactId>
			<scope>test</scope>
		</dependency>

		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-web</artifactId>
		</dependency>

		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-tomcat</artifactId>
			<scope>provided</scope>
		</dependency>

		<dependency>
			<groupId>org.springframework</groupId>
			<artifactId>spring-web</artifactId>
		</dependency>

		<!-- Rest Assured -->
		<dependency>
			<groupId>io.rest-assured</groupId>
			<artifactId>rest-assured</artifactId>
			<version>${rest.assured.version}</version>
			<scope>test</scope>
		</dependency>


	</dependencies>

	<build>
		<plugins>
			<plugin>
				<groupId>org.springframework.boot</groupId>
				<artifactId>spring-boot-maven-plugin</artifactId>
				<version>3.0.4</version>
			</plugin>

			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-site-plugin</artifactId>
				<version>${maven.site.plugin.version}</version>
			</plugin>

			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-surefire-plugin</artifactId>
				<version>${maven.surefire.plugin.version}</version>
				<configuration>
					<testFailureIgnore>true</testFailureIgnore>
				</configuration>
			</plugin>
			
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-compiler-plugin</artifactId>
				<version>${maven.compiler.plugin.version}</version>
				<configuration>
					<source>${maven.compiler.source.version}</source>
					<target>${maven.compiler.target.version}</target>
				</configuration>

			</plugin>
		</plugins>
	</build>
	
	<reporting>
		<plugins>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-surefire-report-plugin</artifactId>
				<version>${maven.surefire.report.plugin.version}</version>
			</plugin>
		</plugins>
	</reporting>

	<repositories>
		<repository>
			<id>spring-milestones</id>
			<name>Spring Milestones</name>
			<url>https://repo.spring.io/milestone</url>
			<snapshots>
				<enabled>false</enabled>
			</snapshots>
		</repository>
		<repository>
			<id>spring-snapshots</id>
			<name>Spring Snapshots</name>
			<url>https://repo.spring.io/snapshot</url>
			<releases>
				<enabled>false</enabled>
			</releases>
		</repository>
	</repositories>
	
	<pluginRepositories>
		<pluginRepository>
			<id>spring-milestones</id>
			<name>Spring Milestones</name>
			<url>https://repo.spring.io/milestone</url>
			<snapshots>
				<enabled>false</enabled>
			</snapshots>
		</pluginRepository>
		
		<pluginRepository>
			<id>spring-snapshots</id>
			<name>Spring Snapshots</name>
			<url>https://repo.spring.io/snapshot</url>
			<releases>
				<enabled>false</enabled>
			</releases>
		</pluginRepository>
	</pluginRepositories>

</project>

    Step 3 – Create the Test classes

    • uses @SpringBootTest annotation which loads the actual application context.
    • uses WebEnvironment.RANDOM_PORT to create and run the application at some random server port.
    • @LocalServerPort gets the reference of the port where the server has started. It helps in building the actual request URIs to mimic real client interactions.

    Below is the code of the Test class. These classes are created in the src/test/java directory.

    import io.restassured.response.ValidatableResponse;
import org.junit.jupiter.api.Assertions;
import org.junit.jupiter.api.Test;
import org.springframework.beans.factory.annotation.Value;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.boot.test.web.server.LocalServerPort;
import static io.restassured.RestAssured.given;

@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
public class SpringBootDemoTests {

    private final static String BASE_URI = "http://localhost:";

    @LocalServerPort
    private int port;

    @Value("${server.servlet.context-path}")
    private String basePath;

    private ValidatableResponse response;

    @Test
    public void verifyController1() throws Exception  {
         response = given().contentType("application/json")
                    .header("Content-Type", "application/json")
                 .when().get(BASE_URI + port + basePath+ "/").then().statusCode(200);

         String Actual = response.extract().asString();
          System.out.println("Result :"+Actual);
          Assertions.assertEquals("Hello World, Spring Boot!", Actual);
    }

    @Test
    public void verifyController2() throws Exception  {
        response = given().contentType("application/json")
                .header("Content-Type", "application/json")
                .when().get(BASE_URI + port + basePath+ "/qaautomation").then().statusCode(200);

        String Actual = response.extract().asString();
        System.out.println("Result :"+Actual);
        Assertions.assertEquals("Hello QA Automation!", Actual);
    }
}

    This class sends the request and receives a response after performing the GET operation. Here, the validation of the response also takes place by asserting the expected and actual response

    Step 4 – Create an application.properties file in src/test/resources

    Application.properties is created under src/test/java. 

    spring.profiles.active=test
server.port=8089
server.servlet.context-path=/demo

    spring.profiles.active – property to specify which profiles are active. The default profile is always active.
    server.port – By default, the embedded server starts on port 8080. Now the server will start on port 8089
    server.servlet.context-path – the context path in Spring Boot can be changed by setting a property, server.servlet.context-path.

    Step 5 – Run the tests from JUnit5

    Right-click on the Test class and select Run ‘SpringBootDemoTests’.

    The output of the above program is

    Below is the execution log.

    This image shows that the profile name is “test”. Application is started on port – “64733” and the context path is “/demo”.

    Step 6 – Run the tests from the Command Line

    Run the tests from the command line by using the below command

    mvn clean test site

    The output of the above program is

    Step 7 – Surefire Report Generation

    The test report generated by JUnit is placed under target/site/index.html.

    Below is the sample Surefire Report.

    Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!! Cheers!!

    vibssingh

    How to handle dropdowns in Robot Framework 

    Last Updated On

    HOME

    In this tutorial, we will automate the execution of DropDown in Robot Framework.

    Table of Contents

    1. Prerequisite
    2. Implementation Steps
    3. How to create a test to automate the options of dropdown in Robot Framework?
      1. Create a new directory in the new project
      2. Download ChromeBinaries from the below location
      3. Automate the selection of options for DropDown
      4. Execute the tests
      5. View Report and Log

    Prerequisite:

    1. Install Python
    2. Install PIP
    3. Install Robot Framework
    4. Install Robot framework Selenium Library
    5. Install PyCharm IDE

    Please refer to this tutorial to install Robot Framework – How to install and setup Robot Framework for Python.

    Implementation Steps:

    Step 1.1 – Open PyCharm and create a new project. Go to File and select New Project from the main menu.

    Step 1.2 – Choose the project location. Click the “Browse” button next to the Location field and specify the directory for your project.

    Deselect the Create a main.py welcome script checkbox because you will create a new Python file for this tutorial.

    Click on the “Create” Button.

    Step 1.3 – A new dialog appears asking to open the project using any one of the given options. I have selected New Window as I like to have separate windows for each project.

    Below is the image of the new project created in PyCharms.

    How to create a test to automate the options of dropdown in Robot Framework?

    Step 4 – Create a new directory in the new project

    Right-Click on the project, select New->Directory and provide name as Tests

    Below is the image of the new directory.

    Right-click on the new directory and select New File and provide the name as DropDown_Demo.robot as shown below:

    Step 5 – Download ChromeBinaries from the below location

    The tests are going to use the Chrome browser, so we need to download the ChromeBinaries to open a blank browser in Chrome.

    https://chromedriver.chromium.org/

    The chromedriver and geckodriver are placed in a folder name drivers in the RobotFramework_Demo project. I have renamed chromedriver to Chrome and geckodriver to Firefox.

    Step 6 – Automate the selection of options for DropDown

    We are now going to write test cases. The test case details will be as follows −

    To work with the Radio Button, we need a locator. A locator is an identifier for the textbox like id, name, class, xpath, css selector, etc.

    To know more about locators, refer to these Selenium Tutorials:

     Locators in Selenium – Locate by ID, ClassName,  Name, TagName,  LinkText, PartialLinkText

    Dynamic XPath  in Selenium WebDriver

    CSS Selector in Selenium WebDriver

    The below page shows that we have multiple DropDown options.

    Let us inspect the locator of DropDown.

    Below is an example of selecting the options in DropDown.

    *** Settings ***
Documentation    To validate the selection of DropDown
Library     SeleniumLibrary
Test Teardown    Close Browser

*** Test Cases ***
Select options in DropDown
    Open the Browser with URL
    Select the dropdown options APIs by value
    Select the dropdown options Microsoft Excel by index
    Select the dropdown options CSS by label

*** Keywords ***
Open the Browser with URL
    Create Webdriver    Chrome  executable_path=/Vibha_Personal/RobotFramework/drivers/chromedriver_linux64
    Go To    https://demo.automationtesting.in/Register.html
    Maximize Browser Window
    Set Selenium Implicit Wait    2

Select the dropdown options APIs by value
    Select From List By Value       id:Skills   APIs


Select the dropdown options Microsoft Excel by index
    Select From List By Index        id:Skills   43

Select the dropdown options CSS by label
    Select From List By Label       id:Skills   CSS

    All the below-mentioned keywords are derived from SeleniumLibrary except the last one. The functionality of keywords mentioned above:

    1. Create Webdriver − The keyword creates an instance of Selenium WebDriver.

    2. Go To – This keyword navigates the current browser window to the provided URL – https://demo.automationtesting.in/Register.html.

    3. Maximize Browser Window – This keyword maximizes the current browser window.

    4. Set Selenium Implicit Wait – This keyword sets the implicit wait value used by Selenium.

    5. Select From List By Value − This keyword is used to select APIs option from dropdown on the current page by value.

    6. Select From List By Index – This keyword is used to select Microsoft Excel option from dropdown on the current page by index.

    7. Select From List By Label – This keyword is used to select CSS option from the dropdown on the current page by label.

    These keywords are present in SeleniumLibrary. To know more about these keywords, please refer to this document – https://robotframework.org/SeleniumLibrary/SeleniumLibrary.htm.

    To run this script, go to the command line and go to directory tests.

    Step 7 – Execute the tests

    We need the below command to run the Robot Framework script.

    robot DropDown_Demo.robot

    The output of the above program is

    Step 8 – View Report and Log

    We have the test case passed. The Robot Framework generates log.html, output.xml, and report.html by default.

    Let us now see the report and log details.

    Report

    Right-click on report.html. Select Open In->Browser->Chrome(any browser of your wish).

    The Report generated by the framework is shown below:

    Log

    Robot Framework has multiple log levels that control what is shown in the automatically generated log file. The default Robot Framework log level is INFO.

    Right-click on log.html. Select Open In->Browser->Chrome(any browser of your wish).

    That’s it! Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!!

    vibssingh

    How to handle radio buttons in Robot Framework 

    HOME

    In this tutorial, we will automate the execution of the Radio Button in Robot Framework.

    Prerequisite:

    1. Install Python
    2. Install PIP
    3. Install Robot Framework
    4. Install Robot framework Selenium Library
    5. Install PyCharm IDE

    Please refer to this tutorial to install Robot Framework – How to install and setup Robot Framework for Python.

    Implementation Steps:

    Step 1.1 – Open PyCharm and create a new project. Go to File and select New Project from the main menu.

    Step 1.2 – Choose the project location. Click the “Browse” button next to the Location field and specify the directory for your project.

    Deselect the Create a main.py welcome script checkbox because you will create a new Python file for this tutorial.

    Click on the “Create” Button.

    Step 1.3 – A new dialog appears asking to open the project using any one of the given options. I have selected New Window as I like to have separate windows for each project.

    Below is the image of the new project created in PyCharms.

    Step 2 – Create a new directory in the new project

    Right-Click on the project, select New->Directory and provide name as Tests

    Below is the image of the new directory.

    Step 3 – Create a robot Test File

    Right-click on the new directory and select New File and provide the name as RadioButton_Demo.robot as shown below:

    Step 4 – Download ChromeBinaries from the below location

    The tests are going to use the Chrome browser, so we need to download the ChromeBinaries to open a blank browser in Chrome.

    https://chromedriver.chromium.org/

    The chromedriver and geckodriver are placed in a folder name drivers in the RobotFramework_Demo project. I have renamed chromedriver to Chrome and geckodriver to Firefox.

    Step 5 – Automate the selection of options for Radio Buttons

    We are now going to write test cases. The test case details will be as follows −

    • Open the browser and copy URL − https://demo.automationtesting.in/Register.html in Chrome
    • Verify that the page contains the Radio Buttons.
    • Verify that the page does not contain the Radio Button. Provided the locator for the checkbox
    • Click on “Male” Radio Button
    • Verify that “Male” Radio Button is selected

    To work with the Radio Button, we need a locator. A locator is an identifier for the textbox like id, name, class, xpath, css selector, etc.

    To know more about locators, refer to these Selenium Tutorials:

     Locators in Selenium – Locate by ID, ClassName,  Name, TagName,  LinkText, PartialLinkText

    Dynamic XPath  in Selenium WebDriver

    CSS Selector in Selenium WebDriver

    The below page shows that we have 2 Radio Buttons – Male and FeMale.

    Let us inspect the locator of the Radio Button.

    Below is an example of selecting the “Male” option in Radio Buttons.

    *** Settings ***
Documentation    To validate the Login Form
Library     SeleniumLibrary
Test Teardown    Close Browser

*** Test Cases ***
Select an option of Radio Button
    Open the Browser with URL
    Select impressive option from 3 radio buttons
    Verify that the radio button is selected


*** Keywords ***
Open the Browser with URL
    Create Webdriver    Chrome  executable_path=/Vibha_Personal/RobotFramework_Demo/drivers/chromedriver_linux64
    Go To    https://demo.automationtesting.in/Register.html
    Maximize Browser Window
    Set Selenium Implicit Wait    2


Select impressive option from 3 radio buttons
    Page Should Contain Radio Button    name:radiooptions
    Page Should Not Contain Radio Button    id:checkbox1    #This is checkbox
    Select Radio Button    radiooptions    Male


Verify that the radio button is selected
    Radio Button Should Be Set To    radiooptions    Male

    All the below-mentioned keywords are derived from SeleniumLibrary. The functionality of keywords mentioned above:

    1. Create Webdriver − The keyword creates an instance of Selenium WebDriver.

    2. Go To – This keyword navigates the current browser window to the provided URL – https://demo.automationtesting.in/Register.html.

    3. Maximize Browser Window – This keyword maximizes the current browser window.

    4. Set Selenium Implicit Wait – This keyword sets the implicit wait value used by Selenium.

    5. Page Should Contain Radio Button − This keyword is used to find the radio buttons that are located on the current page.

    6. Page Should Not Contain Radio Button – This keyword is used to find that the radio buttons are not locator on the current page.

    7. Select Radio Button – This keyword is used to click on the “Male” option of the radio buttons.

    8. Radio Button Should Be Set To – This keyword verifies if the radio button “Male” is selected or not.

    These keywords are present in SeleniumLibrary. To know more about these keywords, please refer to this document – https://robotframework.org/SeleniumLibrary/SeleniumLibrary.htm.

    To run this script, go to the command line and go to directory tests.

    Step 6 – Execute the tests

    We need the below command to run the Robot Framework script.

    robot RadioButton_Demo.robot

    The output of the above program is

    Step 7 – View Report and Log

    We have the test case passed. The Robot Framework generates log.html, output.xml, and report.html by default.

    Let us now see the report and log details.

    Report

    Right-click on report.html. Select Open In->Browser->Chrome(any browser of your wish).

    The Report generated by the framework is shown below:

    Log

    Robot Framework has multiple log levels that control what is shown in the automatically generated log file. The default Robot Framework log level is INFO.

    Right-click on log.html. Select Open In->Browser->Chrome(any browser of your wish).

    That’s it! Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!!

    vibssingh

    What is Resource File in Robot Framework 

    HOME

    What is Resource File?

    In Robot Framework, a resource file is a file that contains reusable keywords, variables, and other settings that can be used across multiple test cases or test suites. Resource files are used to organize and centralize common functionality and reduce duplication of effort in test automation.

    Resource files are typically created in plain text format using the .robot file extension. They can include user-defined keywords, as well as built-in keywords and libraries that are imported for use in test cases. Variables can also be defined in resource files, and these variables can be used to store data that is used across multiple test cases.

    Example of Resource File

    *** Settings ***
Documentation    A resource file with reusable keywords and variables.
Library     SeleniumLibrary

*** Variables ***
${valid_username}     Admin
${valid_password}       admin123
${invalid_username}     1234
${invalid_password}     45678
${url}      https://opensource-demo.orangehrmlive.com/web/index.php/auth/login

*** Keywords ***

Open the Browser with URL
    Create Webdriver    Chrome  executable_path=/Vibha_Personal/RobotFramework/drivers/chromedriver_linux64
    Go To       ${url}
    Maximize Browser Window
    Set Selenium Implicit Wait    5

Close Browser Session
    Close Browser

    In this tutorial, we will create a project in PyCharms and show the use of Resource File in Robot Framework

    Prerequisite:

    1. Install Python
    2. Install PIP
    3. Install Robot Framework
    4. Install Robot framework Selenium Library
    5. Install PyCharm IDE

    Please refer to this tutorial to install Robot Framework – How to install and setup Robot Framework for Python.

    Implementation Steps:

    Step 1 – Open PyCharm and create a new project. Go to File and select New Project from the main menu.

    Step 2 – Choose the project location. Click the “Browse” button next to the Location field and specify the directory for your project.

    Deselect the Create a main.py welcome script checkbox because you will create a new Python file for this tutorial.

    Click on the Create Button.

    Step 3 – A new dialog will appear asking to Open the project using any one of the given options. I have selected New Window as I like to have separate windows for each project.

    Below is the image of the new project created in PyCharms.

    How to create a test using Resource File in Robot Framework?

    Step 1 – Create a new directory in the new project

    Right-Click on the project, select New->Directory and provide name as PageObject

    Right-click on the new directory and select New File and provide the name as LoginPage.robot and resources.robot as shown below:

    Step 2 – Download ChromeBinaries from the below location

    The tests are going to use the Chrome browser, so we need to download the ChromeBinaries to open a blank browser in Chrome.

    https://chromedriver.chromium.org/

    Step 3 – Create a Test using the Resource file

    We are now going to write 2 test cases. The test case details will be as follows :

    Test 1

    Test 2

    We need locators to identify various web elements on the page.

    To know more about locators, refer to these Selenium Tutorials:

     Locators in Selenium – Locate by ID, ClassName,  Name, TagName,  LinkText, PartialLinkText

    Dynamic XPath  in Selenium WebDriver

    CSS Selector in Selenium WebDriver

    Below is an example of a LoginPage.robot 

    *** Settings ***
Documentation       Tests to login to Login Page
Library     SeleniumLibrary
Resource       resources.robot

*** Variables ***
${Login_Error_Message}      css:.oxd-alert-content--error
${Dashboard_Text}       css:.oxd-topbar-header-breadcrumb-module

*** Test Cases ***

Validate Unsuccessful Login
    Open the Browser with URL
    Fill the login form     ${valid_username}       ${invalid_password}
    verify error message is correct
    Close Browser Session

Validate successful Login
    Open the Browser with URL
    Fill the login form     ${valid_username}       ${valid_password}
    Verify Dashboard page opens
    Close Browser Session

*** Keywords ***

Fill the login form
    [Arguments]    ${username}      ${password}
   Input Text    css:input[name=username]   ${username}
   Input Password    css:input[name=password]   ${password}
   Click Button    css:.orangehrm-login-button


Verify error message is correct
    Element Text Should Be    ${Login_Error_Message}    Invalid credentials

Verify Dashboard page opens
    Element Text Should Be    ${Dashboard_Text}     Dashboard

    As you can see, some keywords are not present in this file. The keywords which we know are going to be common for other test files are placed in a Resource File. We have imported the Resource file by using this command in Settings.

    *** Settings ***
Resource       resources.robot

    Below is an example of the resources.robot file.

    *** Settings ***
Documentation    A resource file with reusable keywords and variables.
Library     SeleniumLibrary

*** Variables ***
${valid_username}     Admin
${valid_password}       admin123
${invalid_username}     1234
${invalid_password}     45678
${url}      https://opensource-demo.orangehrmlive.com/web/index.php/auth/login

*** Keywords ***

Open the Browser with URL
    Create Webdriver    Chrome  executable_path=/Vibha_Personal/RobotFramework/drivers/chromedriver_linux64
    Go To       ${url}
    Maximize Browser Window
    Set Selenium Implicit Wait    5

Close Browser Session
    Close Browser

    All the below-mentioned keywords are derived from SeleniumLibrary. The functionality of keywords mentioned above:

    1. Create Webdriver − The keyword creates an instance of Selenium WebDriver.

    2. Go To – This keyword navigates the current browser window to the provided url.

    3. Maximize Browser Window – This keyword maximizes the current browser window.

    4. Set Selenium Implicit Wait – This keyword sets the implicit wait value used by Selenium.

    5. Input Text − This keyword is used to type the given text in the specified textbox identified by the locator name:username.

    6. Input Password – This keyword is used to type the given text in the specified password identified by the locator name:password.

    The difference compared to Input Text is that this keyword does not log the given password on the INFO level.

    7. Click button – This keyword is used to click on the button with location css:.orangehrm-login-button.

    8. ${result} – This is a variable that holds the text value of the error message that is located by css:.oxd-alert-content-text

    9. Get Text – This keyword returns the text value of the element identified by located by css:.oxd-alert-content-text.

    10. Should Be Equal As Strings – This keyword is used from builtIn keyword. This keyword returns false if objects are unequal after converting them to strings.

    To run this script, go to the command line and go to directory tests.

    We need the below command to run the Robot Framework script.

     robot LoginPage.robot

    The output of the above program is

    We have the test case passed. The Robot Framework generates log.html, output.xml and report.html by default.

    Let us now see the report and log details.

    Report

    Right-click on report.html. Select Open In->Browser->Chrome(any browser of your wish).

    The Report generated by the framework is shown below:

    Log

    Robot Framework has multiple log levels that control what is shown in the automatically generated log file. The default Robot Framework log level is INFO.

    Right-click on log.html. Select Open In->Browser->Chrome(any browser of your wish).

    That’s it! Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!!

    vibssingh

    How to handle text box in Robot Framework 

    HOME

    In this tutorial, we will create a project in PyCharms and enter data in TextBox in Robot Framework

    Prerequisite:

    1. Install Python
    2. Install PIP
    3. Install Robot Framework
    4. Install Robot framework Selenium Library
    5. Install PyCharm IDE

    Please refer to this tutorial to install Robot Framework – How to install and setup Robot Framework for Python.

    Implementation Steps:

    Step 1 – Create a new Project

    Step 1.1 – Open PyCharm and create a new project. Go to File and select New Project from the main menu.

    Step 1.2 – Choose the project location. Click the Browse button next to the Location field and specify the directory for your project.

    Deselect the Create a main.py welcome script checkbox because you will create a new Python file for this tutorial.

    Click on the Create Button.

    Step 1.3 – A new dialog will appear asking to Open the project using any one of the given options. I have selected New Window as I like to have separate windows for each project.

    Below is the image of the new project created in PyCharms.

    Step 2 – Create a new directory in the new project

    Right-Click on the project, select New->Directory and provide name as Tests

    Below is the image of the new directory.

    Step 3 – Create a robot Test File

    Right-click on the new directory and select New File and provide the name as Test_Demo.robot as shown below:

    Step 4 – Download ChromeBinaries from the below location

    The tests are going to use the Chrome browser, so we need to download the ChromeBinaries to open a blank browser in Chrome.

    https://chromedriver.chromium.org/

    The chromedriver and geckodriver are placed in a folder name drivers in the RobotFramework_Demo project. I have renamed chromedriver to Chrome and geckodriver to Firefox.

    Step 5 – Enter Data in Textbox

    We are now going to write test cases. The test case details will be as follows:

    To work with the textbox, we need a locator. A locator is an identifier for the textbox like id, name, class, xpath, css selector, etc.

    To know more about locators, refer to these Selenium Tutorials:

     Locators in Selenium – Locate by ID, ClassName,  Name, TagName,  LinkText, PartialLinkText

    Dynamic XPath  in Selenium WebDriver

    CSS Selector in Selenium WebDriver

    Below is an example of entering data in TextBox.

    *** Settings ***
Documentation    To validate the Login Form
Library     SeleniumLibrary

*** Test Cases ***
Validate Unsuccessful Login
    Open the Browser with URL
    Fill the login form
    Verify error message is correct


*** Keywords ***
Open the Browser with URL
    Create Webdriver    Chrome  executable_path=/Vibha_Personal/RobotFramework_Demo/drivers/chromedriver_linux64
    Go To    https://opensource-demo.orangehrmlive.com/web/index.php/auth/login
    Maximize Browser Window
    Set Selenium Implicit Wait    5

Fill the login form
   Input Text    css:input[name=username]   Admin
   Input Password    css:input[name=password]   Admin
   Click Button    css:.orangehrm-login-button


Verify error message is correct
    ${result}=  Get Text    CSS:.oxd-alert-content-text
    Should Be Equal As Strings   ${result}  Invalid credentials

    All the below-mentioned keywords are derived from SeleniumLibrary except the last one. The functionality of keywords mentioned above:

    1. Create Webdriver − The keyword creates an instance of Selenium WebDriver.

    2. Go To – This keyword navigates the current browser window to the provided url.

    3. Maximize Browser Window – This keyword maximizes the current browser window.

    4. Set Selenium Implicit Wait – This keyword sets the implicit wait value used by Selenium.

    5. Input Text − This keyword is used to type the given text in the specified textbox identified by the locator name:username.

    6. Input Password – This keyword is used to type the given text in the specified password identified by the locator name:password.

    The difference compared to Input Text is that this keyword does not log the given password on the INFO level.

    7. Click button – This keyword is used to click on the button with location css:.orangehrm-login-button.

    8. ${result} – This is a variable that holds the text value of the error message that is located by css:.oxd-alert-content-text

    9. Get Text – This keyword returns the text value of the element identified by located by css:.oxd-alert-content-text.

    10. Should Be Equal As Strings – This keyword is used from builtIn keyword. This keyword returns false if objects are unequal after converting them to strings.

    Step 6 – Execute the tests

    To run this script, go to the command line and go to directory tests.

    We need the below command to run the Robot Framework script.

    robot Test_Demo.robot

    The output of the above program is

    Step 7 – View Report and Log

    We have the test case passed. The Robot Framework generates log.html, output.xml, and report.html by default.

    Let us now see the report and log details.

    Report

    Right-click on report.html. Select Open In->Browser->Chrome(any browser of your wish).

    The Report generated by the framework is shown below:

    Log

    Robot Framework has multiple log levels that control what is shown in the automatically generated log file. The default Robot Framework log level is INFO.

    Right-click on log.html. Select Open In->Browser->Chrome(any browser of your wish).

    In the below image of the log, we can see that the text entered by the user is shown here, whereas the password does not show the value of the password.

    That’s it! Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!!

    vibssingh

    How to handle checkbox in Robot Framework 

    HOME

    In this tutorial, we will automate the execution of the CheckBox in Robot Framework.

    Prerequisite:

    1. Install Python
    2. Install PIP
    3. Install Robot Framework
    4. Install Robot framework Selenium Library
    5. Install PyCharm IDE

    Please refer to this tutorial to install Robot Framework – How to install and setup Robot Framework for Python.

    Implementation Steps:

    Step 1 – Create a new Project

    Step 1.1 – Open PyCharm and create a new project. Go to File and select New Project from the main menu.

    Step 1.2 – Choose the project location. Click the “Browse” button next to the Location field and specify the directory for your project.

    Deselect the Create a main.py welcome script checkbox because you will create a new Python file for this tutorial.

    Click on the “Create” Button.

    Step 1.3 – A new dialog appears asking to open the project using any one of the given options. I have selected New Window as I like to have separate windows for each project.

    Below is the image of the new project created in PyCharms.

    Step 2 – Create a new directory in the new project

    Right-Click on the project, select New->Directory and provide name as Tests

    Below is the image of the new directory.

    Step 3 – Create a robot Test File

    Right-click on the new directory and select New File and provide the name as CheckBox_Demo.robot as shown below:

    Step 4 – Download ChromeBinaries from the below location

    The tests are going to use the Chrome browser, so we need to download the ChromeBinaries to open a blank browser in Chrome.

    https://chromedriver.chromium.org/

    The chromedriver and geckodriver are placed in a folder name drivers in the RobotFramework_Demo project. I have renamed chromedriver to Chrome and geckodriver to Firefox.

    Step 5 – Automate the selection of options for CheckBox

    We are now going to write test cases. The test case details will be as follows −

    • Open the browser and copy URL − https://demo.automationtesting.in/Register.html in Chrome.
    • Verify that the page contains CheckBox.
    • Verify that the page does not contain CheckBox. Provided the locator for Radio button.
    • Check “Cricket” and “Hockey” options of CheckBox.
    • Uncheck “Hockey” option of CheckBox.
    • Verify that “Cricket“ option of CheckBox is checked.
    • Verify that “Hockey“ option of CheckBox is not checked.

    To work with the Radio Button, we need a locator. A locator is an identifier for the textbox like id, name, class, xpath, css selector, etc.

    To know more about locators, refer to these Selenium Tutorials:

     Locators in Selenium – Locate by ID, ClassName,  Name, TagName,  LinkText, PartialLinkText

    Dynamic XPath  in Selenium WebDriver

    CSS Selector in Selenium WebDriver

    The below page shows that we have 3 CheckBoxes – Cricket, Movies, and Hockey.

    Let us inspect the locator of the CheckBox.

    Below is an example of selecting the “Cricket” and “Hockey” options in CheckBox.

    *** Settings ***
Documentation    To validate the Login Form
Library     SeleniumLibrary
Test Teardown    Close Browser

*** Test Cases ***
Select an option of Radio Button
    Open the Browser with URL
    Verifies page contains a checkbox
    Select the checkbox options Cricket and Hockey
    Unselect the checkbox option Hockey
    Verify Checkbox option Cricket is selected
    Verify Checkbox option Hockey is not selected


*** Keywords ***
Open the Browser with URL
    Create Webdriver    Chrome  executable_path=/Vibha_Personal/RobotFramework/drivers/chromedriver_linux64
    Go To    https://demo.automationtesting.in/Register.html
    Maximize Browser Window
    Set Selenium Implicit Wait    2


Verifies page contains a checkbox
    Page Should Contain Checkbox    id:checkbox1
    Page Should Not Contain Checkbox    name:radiooptions   #This is the locator for Radio Button


Select the checkbox options Cricket and Hockey
    Select Checkbox    id:checkbox1
    Select Checkbox    id:checkbox3

Unselect the checkbox option Hockey
    Unselect Checkbox    id:checkbox3

Verify Checkbox option Cricket is selected
    Checkbox Should Be Selected      id:checkbox1

Verify Checkbox option Hockey is not selected
    Checkbox Should Not Be Selected    id:checkbox3

    All the below-mentioned keywords are derived from SeleniumLibrary except the last one. The functionality of keywords mentioned above:

    1. Create Webdriver − The keyword creates an instance of Selenium WebDriver.

    2. Go To – This keyword navigates the current browser window to the provided URL – https://demo.automationtesting.in/Register.html.

    3. Maximize Browser Window – This keyword maximizes the current browser window.

    4. Set Selenium Implicit Wait – This keyword sets the implicit wait value used by Selenium.

    5. Page Should Contain Checkbox − This keyword is used to find the checkbox that is located on the current page.

    6. Page Should Not Contain Checkbox – This keyword is used to find that the checkbox is not locator on the current page.

    7. Select Checkbox – This keyword is used to select options “Cricket” and “Hockey” of the CheckBox.

    8. Unselect Checkbox – This keyword is used to unselect the option “Hockey” of the CheckBox.

    9. Checkbox Should Be Selected – This keyword verifies if the checkbox “Cricket” is checked.

    10. Checkbox Should Not Be Selected – This keyword verifies if the checkbox “Hockey” is not checked.

    These keywords are present in SeleniumLibrary. To know more about these keywords, please refer to this document – https://robotframework.org/SeleniumLibrary/SeleniumLibrary.htm

    To run this script, go to the command line and go to directory tests.

    cd Tests

    Step 6 – Execute the tests

    We need the below command to run the Robot Framework script.

    robot CheckBox_Demo.robot

    The output of the above program is

    Step 7 – View Report and Log

    We have the test case passed. The Robot Framework generates log.html, output.xml, and report.html by default.

    Let us now see the report and log details.

    Report

    Right-click on report.html. Select Open In->Browser->Chrome(any browser of your wish).

    The Report generated by the framework is shown below:

    Log

    Robot Framework has multiple log levels that control what is shown in the automatically generated log file. The default Robot Framework log level is INFO.

    Right-click on log.html. Select Open In->Browser->Chrome(any browser of your wish).

    That’s it! Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!!

    vibssingh

    Testing of SpringBoot Application with Serenity BDD, Cucumber and JUnit5

    Last Updated On

    HOME

    In the previous tutorial, I explained about Integration Testing of Springboot with Cucumber and JUnit4. In this tutorial, I will explain the Testing of the SpringBoot Application in BDD format using Serenity Bdd and Cucumber and JUnit5.

    Table of Contents

    1. What is Serenity BDD?
    2. What is SpringBoot Application?
    3. Dependency List
    4. Project Directory Structure
    5. Relationship between SpringBoot, Serenity BDD, Cucumber, and JUnit5
      1. What is RestController?
    6. Implementation Steps
      1. Create a source folder – src/test/resources 
      2. Add SpringBoot, Serenity, Cucumber, and JUnit5 dependencies to the project
      3. Create a feature file under src/test/resources
      4. Create the StepDefinition and Helper classes
      5. Create a Serenity Runner class in the src/test/java directory
      6. Run the tests from JUnit5
      7. Run the tests from the Command Line
      8. Serenity Report Generation
      9. Cucumber Report Generation

    What is Serenity BDD?

    Serenity BDD is an open-source library that aims to make the idea of living documentation a reality.

    Serenity BDD helps you write cleaner and more maintainable automated acceptance and regression tests faster. Serenity also uses the test results to produce illustrated, narrative reports that document and describe what your application does and how it works. Serenity tells you not only what tests have been executed, but more importantly, what requirements have been tested.

    What is SpringBoot Application?

     Spring Boot is an open-source micro framework that provides Java developers with a platform to get started with an auto-configurable production-grade Spring application. 

    • Comes with embedded HTTP servers like Tomcat or Jettyto test web applications.
    • Adds many plugins that developers can use to work with embedded and in-memory databases easily. Spring allows you to easily connect with database and queue services like Oracle, PostgreSQL, MySQL, MongoDB, Redis, Solr, ElasticSearch, Rabbit MQ, and others.

    Dependency List

    1. SpringBoot Starter Parent – 3.1.5
    2. Serenity –  4.0.18
    3. Serenity Cucumber – 4.0.18
    4. Serenity Rest Assured – 4.0.18
    5. Cucumber – 7.14.0
    6. Java 17
    7. JUnit Platform – 1.10.0
    8. Maven – 3.8.6

    Project Directory Structure

    Relationship between SpringBoot, Serenity BDD, Cucumber, and JUnit5

    What is RestController?

    HTTP requests are handled by a controller in Spring’s approach to building RESTful web services. The @RestController annotation identifies these components, and the GreetingController shown below (from src/main/java/com/example/springboot_demo/HelloController.java) handles GET requests for / and /qaautomation by returning a new instance of the Greeting class. Spring RestController takes care of mapping request data to the request-defined handles method.

    import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;
  
@RestController
public class HelloController {
      
    @GetMapping(path="/")
    String hello() {
        return "Hello World, Spring Boot!";
    }
      
      
    @GetMapping(path="/qaautomation")
    String qaautomation() {
        return "Hello QA Automation!";
    }
  
}

    Implementation Steps

    Step 1 – Create a source folder – src/test/resources 

    Create a source folder – src/test/resources to create test scenarios in the Feature file.

    Right-click on the test directory select New->Directory and select resources (Maven Source Directories).

    Step 2 – Add SpringBoot, Serenity, Cucumber, and JUnit5 dependencies to the project

    We have added SpringBootTest, Serenity, Cucumber, JUnit5, Cucumber Junit Platform Engine, and many more.

    <?xml version="1.0" encoding="UTF-8"?>
<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 https://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>

	<parent>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-parent</artifactId>
		<version>3.1.5</version>
		<relativePath/> <!-- lookup parent from repository -->
	</parent>

	<groupId>com.example</groupId>
	<artifactId>SpringBoot3_Serenity_Cucumber_JUnit5_Demo</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>demo</name>
	<description>Demo project for Spring Boot</description>

	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
		<serenity.version>4.0.18</serenity.version>
		<serenity.cucumber.version>4.0.18</serenity.cucumber.version>
		<junit.platform.version>1.10.0</junit.platform.version>
		<cucumber.version>7.14.0</cucumber.version>
		<maven.surefire.plugin.version>3.2.1</maven.surefire.plugin.version>
		<maven.failsafe.plugin.version>3.2.1</maven.failsafe.plugin.version>
		<parallel.tests></parallel.tests>
		<maven.compiler.plugin>3.11.0</maven.compiler.plugin>
		<maven.compiler.source.version>17</maven.compiler.source.version>
		<maven.compiler.target.version>17</maven.compiler.target.version>
		<encoding>UTF-8</encoding>
		<tags></tags>
	</properties>
	
	<dependencies>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter</artifactId>
		</dependency>

		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-test</artifactId>
			<scope>test</scope>
		</dependency>

		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-web</artifactId>
		</dependency>

		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-tomcat</artifactId>
			<scope>provided</scope>
		</dependency>

		<dependency>
			<groupId>org.springframework</groupId>
			<artifactId>spring-web</artifactId>
		</dependency>

		<!-- Serenity Core -->
		<dependency>
			<groupId>net.serenity-bdd</groupId>
			<artifactId>serenity-core</artifactId>
			<version>${serenity.version}</version>
			<scope>test</scope>
		</dependency>

		<!-- Serenity With Cucumber -->
		<dependency>
			<groupId>net.serenity-bdd</groupId>
			<artifactId>serenity-cucumber</artifactId>
			<version>${serenity.version}</version>
			<scope>test</scope>
		</dependency>

		<dependency>
			<groupId>net.serenity-bdd</groupId>
			<artifactId>serenity-screenplay</artifactId>
			<version>${serenity.version}</version>
			<scope>test</scope>
		</dependency>

		<dependency>
			<groupId>net.serenity-bdd</groupId>
			<artifactId>serenity-screenplay-webdriver</artifactId>
			<version>${serenity.version}</version>
			<scope>test</scope>
		</dependency>

		<dependency>
			<groupId>net.serenity-bdd</groupId>
			<artifactId>serenity-ensure</artifactId>
			<version>${serenity.version}</version>
			<scope>test</scope>
		</dependency>

		<!-- Serenity With Rest Assured -->
		<dependency>
			<groupId>net.serenity-bdd</groupId>
			<artifactId>serenity-rest-assured</artifactId>
			<version>${serenity.version}</version>
			<scope>test</scope>
		</dependency>

		<!-- Serenity With Spring -->
		<dependency>
			<groupId>net.serenity-bdd</groupId>
			<artifactId>serenity-spring</artifactId>
			<version>${serenity.version}</version>
			<scope>test</scope>
		</dependency>

		<dependency>
			<groupId>io.cucumber</groupId>
			<artifactId>cucumber-junit-platform-engine</artifactId>
			<version>${cucumber.version}</version>
			<scope>test</scope>
		</dependency>

		<dependency>
			<groupId>org.junit.platform</groupId>
			<artifactId>junit-platform-suite</artifactId>
			<version>${junit.platform.version}</version>
			<scope>test</scope>
		</dependency>

	</dependencies>

	<build>
		<plugins>
			<plugin>
				<groupId>org.springframework.boot</groupId>
				<artifactId>spring-boot-maven-plugin</artifactId>
			</plugin>

				<plugin>
					<groupId>org.apache.maven.plugins</groupId>
					<artifactId>maven-surefire-plugin</artifactId>
					<version>${maven.surefire.plugin.version}</version>
					<configuration>
						<skip>true</skip>
					</configuration>
				</plugin>
				<plugin>
					<artifactId>maven-failsafe-plugin</artifactId>
					<version>${maven.failsafe.plugin.version}</version>
					<configuration>
						<includes>
							<include>**/*Test.java</include>
							<include>**/SpringRunnerTests.java</include>
							<include>**/*TestSuite.java</include>
							<include>**/When*.java</include>
						</includes>
						<parallel>classes</parallel>
						<parallel>methods</parallel>
						<useUnlimitedThreads>true</useUnlimitedThreads>
					</configuration>
					<executions>
						<execution>
							<goals>
								<goal>integration-test</goal>
								<goal>verify</goal>
							</goals>
						</execution>
					</executions>
				</plugin>
				<plugin>
					<groupId>org.apache.maven.plugins</groupId>
					<artifactId>maven-compiler-plugin</artifactId>
					<version>${maven.compiler.plugin}</version>
					<configuration>
						<source>${maven.compiler.source.version}</source>
						<target>${maven.compiler.target.version}</target>
					</configuration>
				</plugin>
				<plugin>
					<groupId>net.serenity-bdd.maven.plugins</groupId>
					<artifactId>serenity-maven-plugin</artifactId>
					<version>${serenity.version}</version>
					<configuration>
						<tags>${tags}</tags>
					</configuration>
					<executions>
						<execution>
							<id>serenity-reports</id>
							<phase>post-integration-test</phase>
							<goals>
								<goal>aggregate</goal>
							</goals>
						</execution>
					</executions>
				</plugin>
			</plugins>
	</build>
	<repositories>
		<repository>
			<id>spring-milestones</id>
			<name>Spring Milestones</name>
			<url>https://repo.spring.io/milestone</url>
			<snapshots>
				<enabled>false</enabled>
			</snapshots>
		</repository>
		<repository>
			<id>spring-snapshots</id>
			<name>Spring Snapshots</name>
			<url>https://repo.spring.io/snapshot</url>
			<releases>
				<enabled>false</enabled>
			</releases>
		</repository>
	</repositories>
	<pluginRepositories>
		<pluginRepository>
			<id>spring-milestones</id>
			<name>Spring Milestones</name>
			<url>https://repo.spring.io/milestone</url>
			<snapshots>
				<enabled>false</enabled>
			</snapshots>
		</pluginRepository>
		<pluginRepository>
			<id>spring-snapshots</id>
			<name>Spring Snapshots</name>
			<url>https://repo.spring.io/snapshot</url>
			<releases>
				<enabled>false</enabled>
			</releases>
		</pluginRepository>
	</pluginRepositories>

</project>

    Step 3 – Create a feature file under src/test/resources

    Below is an example of a feature file that shows a sample test scenario.

    Feature: SpringBoot Request
   
@ReceiveCorrectResponse

   Scenario Outline: Send a valid Request to get correct response
    Given I send a request to the URL "<url>"
    Then the response will return "<response>"

   Examples:
   | url                       | response                             |
   | /                          | Hello World, Spring Boot!  |
   | /qaautomation   | Hello QA Automation!        |

    The test class mentioned below (AbstractRestAssuredHelper) contains integration tests for the spring boot rest controller mentioned. This test class:

    • uses @SpringBootTest annotation which loads the actual application context.
    • uses WebEnvironment.RANDOM_PORT to create and run the application at some random server port.
    • @LocalServerPort gets the reference of the port where the server has started. It helps in building the actual request URIs to mimic real client interactions.

    Step 4 – Create the StepDefinition and Helper classes

    Below is the code of the StepDefinition and Helper class. These classes are created in the src/test/java directory.

    AbstractRestAssuredHelper

    import io.restassured.RestAssured;
import io.restassured.specification.RequestSpecification;
import net.serenitybdd.rest.SerenityRest;

import org.springframework.beans.factory.annotation.Value;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.boot.test.context.SpringBootTest.WebEnvironment;
import org.springframework.boot.test.web.server.LocalServerPort;


@SpringBootTest(webEnvironment = WebEnvironment.RANDOM_PORT)
public abstract class AbstractRestAssuredHelper {
     private final static String BASE_URI = "http://localhost";
 
     @LocalServerPort
     private int port;

     @Value("${server.servlet.context-path}")
     private String basePath;
 
     protected void configureRestAssured() {
           RestAssured.baseURI = BASE_URI;
           RestAssured.port = port;
           RestAssured.basePath = basePath;
           
 
     }

     protected RequestSpecification getAnonymousRequest() {
           configureRestAssured();
           return SerenityRest.given();
     }
}

    This class sends the request and receives a response after performing the GET operation. Here, the validation of the response also takes place by asserting the expected and actual response

    To use Rest-assured, Serenity provides the class SerenityRest

    import io.cucumber.java.en.Given;
import io.cucumber.java.en.Then;
import io.restassured.response.Response;
import net.serenitybdd.rest.SerenityRest;
import net.thucydides.core.annotations.Steps;
import org.junit.jupiter.api.Assertions;

public class SpringBootDemoDefinitions {

	@Steps
    AbstractRestAssuredHelper helper;
    private Response response;

    @Given("I send a request to the URL {string}")
    public void iSendARequest(String endpoint) throws Exception  {
         response = helper.getAnonymousRequest().contentType("application/json")
                    .header("Content-Type", "application/json").when().get(endpoint);
    }

    @Then("the response will return {string}")
    public void extractResponse(String Expected ) {
          SerenityRest.restAssuredThat(response -> response.statusCode(200));
          String Actual = response.asString();    
          System.out.println("Result :"+Actual);
          Assertions.assertEquals(Expected, Actual);
    }
}

    Step 5 – Create a Serenity Runner class in the src/test/java directory

    We cannot run a Feature file on its own in a cucumber-based framework. We need to create a Java class that will run the Feature File. It is the starting point for JUnit to start executing the tests. TestRunner class is created under src/ test/java. 

    import org.junit.platform.suite.api.ConfigurationParameter;
import org.junit.platform.suite.api.IncludeEngines;
import org.junit.platform.suite.api.SelectClasspathResource;
import org.junit.platform.suite.api.Suite;
import static io.cucumber.junit.platform.engine.Constants.GLUE_PROPERTY_NAME;
import static io.cucumber.junit.platform.engine.Constants.PLUGIN_PROPERTY_NAME;

@Suite
@IncludeEngines("cucumber")
@SelectClasspathResource("com.example")
@SelectClasspathResource("/features")
@ConfigurationParameter(key = GLUE_PROPERTY_NAME, value = "com.example.definitions")
@ConfigurationParameter(key = PLUGIN_PROPERTY_NAME, value = "io.cucumber.core.plugin.SerenityReporterParallel,pretty,timeline:build/test-results/timeline")
public class SpringRunnerTests {
}

    @Suite – annotation from JUnit 5 to make this class a run configuration for the test suite.
    @IncludeEngines(“cucumber”) – tells JUnit 5 to use the Cucumber test engine to run features.
    @SelectClasspathResource(“/features”) – to change the location of your feature files (if you do not add this annotation classpath of the current class will be used).
    @ConfigurationParameter(key = GLUE_PROPERTY_NAME, value = “com.example.SpringBoot_Demo.definitions”) – this annotation specifies the path to steps definitions (java classes).

    Step 6 – Run the tests from JUnit5

    You can run the tests from SpringRunnerTests class. Right-click on the class and select Run ‘SpringRunnerTests’.

    The output of the above program is

    Step 7 – Run the tests from the Command Line

    Run the tests from the command line by using the below command

    mvn clean verify

    The output of the above program is

    The test execution status is shown below:

    Step 8 – Serenity Report Generation

    By default, the test report generated by Serenity is placed under target/site/serenity/index.html. Below is the sample Serenity Report.

    Go to the Test Results tab and we can see all the test scenarios.

    Step 9 – Cucumber Report Generation

    Cucumber Report can be generated by adding publish=true in SpringRunnerTests as shown in the above example. Click on the link provided in the execution status.

    Cucumber Report

    The next tutorial explains the Testing of SpringBoot REST Application using Serenity BDD and Rest Assured for GET Method.

    The complete code can be found on GitHub.

    vibssingh

    Robot Framework Features – Settings, Libraries, Variables, Keywords, Resources, Reports, Logs

    HOME

    The previous tutorial has explained What is Robot Framework and its advantages. This tutorial will explain the various features available in this framework.

    1. Settings

    The Setting section is used to import libraries, resource files, and variable files and to define metadata for test suites and test cases. It can be included in test case files and resources.

    The most commonly used are:

    NameDescription
    LibraryUsed for importing libraries.
    ResourceUsed for taking resource files into use.
    DocumentationUsed for specifying a test suite or resource file documentation.
    VariablesUsed for taking variable files into use.
    MetadataUsed for setting free test suite metadata.
    Test SetupUsed for specifying a default test setup.
    Test TeardownUsed for specifying a default test teardown.
    Test TemplateUsed for specifying a default template keyword for test cases.

    Example of Setting:

    *** Settings ***
Documentation    To validate the Login Form
Library     SeleniumLibrary
Test Teardown    Close Browser

    2. Test Cases

    The settings in the Test Case section are always specific to the test case for which they are defined. Some of these settings override the default values defined in the Settings section.

    Example of Test Case:

    *** Test Cases ***
Validate Unsuccessful Login
    Open the Browser with URL
    Fill the login form
    Verify error message is correct

    3. Keywords

    The Keyword section settings are unique to the user keyword for which they are defined. The robot architecture includes built-in keywords as well as keywords from libraries such as the Selenium Library. (open browser, close browser, maximize browser, etc.). We can also make user-defined keywords out of other user-defined keywords or built-in or library keywords. We can also give arguments to those keywords, which turns them into functions that can be reused.

    Example of Keywords:

    *** Keywords ***
Open the Browser with URL
    Create Webdriver    Chrome  executable_path=/Vibha_Personal/RobotFramework/drivers/chromedriver_linux64
    Go To    https://opensource-demo.orangehrmlive.com/web/index.php/auth/login
    Maximize Browser Window
    Set Selenium Implicit Wait    5

    4. Libraries

    Many external libraries, such as SeleniumLibrary, Database Library, FTP Library, and HTTP Library, are supported by the Robot architecture. SeleniumLibrary is mostly used to communicate with browsers and aid in web application and UI testing. Robot framework also includes its own libraries for strings, dates, integers, and so on.

    Normally, test libraries are imported by selecting the Library option in the Setting section and entering the library name in the following column. The collection name, unlike most other data, is case and space sensitive. If a library is part of a package, use the complete name, including the package name.

    Example of Libraries:

    Library     SeleniumLibrary
Library     String

    5. Variables

    Variables which are defined in the *** Variables *** section are available in all test cases and keywords in the same file.
    Variables defined in the *** Variables *** section are suite variables.
    If a .resource or a .robot file with a *** Variables *** section is imported into a test suite, and the variables there also become suite variables.

    Example of Variables:

     ${result}=  Get Text    CSS:.oxd-alert-content-text

    6. Resources

    Resource files are imported using the Resource setting in the Settings section so that the path to the resource file is given as an argument to the setting.  The robot framework also allows the import of robot files with keywords externally to be used with test cases. Resources are very easy to use and are of great help when we need to use some keywords already written for other test projects.

    Example of Resource File:

    *** Settings ***
Documentation
Library     SeleniumLibrary

*** Variables ***
${valid_username}     Admin
${valid_password}       admin123
${invalid_username}     1234
${invalid_password}     45678
${url}      https://opensource-demo.orangehrmlive.com/web/index.php/auth/login

*** Keywords ***

Open the Browser with URL
    Create Webdriver    Chrome  executable_path=/Vibha_Personal/RobotFramework/drivers/chromedriver_linux64
    Go To       ${url}
    Maximize Browser Window
    Set Selenium Implicit Wait    5

Close Browser Session
    Close Browser

    7. Reports and Logs

    The robot framework provides all test suite and test case execution details in the shape of reports and logs. The log file contains all the test case’s execution information. Details such as whether the test case failed or passed, the time required for execution, and the steps needed to run the test case are provided.

    Report

    Log

    That’s it! Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!!

    vibssingh

    Robot Framework – Working With Browsers Using Selenium Library

    HOME

    In this tutorial, we will create a project in PyCharms and create a test case in Robot Framework using Selenium WebDriver.

    Prerequisite:

    1. Install Python
    2. Install PIP
    3. Install Robot Framework
    4. Install Robot framework Selenium Library
    5. Install PyCharm IDE

    Please refer to this tutorial to install Robot Framework – How to install and setup Robot Framework for Python.

    Implementation Steps:

    Step 1 – Open PyCharm and create a new project. Go to File and select “New Project” from the main menu.

    Step 2 – Choose the project location. Click the “Browse” button next to the Location field and specify the directory for your project.

    Deselect the Create a main.py welcome script checkbox because you will create a new Python file for this tutorial.

    Python best practice is to create a virtualenv for each project. In most cases, PyCharm creates a new virtual environment automatically, and you don’t need to configure anything. But, in this case, we need to create a Base Interpreter that has the robot framework already installed. This is explained in this tutorial – How to install and setup Robot Framework for Python. To preview and modify the venv options. Expand the Python Interpreter: New Virtualenv Environment node and select a tool used to create a new virtual environment. Let’s choose Virtualenv tool, and specify the location of the environment and the base Python interpreter used for the new virtual environment.

    Click on the “Create” Button.

    Step 3 – A new dialog will appear asking to Open the project using any one of the given options. I have selected New Window as I like to have separate windows for each project.

    Below is the image of the new project created in PyCharms.

    How to create a Selenium test in Robot Framework?

    Step 1 – Create a new directory in the new project

    Right-Click on the project, select New->Directory and provide name as Tests

    Below is the image of the new directory.

    Right-click on the new directory and select New File and provide the name as Test_Demo.robot as shown below:

    Step 2 – Download ChromeBinaries from the below location

    The tests are going to use the Chrome browser, so we need to download the ChromeBinaries to open a blank browser in Chrome.

    https://chromedriver.chromium.org/

    Step 3 – Create a simple Selenium Test

    *** Settings ***
Documentation    To validate the Login Form
Library     SeleniumLibrary

*** Test Cases ***
Validate Unsuccessful Login
    Open the Browser with URL
    Fill the login form
    Verify error message is correct


*** Keywords ***
Open the Browser with URL
    Create Webdriver    Chrome  executable_path=/Vibha_Personal/RobotFramework_Demo/drivers/chromedriver_linux64
    Go To    https://opensource-demo.orangehrmlive.com/web/index.php/auth/login
    Maximize Browser Window
    Set Selenium Implicit Wait    5

Fill the login form
   Input Text    css:input[name=username]   Admin
   Input Password    css:input[name=password]   Admin
   Click Button    css:.orangehrm-login-button


Verify error message is correct
    ${result}=  Get Text    CSS:.oxd-alert-content-text
    Should Be Equal As Strings   ${result}  Invalid credentials

    The chromedriver is placed in a folder name drivers in RobotFramework_Demo project.

    I will explain the terms Settings, Test Cases, Keywords in the next tutorial.

    To run this script, go to the command line and go to directory tests.

    We need the below command to run the Robot Framework script.

    robot Test_Demo.robot

    The output of the above program is

    We have the test case passed. The Robot Framework generates log.html, output.xml, and report.html by default.

    Let us now see the report and log details.

    Report

    Right-click on report.html. Select Open In->Browser->Chrome(any browser of your wish).

    The Report generated by the framework is shown below:

    Log

    Robot Framework has multiple log levels that control what is shown in the automatically generated log file. The default Robot Framework log level is INFO.

    Right-click on log.html. Select Open In->Browser->Chrome(any browser of your wish).

    That’s it! Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!!