This project is a QA automation framework built using Cucumber BDD (Behavior-Driven Development) framework with Selenium. It provides a structured approach for automating browser tests, ensuring efficient test case management and easier collaboration between QA engineers and stakeholders. Maven as the build automation tool for managing dependencies and executing tests. JUnit for assertion and validation of test results. There is two main step for this framework

1.add below property section

<properties>
    <maven.compiler.source>11</maven.compiler.source>
    <maven.compiler.target>11</maven.compiler.target>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>

2.Add dependencies

<dependencies>

     <dependency>
          <groupId>org.seleniumhq.selenium</groupId>
          <artifactId>selenium-java</artifactId>
          <version>3.141.59</version>
     </dependency>

     <!-- https://mvnrepository.com/artifact/io.github.bonigarcia/webdrivermanager -->
     <dependency>
          <groupId>io.github.bonigarcia</groupId>
          <artifactId>webdrivermanager</artifactId>
          <version>5.3.1</version>
     </dependency>
     
     <!-- https://mvnrepository.com/artifact/io.cucumber/cucumber-java -->
     <dependency>
          <groupId>io.cucumber</groupId>
          <artifactId>cucumber-java</artifactId>
          <version>7.2.3</version>
     </dependency>

     <!-- https://mvnrepository.com/artifact/io.cucumber/cucumber-junit -->
     <dependency>
          <groupId>io.cucumber</groupId>
          <artifactId>cucumber-junit</artifactId>
          <version>7.2.3</version>
          <scope>test</scope>
     </dependency>

     <dependency>
          <groupId>me.jvt.cucumber</groupId>
          <artifactId>reporting-plugin</artifactId>
          <version>7.2.0</version>
     </dependency>

     <!-- https://mvnrepository.com/artifact/com.github.javafaker/javafaker -->
     <dependency>
          <groupId>com.github.javafaker</groupId>
          <artifactId>javafaker</artifactId>
          <version>1.0.2</version>
     </dependency>

     <!--If you want to get rid of SLF4J Failed to load message from the console -->
     <dependency>
          <groupId>org.slf4j</groupId>
          <artifactId>slf4j-simple</artifactId>
          <version>1.7.32</version>
     </dependency>

     <dependency>
          <groupId>org.junit.jupiter</groupId>
          <artifactId>junit-jupiter</artifactId>
          <version>5.7.2</version>
     </dependency>

     <dependency>
          <groupId>io.rest-assured</groupId>
          <artifactId>rest-assured</artifactId>
          <version>4.4.0</version>
     </dependency>

     <!-- https://mvnrepository.com/artifact/com.fasterxml.jackson.core/jackson-databind -->
     <dependency>
          <groupId>com.fasterxml.jackson.core</groupId>
          <artifactId>jackson-databind</artifactId>
          <version>2.14.2</version>
     </dependency>


     <dependency>
          <groupId>org.projectlombok</groupId>
          <artifactId>lombok</artifactId>
          <version>1.18.26</version>
     </dependency>
     
</dependencies>

3.Add Build Plugins

<build>

     <plugins>
          <plugin>
               <groupId>org.apache.maven.plugins</groupId>
               <artifactId>maven-surefire-plugin</artifactId>
               <version>3.0.0-M5</version>
               <configuration>
                    <parallel>methods</parallel>
                    <!--<useUnlimitedThreads>true</useUnlimitedThreads>-->
                    <threadCount>4</threadCount>
                    <testFailureIgnore>true</testFailureIgnore>
                    <includes>
                         <include>**/CukesRunner*.java</include>
                    </includes>
               </configuration>
          </plugin>
     </plugins>
</build>

1. under com.demoQAUI, create pages, runners, srep_definitions and utilities packages

2. Add a configuration.properties file to store project information in order to avoid hard coding. add following information:

browser=chrome
username=johnWick
password=Pass471!
url=https://demoqa.com/

1. Create a file with .feature extension to define scenarios and steps. This just a regular file.

2. In feature file follow cucumber BDD (Gherkin) approach

if you are using command line: mvn clean verify cmd+enter or ctrl+enter. if you dont have maven installed locally and if you are using IntelliJ buttons; first click on clean then click on verify. Your report will be generated under target as HTML Report

1. Create Hooks java class to use cucumber @Before and @After annotations

1. Add below information above CukesRunner class name

@RunWith(Cucumber.class)
@CucumberOptions(
        plugin = {
                //"pretty",
                "html:target/cucumber-report.html",
                "rerun:target/rerun.txt",
                "me.jvt.cucumber.report.PrettyReports:target/cucumber",
                "json:target/cucumber.json"
        },

        features = "src/test/resources/features",
        glue = "com/demoQAUI/step_definitions",
        dryRun =,
        tags = ""
)

2. Add below information above FailedTestRunner class name

@RunWith(Cucumber.class)
@CucumberOptions(
        glue = "com/demoQAUI/step_definitions",
        features = "@target/rerun.txt"
)

1. Create BasePage java class and add base page class constructor with following

 public BasePage() {
        PageFactory.initElements(Driver.getDriver(),this);
    }

1. Create pojo package to store POJO classes which is implementing deserialization for each JSON file
2. Improving code quality and productivity in testing by reducing repetitive tasks and enhancing the readability of test cases and test data by using Lombok library

@Getter
@Setter
@ToString

3. Create a test package in order to write actual code fragments

Normally I have a framework for API testing. It is Serenity BDD framework. I could not implement it in this project. Because there is frontend part as well. I am using Cucumber BDD framework with Selenium for that. So I have chose Cucumber.

1. I have serenity.conf file and serenity.properties file where I store my base url, Database connection string and one valid user credentials for each type of user.
2. serenity.conf file allows me to switch between environment easily.I have same key name with different environments so that when I want to switch I use mvn clean verify -dEnvironment=...(qa2) and it runs my test cases against to env I used. If I dont specify it will use default environment that I set in serenity.conf file
3. I label my classes with @SerenityTest and I set my report and root name in serenity.properties file. So that tests are recognized by report.

1. I have BaseTest for my project where I use @BeforeAll and @AfterAll methods to set my base_url, db connection, and close connections and reset.
2. I have used regular @Tests and @ParametrizedTests from Junit5. @ParameterizedTests allow me to run same testcase with different sets of data which is DDT(Data Driven Testing).
3. I use @MethodSource and @CsvFileSource mostly, but I know there are like ValueSource and CsvSource also.

1. I use Serenity version of RestAssured library where I have same methods in gherkin format.Gherkin allow me type readable test cases for non-technical people.If the person knows API they can easily understand my test cases.
2. Serenity way is allowing me to get request and response in the report.I also use Ensure.that() type of verification to log each assertion that I make, to see in the report.
3. I use Hamcrest matchers inside the my assertion,I use pojo classes and java maps mostly to store and send request and json body.

This is a small task. So I did not create any utility classes for API part. I implemented DDT by using Csv source with ParameterizedTest annotations. Also I have an experience by using Method source and Csv file source annotations.