Carina is a Java-based test automation framework that unites all testing layers: Mobile applications (web, native, hybrid), WEB applications, REST services, Databases.

• Carina framework is built on top of most popular open-source solutions like Selenium, Appium, TestNG allowing to reduce dependence on specific technology stack.

• Carina supports all popular browsers (IE, Safari, Chrome, Firefox) and mobile devices (iOS/Android). Special feature for mobile domain: it reuses test automation code between IOS/Android up to 70-80%.

• As far as our framework is built in Java, it is cross-platform. Tests may be easily executed both on Unix or Windows OS. All you need is JDK 8 installed.

• Framework supports different types of databases - both relational and nonrelational (MySQL, SQL Server, Oracle, PostgreSQL), providing amazing experience of DAO layer implementation using MyBatis ORM framework.

• API testing is based on Freemarker template engine. It enables great flexibility in generating REST requests and responses are dynamically changed by incoming arguments.

TRY DEMO PROJECT NOW

• Initial setup
• Project structure
• Configuration and execution
• Web UI automation
• Web services API automation
• Mobile automation
• Database access setup
• Data-providers usage
• Git configuration
• License

• Install and configure JDK 1.8+
• Install and configure Apache Maven 3.5.2+
• Download and start the latest Selenium standalone server
• Download the latest version of Eclipse and install TestNG plugin

The easiest way to initialize new project is to use Carina archetype, you will get correct project structure along with test samples:

mvn archetype:generate -DarchetypeGroupId=com.qaprosoft \
                       -DarchetypeArtifactId=carina-archetype \
                       -DarchetypeVersion=1.0 \
                       -DgroupId=<your_groupId> \ 
                       -DartifactId=<your_artifactId> \ 
                       -Dname="<you_proj_name>" \
                       -Durl=<your_proj_url> \
                       -Dversion=<your_proj_version>

If any attribute contains spaces, it should be set in quotes (e.g.: -Dname="Hello World"). In above Maven command you have to specify 5 attributes while the first 3 should be left unchanged. Let's go through these attributes:

If generation is successfully complete, you would see a new project folder with a name equal to the artifactId attribute specified during generation, so navigate to that folder (where pom.xml is located) and execute the following Maven task:

mvn clean eclipse:eclipse

By executing this command, Maven should resolve all dependencies, downloading required libraries to your local repository and generating Eclipse classpath. Before importing new project to Eclipse, you should link your IDE to your Maven repository by executing the following task:

mvn -Dworkspace=<path_to_workspace> eclipse:configure-workspace

Here you have to specify the absolute path to the Eclipse workspace. After that, restart Eclipse IDE. Now you can import generated projects such as "Existing Java Project" into Eclipse IDE. Generate Eclipse workspace using command:

mvn clean eclipse:eclipse

Now you are ready to import project into Eclipse.

Carina test project is structured as a standard Maven project:

carina-demo
|-- pom.xml
|-- src/test/java        
|-- src/test/resources
    |-- api
    |-- testng_suites
    |-- xls
|-- src/main/java
|-- src/main/resources
    |-- l18n

• src/test/java - contains test classes organized using TestNG annotations

• src/test/resources - contains TestNG xml files, API templates and XLS data providers

• src/main/java - contains page object classes, API domains and additional utilities

• src/main/resources - contains l18n bundles, configuration properties files and MyBastis profiles if needed

There are multiple properties files located in src/main/resources:

• _api.properties - API test endpoints reference
• _config.properties - global test configuration
• _database.properties - database connection properties
• _email.properties - emailable reports config
• _testdata.properties - test user credentials

All properties may be retrieved in test using R class:

R.API.get("GetUserMethods")
R.CONFIG.get("browser")
R.DATABASE.get("db.url")
R.EMAIL.get("title")
R.TESTDATA.get("user.email")

Default config properties can be obtained by

Configuration.get(Parameter.EXTRA_CAPABILITIES)

All project configuration properties are located in _config.properties file. In the table below we are providing description for most of the parameters:

Most of the properties may be read in the following way:

