This is the homepage for the Orasi Selenium Core libraries. These libraries contain both original code created by Orasi developers and open source code from various other projects which are listed further down. With these libraries, consumers have access to extended functionality for creating testing suites for Web Applications and API Web Services.
Orasi is a software and professional services company focused on software quality testing and management. As an organization, we are dedicated to best-in-class QA tools, practices and processes. We are agile and drive continuous improvement with our customers and within our own business.
Licensed under BSD License
It is recommend to use an IDE profile in order to promote code consistency and reduce unneeded code changes in your SCM. In the etc folder of this project exists profiles tailored to achieve this.
The core code uses the Java-based Selenium webdriver for GUI testing. It takes the standard Selenium-defined WebElement and divides them into more consumer-friendly Elements, whose names are commonly found in HTML DOMs. The following are Elements, and the prefixes used in the code to identify them, as well as examples using the naming conventions:
| Element | Prefix | Example |
|---|---|---|
| Button | btn | btnContinue |
| Checkbox | chk | chkAgreeToTermsAndConditions |
| Label | lbl | lblHeader |
| Link | lnk | lnkCancel |
| Listbox | lst | lstStates |
| Radiogroup | rad | radYesOrNo |
| Textbox | txt | txtUsername |
| Webtable | tab | tabMemberNames |
| Element (Generic Web Element) | ele | eleImage |
All elements utilize the Orasi-developed TestReporter which extends the TestNG Reporter by concatenating a timestamp and HTML formatting for use in viewing the report in a web browser. This allows for a functional audit which can ensure requirements are being met by the automated test, as well as provide steps to reproduce a defect when one occurs.
These libraries contain a SOAP API testing solution which leverages Java and W3C functionalities to dynamically build requests at runtime, modify the requests, transmit and receive SOAP messages, and parse responses for field-level values with which validation can be performed.
These libraries contain a SOAP API testing solution which leverages the Apache HttpClient libraries. Full XML and JSON support is included to parse responses for field-level values with which validation can be performed.
This project is designed to have a Jenkins CI instance hook into this repository and detect when changes are pushed to the Master branch. Ideally, this trigger will be changed to look for code changes pushed by developers, thereby triggering a new build to test the new application code.
The capabilities of the Sauce Labs VM farm are harnessed to test the OS-Browser configurations required by the project. The Jenkins instance uses a local VM to spin up a webdriver for a test and the webdriver sends the commands to the remote VM to be executed.
-
TestReporter: Contains results for individual tests using the TestNG-extended reporting.
-
Jenkins CI: Contains results for individual tests using the TestNG-extended Orasi reporter. Also, keeps a build history to show the relative stability of past builds.
-
Allure Reports: Contains results for individual tests using Allure Reporter. Reports generate can range from Automation issues, Application issues, grouping by Features and Stories as well is high level Steps giving high level Executive Reports.
-
Sauce Labs: Contains results for individual tests as well as captures videos and screenshots.
This class is designed to be extended by test classes and can be passed into page classes. It houses test environment data and remote WebDrivers as well as page class methods used to sync page behavior. The need for this arose due to the parallel behavior that indicated that WebDriver instances were crossing threads and testing on the wrong os/browser configurations.
Also contained in this class is the determination as to whether the test should be executed locally or remotely based on a TestNG parameter. Once this is established, a webdriver is created and executed appropriately.
This is an extention of WebDriver that grants access to the Element interfaces by giving them their own find method ( i.e. driver.findButton(By by) ), but also making interface methods easier to reach such as setting timeouts, or executing Javascript.
More info on usage and availible methods in the VersionHistory
The Page Object Model was utilized for this core. With this framework, a single GUI web application page and all of the objects and interactions contained therein, are mapped to a single Java class. Selenium web elements for a particular page are redefined using the user-defined elements such as button, link , etc. Below is an example:
@FindBy(xpath = "//*[@id=\"tcom-main-nav\"]/ul/li[3]/button")
private Button btnYourLocation;
When a page class is instantiated, all @FindBy elements are initialized as proxies, or skeletons, which are not full objects that can be manipulated or interacted with, but do inherit all properties of a the object type (here, btnYourLocation inherits all methods and fields from the Button class). When an element is actually invoked
btnYourLocation.click();
Selenium grabs the actual object to allow the test/user to interact with the element.
A flow through an web application is represented by a test class. Each test class is comprised of:
* TestNG annotated methods (e.g. @BeforeMethod, @Test, @AfterMethod, etc.)
* Creation of a DataProvider method to data-drive tests
* Instantiation of the TestEnvironment class (i.e. create the web driver)
* Instantiation of Page Class objects and associated methods to carry out the
automated flow
Execution of tests is conducted through the TestNG framework which, given our Test Class framework, requires a TestNG XML. An example XML follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite" parallel="tests" thread-count="8">
<parameter name="browserUnderTest" value="firefox" />
<parameter name="environment" value="staging" />
<parameter name="runLocation" value="local" />
<parameter name="browserVersion" value="" />
<parameter name="operatingSystem" value="windows" />
<test name="Test">
<classes>
<class name="com.orasi.bluesource.features.manageEmployees.AddEmployee" />
</classes>
</test> <!-- Test -->
</suite> <!-- Suite -->
The various parts are described below:
| Attributes | Description | Acceptable Values |
|---|---|---|
| name="AddEmployee" | Contains the test suite name used by TestNG reporting | Any value that helps uniquely identify the suite |
| parallel="false" | Determines what, if anything, is to be executed in parallel | false, methods, tests, classes, instances |
| parameter name="browserUnderTest" value="chrome" | parameter and value used to create the driver; here, the browser type is defined | Sauce Labs: safari, chrome, firefox, iexplore |
| parameter name="environment" value="" | defines a particular environment to test | User-defined in EnvironmentURLs.properties file |
| parameter name="runLocation" value="local" | defines the run location | local or remote |
| parameter name="browserVersion" value="" | defines the browser version to use | Any value available is valid; with Sauce Labs, a blank value will trigger the latest version to be used |
| parameter name="operatingSystem" value="windows" | defines the operating system to use | Sauce Labs: MAC OS X 10.10, MAC OS X 10.9, Windows 7, Windows 8.1 |
| test name="AddEmployee" | Contains the test name used by TestNG reporting | Any value that helps uniquely identify the test and is not used by another test in the same suite. |
| class name="com.orasi.bluesource.features.manageEmployees.AddEmployee" | Path of the class to be executed | User-defined and dependent of the build path |
These resources are being used directly, or have been extended upon.
- Selenium: The base library that allows for automation of web browsers.
- TestNG: Test execution framework that extends JUnit tests and allows more flexibility for testing.
- Sauce Labs: Facilitates the use of using the Sauce Lab VM farm as a remote Selenium grid on which to execute tests.
- Apache HttpClient Used to transmit and receive SOAP and REST message requests and responses.
- Allure Reports for TestNG: Generates high level executive reporting