A showcase of my QA abilities by creating an automation framework using Java, Selenium, TestNG. In short: this framework will be a BDD-POM hybrid framework with support for API and database testing.
Important note: in the process of building up the framework from scratch, it's unavoidable that there will be files leftover to represent what the framework looked like at an earlier point. Additionally, I have decided to keep multiple versions of the POM implementation within the framework. It is up to the automation framework architect to decide which version to implement based on the needs of the company they work for.
This framework will include the following:
Click me to display this section
- POM (Page Object Model) - To separate function driven methods into several classes as well as using PageFactory to find elements.
- Object Repository - To store WebElement locators in properties files.
- BDD/BDT (Behavior Driven Development/Testing) - To abstract away the difficulty of creating test scripts by using Gherkin.
- Rest API Testing - To test REST API using Rest Assured.
- Database Testing - To test a mysql database using JDBC.
- Cross-browser Testing - To run tests on multiple browsers at the same time.
- Jenkins (CI/CD) - To run tests based on certain criteria (new code has been pushed, it is after work hours, etc)
- Selenium GRID/Browser Stack (parallel distributed testing) - To run tests on a distributed environment either locally (GRID) or on a service (Browser Stack).
This framework will be missing the following (for now):
Click me to display this section
-
Note that while I provide only these options, there may be many more. There is no right or wrong way of implementing these types of frameworks, it all just depends on your situation (the website being tested, your script creators, complexity of the test cases, etc)
-
Mobile Testing - If you wanted to implement this yourself, you have these option(s):
- You can use Appium (which has similar syntax as Selenium) in order to do mobile testing.
-
KDD/KDT (Keyword Driven Development/Testing) - If you wanted to implement this yourself, you have these option(s):
-
Create an Excel spreadsheet with a format that your test team can agree with.
Excel keyword framework data format... click me to display
Step Locator Action Data 1 LINK_TEXT:Login CLICK 2 ID:spree_user_email SEND_KEYS shift@gmail.com 3 ID:spree_user_password SEND_KEYS shiftedtech 4 NAME:commit CLICK 5 CSS:.alert-success VERIFY_TEXT Logged in successfully -
Use Apache POI to read this Excel data.
Reading Excel data code... click me to display
String file = <fileLocation> ExcelReader reader = new ExcelReader(file); String[][] data = reader.getExcelSheetData(0, true); for(int i = 0; i < data.length; i++) { String index = data[i][0]; String locator = data[i][1]; String action = data[i][2]; String testData = data[i][3]; System.out.println(String.format("Index: %s Locator: [%s] Action: %s TestData: %s", index, locator, action, testData)); }
-
-
-
DDD/DDT (Data Driven Development/Testing) - If you wanted to implement this yourself, you have these option(s):
-
Create a method that returns a two dimensional array then mark that method using TestNG's @DataProvider to feed this data into a parameterized test.
-
Use Apache POI to get data from an Excel spreadsheet then use that data in a parameterized test using TestNG's @DataProvider.
-
You can create a test script generator using Java where you feed the generator a bunch of test data. For each "unit" of test data that you input, it will create a test case using a "default" structure. With each different test, it will replace the parameters you want with the test data.
-
Example:
Test script generator... click me to display
// Sample default structure @Test() public void test<id>() { homePage.goToLoginPage(); loginPage().login(<username>, <password>); homePage().verifyLoginSuccess(); } // Test script generator will generate the following: // Auto generated test script @Test() public void test1() { homePage.goToLoginPage(); loginPage().login("shift@gmail.com", "password"); homePage().verifyLoginSuccess(); } // Auto generated test script @Test() public void test2() { homePage.goToLoginPage(); loginPage().login("shiftqa@gmail.com", "password1"); homePage().verifyLoginSuccess(); } . . . // Auto generated test script @Test() public void test999() { homePage.goToLoginPage(); loginPage().login("shiftqa00312@gmail.com", "someR32#ndao@OmPaswowerd"); homePage().verifyLoginSuccess(); }
-
Click me to display this section
- Create a Maven project.
- Create proper project structure.
- Setup local maven repository, proxy, mirrors, and repositories.
- Add required dependencies into pom.xml
- Setup custom test reporting (Extent or Allure reporting or create your own reporting)
- Create a driver factory that supports ThreadLocal so all your tests can be run in parallel.
- The driver factory should make creating and using a WebDriver as simple as possible.
- Allow users to choose which WebDriver to use when creating a driver.
- Allow users to choose between headless or GUI WebDrivers.
- Setup cross browser testing by creating a testng.xml runner that utilizes parameters.
- Implement the POM (Page Object Model) framework.
- Navigation (and other WebElements that remain the same from one page to another should be the base class/super class)
- Each page of the company website should have it's own class and these classes should all extend the navigation page class.
- Implement a function driven framework where each page has several steps of a test wrapped into it's own function.
- For example in the Login page class, create a function that takes in a String username and String password. The username and password fields are cleared of any previous text stored. Next, the function enters those Strings into the username and password field respectively. Finally, the login button is clicked.
- Implement the BDD (Behavior Driven Development/Testing) framework.
- Implement Rest Assured for API testing.
- Implement Karate for BDD style API testing.
- Implement the JDBC (Java Database Connector) for database testing.
- Has an added benefit of being used for Keyword and Data Driven Development/Testing.
- Generate tests using AssertJ, Selenium, and TestNG.
- Setup Selenium Grid and/or Browser Stack based on company's requirements.
- Setup Jenkins or Bamboo as a CI/CD pipeline based on company's requirements.
Click me to display this section
- Using IntelliJ IDEA, click on New > New Project.
- Select Maven > Next.
- Provide a GroupId in reverse order (if your company's url is google.com then you should make the GroupId "com.google")
- Provide an ArtifactId based on the project you are working on then click Next.
- Provide a project name and location then click Finish.
Click me to display this section
-
The testcases package contains random test cases just to make sure that the project works with all the dependencies.
-
The hybridtestcases package is to make sure the framework has been implemented properly.
-
The com.shiftedtech.spree package contains all tests related to the website http://spree.shiftedtech.com
-
The com.shiftedtech.heatclinic package contains all tests related to the website http://heatclinic.shiftedtech.com
-
All test scripts belong in src/test/java
-
All framework scripts belong in src/main/java
Framework layout... click me to display
- pom.xml - src - main - java - com.h1ddengames.framework // All framework files belong here - pages - BasePage - HomePage - LoginPage - All other page object model files belong here - steps - All step definition files belong here - utils - All utility files belong here - resources - All properties files for different environments belong here - Any properties files for custom reporting belong here - test - java - com.h1ddengames - bdd - All bdd runner files go here - resources - log4j.properties - testng-simpletest.xml
Click me to display this section
- Download Maven CLI: https://maven.apache.org/download.cgi
- Create and add a MAVEN_HOME variable then put it in your path.
- Go to MAVEN_HOME/conf and copy the settings.xml file to your user's .m2 folder.
- Change the settings.xml file to suit your company's requirements.
- For example change your localRepository to a path on your computer rather than on the network drive that most companies will use.
- Setup the proxy sever information if your company does not allow you to access the internet directly.
- Use an internal repository if your company has one https://maven.apache.org/guides/introduction/introduction-to-repositories.html
- Setup mirrors if required.
Click me to display this section
-
Go to https://mvnrepository.com and search for the following dependencies or include the dependencies below:
- Selenium
- WebDriverManager
- Rest-Assured
- Mysql JDBC
- TestNG
- Hamcrest
- Assertj
- Cucumber Java
- Cucumber TestNG
- Cucumber Reporting
- slf4j-api
- slf4j-log4j12
- Maven Surefire Plugin
- Maven Compiler Plugin
-
In the properties tag, create a property for all the dependencies with the current version number within the property tag.
-
For example:
<properties> <java.version>11</java.version> <selenium-java.version>3.141.59</selenium-java.version> ... All the rest from step 1. ... <maven-compiler.version>3.8.1</maven-compiler.version> </properties>
-
-
Update all the dependencies versions using the property variables created above:
<dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium-java</artifactId> <version>3.141.159</version> </dependency> becomes: <dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium-java</artifactId> <version>${selenium-java.version}</version> </dependency> -
Create a file in src/test/resources and name it log4j.properties. Then put the following lines in the file:
# Set root logger level to DEBUG and its only appender to A1. log4j.rootLogger=INFO, A1 # A1 is set to be a ConsoleAppender. log4j.appender.A1=org.apache.log4j.ConsoleAppender # A1 uses PatternLayout. log4j.appender.A1.layout=org.apache.log4j.PatternLayout log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n -
The final pom.xml should look something like this:
Final pom.xml... click me to display
<properties> <!-- Keep all the version numbers at the top to make it easier to upgrade --> <java.version>11</java.version> <selenium-java.version>3.141.59</selenium-java.version> <webdrivermanager.version>3.6.2</webdrivermanager.version> <rest-assured.version>4.0.0</rest-assured.version> <mysql-jdbc.version>8.0.17</mysql-jdbc.version> <testng.version>7.0.0</testng.version> <hamcrest.version>1.3</hamcrest.version> <assertj.version>3.13.2</assertj.version> <cucumber-java.version>4.7.1</cucumber-java.version> <cucumber-testng.version>4.7.1</cucumber-testng.version> <cucumber-reporting.version>4.9.0</cucumber-reporting.version> <slf4j-api.version>1.7.28</slf4j-api.version> <slf4j-log4j12.version>1.7.28</slf4j-log4j12.version> <maven-surefire.version>3.0.0-M3</maven-surefire.version> <maven-compiler.version>3.8.1</maven-compiler.version> </properties> <dependencies> <!-- https://mvnrepository.com/artifact/org.seleniumhq.selenium/selenium-java This dependency is for browser automation --> <dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium-java</artifactId> <version>${selenium-java.version}</version> </dependency> ... Include all the other dependencies in the above format ... <!-- https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-compiler-plugin --> <dependency> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>${maven-compiler.version}</version> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.8.0</version> <configuration> <release>${java.version}</release> <encoding>UTF-8</encoding> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>3.0.0-M3</version> <configuration> <suiteXmlFiles> <suiteXmlFile>testng-simpletest.xml</suiteXmlFile> </suiteXmlFiles> <argLine> --illegal-access=permit </argLine> </configuration> </plugin> </plugins> </build>
Click me to display this section
Click me to display this section
Click me to display this section
-
Create an xml file called simple-tests.xml with the following code:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd"> <suite name="Simple Test Suite" verbose="1"> <test name="Chrome Test" > <parameter name="browser" value="CH"/> <classes> <class name="com.h1ddengames.testcases.TestCase1"/> </classes> </test> <test name="Firefox Test" > <parameter name="browser" value="FF"/> <classes> <class name="com.h1ddengames.testcases.TestCase1"/> </classes> </test> </suite> -
Update the setup method (@BeforeClass marked method) to look like this:
@Parameters({ "browser" }) @BeforeClass public void setup(String browser) { // Downloading directly over the network is forbidden so you might // not be able to use WebDriverManager. WebDriverManager.chromedriver().version("76.0.3809.68").setup(); WebDriverManager.firefoxdriver().version("0.24.0").setup(); if(browser.toUpperCase().contentEquals("CH")) { driver = new ChromeDriver(); } else if(browser.toUpperCase().contentEquals("FF")) { driver = new FirefoxDriver(); } else { driver = new ChromeDriver(); } }
-
The simple-tests.xml will run all the tests found in TestCase1 script file with Chrome first then rerun all the tests with Firefox.
-
The simple-tests.xml can be updated to only run certain groups of tests (function, regression, etc) for each of the browsers:
testng.xml... click me to display
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd"> <suite name="Simple Test Suite" parallel="tests" thread-count="5" verbose="1"> <test name="Chrome Test"> <!--parallel="methods" thread-count="3"--> <parameter name="browser" value="CH"/> <groups> <run> <exclude name="broken"/> <exclude name="unimplemented"/> </run> </groups> <classes> <class name="com.h1ddengames.testcases.TestCase1"/> <class name="com.h1ddengames.testcases.TestCase2"/> <class name="com.h1ddengames.testcases.POMTestCase"/> <class name="com.h1ddengames.testcases.POMWithObjectRepositoryTestCase"/> <class name="com.h1ddengames.testcases.POMWithPageFactoryTestCase"/> </classes> </test> <test name="Firefox Test" > <parameter name="browser" value="FF"/> <groups> <run> <exclude name="broken"/> <exclude name="unimplemented"/> </run> </groups> <classes> <class name="com.h1ddengames.testcases.TestCase1"/> <class name="com.h1ddengames.testcases.TestCase2"/> <class name="com.h1ddengames.testcases.POMTestCase"/> <class name="com.h1ddengames.testcases.POMWithObjectRepositoryTestCase"/> <class name="com.h1ddengames.testcases.POMWithPageFactoryTestCase"/> </classes> </test> </suite>-
If you are specifying the type of test to be run, you have to mark your test methods like so:
@Test(groups = { "functional" }) public void positiveLoginCase() { // code here } @Test(groups = { "broken" }) { // some broken test that will get ignored here. } @Test(groups = { "unimplemented" }) { // some test that needs to be implemented here. }
-
-
-
Once a DriverFactory that supports ThreadLocal creation of WebDrivers has been implemented you can run both browsers in parallel (both browsers will open at the same time and all the tests will run on both browsers thus speeding up testing) with the following:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd"> <suite name="Simple Test Suite" parallel="tests" verbose="1"> <test name="Chrome Test" > <parameter name="browser" value="CH"/> <classes> <class name="com.h1ddengames.testcases.TestCase1"/> </classes> </test> <test name="Firefox Test" > <parameter name="browser" value="FF"/> <classes> <class name="com.h1ddengames.testcases.TestCase1"/> </classes> </test> </suite>
Click me to display this section
Important note: there are several ways to implement POM into a framework.
Here are a couple examples:
- Basic POM - You create Java files based on the names of the pages you are testing and each of these files contain function driven methods such as logging in or moving to another page. In a pure POM framework, test script creators use only the functions provided to them. Since the function implementation is done by the framework architect, the script creators do not need to worry or know about knowing Selenium locators.
- BasePage - Contains all navigation functions (methods)
- HomePage - Contains all the functions related to tasks on the home page.
- LoginPage - Same as above except for the login page.
- etc. - The amount of pages depends on the website being tested and the scope of your automation tests.
- POM with Object Repository - The Java files are created just like with basic POM but instead of having Selenium locators all across your page functions, you use property files located within the src/main/resources folder to contain them. The benefit of doing it this way over basic POM is that you get to keep all the locators in one place so if your application changes locators a lot from version to version, you can just update the locators in one place rather than search every file for them.
- POM with Excel Spreadsheet - The idea is the same as POM with Object Repository but instead of using properties file(s), you instead use an Excel spreadsheet to contain all the Selenium locators. Please note that there is no "correct" way of implementing POM. You just have to decide which version is the best for the company/website.
- POM with PageFactory - Now instead of having locators in a different location, you specify WebElements with locators at the top of each page file with the @FindBy annotation. Update the constructor of each page to use PageFactory to find each element through the @FindBy annotation.
If you want examples of all four types of POM then you'll need to view the project in an IDE.
Here is an example of implementing the basic POM:
-
Create a package in /src/main/java based on the project.
- For example: spree.pages (${website}.pages)
-
Create as many java files as there are pages to be tested.
- BasePage
- HomePage
- LoginPage
- CartPage
- etc.
-
Create a java file that will act as the composition class (holds all other page classes within it)
- Name it whatever you want (SpreeScriptBase or PageComposition)
- For this example, we'll use PageComposition
-
Put the following code into the PageComposition class:
Page composition class... click me to display
private HomePage homePage; private LoginPage loginPage; private CartPage cartPage; // any other pages go here following the above structure. // HomePage is different because if it's the first time creating a HomePage object then you need to use driver.navigate to go to the website. // For all other times that you ask for the homePage, you get whatever is already in memory. public HomePage homePage() { if(homePage == null) { homePage = new HomePage(driver); // When homePage is null, that means the script has not used driver.navigate() to get // to the homePage's baseURL. Calling any other method than navigate... will cause // WebElements to not be found. driver.navigate().to(homePage.baseURL); } return homePage; } public LoginPage loginPage() { if(loginPage == null) { loginPage = new LoginPage(driver); } return loginPage; } // ... all other pages follow the same structure as loginPage
-
For each of your pages you'll need to create a constructor with WebDriver as a parameter:
// The constructor should be the class name (WebDriver driver) with everything else the same. public HomePage(WebDriver driver) { // This line might be the only line required for you. this.driver = driver; // I include WebDriverWait because the framework that I'm choosing to make here uses WebDriverWait to find and use WebElements. this.driverWait = new WebDriverWait(driver, ScriptBase.DEFAULT_WEB_DRIVER_WAIT); // Same idea with JavaScriptExecutor. I choose to include it now so I can use it later. this.driverJSExecutor = (JavascriptExecutor) driver; }
-
Create function driven methods for each of the classes.
-
For example: you don't want a login method on every single page if the login method requires access to the username/password textbox that's only available on the login page.
-
For example this would be the login page:
LoginPage... click me to display
public class LoginPage extends BasePage { public LoginPage(WebDriver driver) { this.driver = driver; this.driverWait = new WebDriverWait(driver, ScriptBase.DEFAULT_WEB_DRIVER_WAIT); this.driverJSExecutor = (JavascriptExecutor) driver; } public void login(String email, String password, boolean shouldLoginWork) { goToLoginPage(); enterUsernameAndPassword(email, password); if(shouldLoginWork) { checkLoginSuccessMessage(); } else { checkLoginFailedMessage(); } } public void enterUsernameAndPassword(String email, String password) { enterDataIntoElement(By.id("spree_user_email"), email); enterDataIntoElement(By.id("spree_user_password"), password); clickElement(By.name("commit")); } public void checkLoginSuccessMessage() { WebElement loginSuccessMessage = driver.findElement( By.xpath("//div[@id='content']/div[contains(text(),'Logged in successfully')]")); assertThat(loginSuccessMessage.getText()).startsWith("Logged").endsWith("successfully"); } public void checkLoginFailedMessage() { WebElement loginFailedMessage = driver.findElement( By.xpath("//div[@id='content']/div[contains(text(),'Invalid email or password.')]")); MatcherAssert.assertThat(loginFailedMessage.getText(), equalTo("Invalid email or password.")); } }
-
The BasePage should implement navigation methods since navigation will be the same across all pages. Notice how the logout function belongs in this class since you can always logout no matter what page you're on.
BasePage... click me to display
public class BasePage extends CommonSeleniumTasks { public String baseURL = "http://spree.shiftedtech.com"; protected WebDriver driver; protected WebDriverWait driverWait; protected JavascriptExecutor driverJSExecutor; @Override protected WebDriver getDriver() { return driver; } @Override protected WebDriverWait getDriverWait() { return driverWait; } @Override protected JavascriptExecutor getDriverJSExecutor() { return driverJSExecutor; } public void goToHomePage() { clickElement(By.linkText("Home")); } public void goToLoginPage() { clickElement(By.linkText("Login")); } public void goToCart() { clickElement(By.id("link-to-cart")); } public void logOut() { clickElement(By.linkText("Logout")); checkSignoutSuccessMessage(); } public void checkSignoutSuccessMessage() { WebElement signoutSuccessMessage = driver.findElement( By.xpath("//div[@id='content']/div[contains(text(),'Signed out successfully.')]")); Assert.assertEquals(signoutSuccessMessage.getText(), "Signed out successfully."); } }
-
-
Create your test scripts. While it might take one or two more lines compared to a pure function driven framework, you have: increased readability, code reuse by implementing POM, and avoided monolithic Java files. Code reuse because you've implemented OOP through POM (extends SpreeScriptBase, extends BasePage, extends CommonSeleniumTasks), readability because the methods seem more like an English sentence, and avoided monolithic Java files because each function will be contained within the Java file that fits the function (login belongs to the login page, while navigation belongs to every page, etc):
homePage().goToLoginPage(); loginPage().login("shiftedtech0000@gmail.com", "shiftedtech", true); [from] home page, go to login page. [when on] login page, login(using email, and password, and expect result).
public class POMTestCase extends SpreeScriptBase { @Test() public void positiveLoginCaseWithFunctions() { homePage().goToLoginPage(); loginPage().login("shiftedtech0000@gmail.com", "shiftedtech", true); } @Test() public void negativeLoginCaseWithFunctions() { homePage().goToLoginPage(); loginPage().login("shiftedtech0000@gmail.com", "shiftedtec", false); } @Test() public void logoutCaseWithFunctions() { homePage().goToLoginPage(); loginPage().login("shiftedtech0000@gmail.com", "shiftedtech", true); loginPage().logOut(); } }
Click me to display this section
-
First setup Intellij to utilize Cucumber JVM
-
Add these dependencies to your pom.xml:
Dependencies... click me to display
<!-- https://mvnrepository.com/artifact/io.cucumber/cucumber-java This dependency allows a BDD framework to be created --> <dependency> <groupId>io.cucumber</groupId> <artifactId>cucumber-java</artifactId> <version>${cucumber-java.version}</version> </dependency> <!-- https://mvnrepository.com/artifact/io.cucumber/cucumber-testng This dependency allows a BDD framework to be created --> <dependency> <groupId>io.cucumber</groupId> <artifactId>cucumber-testng</artifactId> <version>${cucumber-testng.version}</version> </dependency> <!-- https://mvnrepository.com/artifact/net.masterthought/maven-cucumber-reporting This dependency allows better reporting but only for BDD tests --> <dependency> <groupId>net.masterthought</groupId> <artifactId>maven-cucumber-reporting</artifactId> <version>${cucumber-reporting.version}</version> </dependency> <!-- https://mvnrepository.com/artifact/io.cucumber/cucumber-expressions --> <dependency> <groupId>io.cucumber</groupId> <artifactId>cucumber-expressions</artifactId> <version>${cucumber-expressions.version}</version> </dependency> -
File > Settings > Plugins > Marketplace. Download Cucumber for Java and Gherkin. DO NOT INSTALL Substeps Intellij Plugin. Restart IDE after install.
-
-
Create a feature file in src/test/resources/features:
Feature: Spree Login Functionality - 1 Scenario: 1. Valid user with valid password Given an unvalidated user When user browses to "http://spree.shiftedtech.com" Then home page will display When user clicks "Navigation.Login" link Then login page will display When user enters "shiftqa01@gmail.com" into "LoginPage.EmailTextbox" And user enters "shiftedtech" at "LoginPage.PasswordTextbox" And user clicks on "LoginPage.LoginButton" button Then home page will display And login success message displays in "HomePage.LoginSuccessAlert" as "Logged in Successfully"
-
Right click on the word "Feature" within the feature file then select Run "Feature:..."
-
If you are unable to right click on the Feature keyword on the feature file, Go to File > Project Structure > Modules > Dependencies. Then for every io.cucumber dependency you find, set the Scope to Test. Retry the previous step.
-
Copy all the snippets that were generated in the output.
-
Reset every io.cucumber dependency Scope to Compile.
-
Create a step definition file within src/main/java/steps and paste the snippets that you copied.
-
Create a BDDRunner file in src/main/java/steps
package com.h1ddengames.com.shiftedtech.bdd.spree; import io.cucumber.testng.*; @CucumberOptions( //dryRun = true, /* Run just to check if the syntax if fine */ //tags = { "@Acceptance" }, /* Will run tests that only has the acceptance tag */ //tags = { "@Acceptance, @Functional"}, /* Will run any test that has both the acceptance tag and the functional tag */ //monochrome = true, /* */ features = {"src/test/resources/features/spree"}, /* Specify where the feature files are located */ glue = "com/h1ddengames/framework/steps/spree", /* Where are the step definitions located. Do not type /src/java/[main/test] */ plugin = { "pretty:target/cucumber-test-report/cucumber-pretty.txt", "html:target/cucumber-test-report/", "json:target/cucumber-test-report/cucumber-report.json", "junit:target/cucumber-test-report/test-report.xml" } ) public class BDDRunner extends AbstractTestNGCucumberTests { }
-
Implement the step definitions.
-
Right click on the BDDRunner then select Run BDDRunner.
Click me to display this section
Click me to display this section
Click me to display this section
Click me to display this section
Click me to display this section
Click me to display this section
Click me to display this section
Click me to display this section
Click me to display this section
-
A test can only be a test if you assert that something should happen.
-
For example:
// The success message contained in the WebElement successMessage should have the exact text "Logged in successfully" Assert.assertEquals(successMessage.getText(), "Logged in successfully");
-
-
A false positive is worse than a false negative because no one cares to look at a test when it passes.
- Example of false positive: being able to log in with an invalid username and/or password.
- Example of false negative: not being able to log in with a valid username and password.
-
Once the bug slips through this crack, it becomes much harder to find later on.