Configuration.get(Parameter.URL) // returns string value
Configuration.getBoolean(Parameter.AUTO_SCREENSHOT) // returns boolean value
Configuration.getInt(Parameter.SMALL_SCREEN_WIDTH) // returns integer value
Configuration.getDouble(Parameter.BROWSER_VERSION) // returns double value

In some cases it is required to support multiple environments for testing. Let's assume we have STAG and PROD environments which have different application URLs. In this case we need to specify the following properties in _config.properties:

env=DEMO
STAG.url=http://stag-app-server.com
PROD.url=http://prod-app-server.com

And get env-specific argument in test the following way:

Configuration.getEnvArg("url")

As a result you switch between environments just changing env argument in _config.properties file.

There are a several options to execute the test: you may run test suite from Eclipse IDE or initiate test execution from the console using Maven Surefire plugin built into Carina framework. Before running tests make sure you have downloaded Selenium standalone server jar file and started it by the following command:

java -jar selenium-server-standalone-3.6.0.jar

To run the test suite from Eclipse IDE, just select the required TestNG xml file: Right click > Run As > TestNG suite

To run the same test suite from the console, navigate to the test project root (where pom.xml is located) and execute the following command:

mvn clean -Dsuite=api test

In the table below we are providing description for most important WEB parameters:

TODO

We could provide any Appium capabilty in _config.properties file using capabilities.< name >=< value > format. In the table below we are providing description for the most popular mobile capabilities:

#=============== Android Mobile ======================#
capabilities.deviceName=Samsung_Galaxy_J5
capabilities.app=s3://qaprosoft.com/android/myapk.*-release.apk
capabilities.skipUnlock=true
capabilities.noSign=true
capabilities.automationName=uiautomator2
capabilities.newCommandTimeout=180
capabilities.platformName=ANDROID
capabilities.autoGrantPermissions=true
#=====================================================#

#=================== iOS Mobile ======================#
capabilities.autoAcceptAlerts=true
capabilities.app=/opt/apk/my-apk.app
capabilities.automationName=XCUITest
capabilities.newCommandTimeout=180
capabilities.platformName=IOS
#=====================================================#

ExtendedWebElement is an extended version of selenium WebElement which you can find in org.openqa.selenium package. The best thing in using ExtendedWebElement is that you can use both old methods of WebElement and new more convenient Carina methods.

The easiest way to find ExtendedWebElement is using annotation @FindBy. The @FindBy annotation is used to locate one or more ExtendedWebElements using a single criterion. The list of criteria is standard:

• className
• css
• how...using
• id
• linkText
• name
• partialLinkText
• tagName
• xpath

    @FindBy(name = "Hybrid")
    private ExtendedWebElement hybridUnits;

    @FindBy(id = "com.ua.record.debug:id/spinner_text")
    private List <ExtendedWebElement> unitsVersions;

Most usable methods are reperesented in the table bellow:

You can simply transform ExtendedWebElement to WebElement using getElement() method. After this it's possible to operate with standard WebElement methods.

   Point point = element.getElement().getLocation();
   Dimension dim = element.getElement().getSize();

TODO

TODO

1). Fork repository https://github.com/qaprosoft/carina to your own user.

2). Clone your fork to your local machine:

git clone [email protected]:your_fork_url/carina.git

3). git remote add origin <your_fork_url> (can be already added)

4). git fetch origin

5). git remote add upstream [email protected]:qaprosoft/carina.git

6). git fetch upstream

7). git checkout -b work_local_branch upstream/master

And then after adding files (git add ...) use git commit (add description) and thenpush:

git push origin work_local_branch:work_remote_branch

And on https://github.com/qaprosoft/carina you will see possibility to "Compare & Pull Request"

We propose to use our configured java code formatter for Eclipse. It is available here https://github.com/qaprosoft/carina/carina_formatter.xml

To use same formatter in IntelliJ IDEA you should installEclipse Code Formatter

And configure it.

Code - Apache Software License v2.0

Documentation and Site - Creative Commons Attribution 4.0 International License