SmartUnit

Unit test utilities library

License

License

GroupId

GroupId

org.agileware
ArtifactId

ArtifactId

smartunit
Last Version

Last Version

0.10.2
Release Date

Release Date

Type

Type

jar
Description

Description

SmartUnit
Unit test utilities library
Project URL

Project URL

https://github.com/rlogiacco/smartunit
Source Code Management

Source Code Management

https://github.com/rlogiacco/SmartUnit

Download smartunit

How to add to project

<!-- https://jarcasting.com/artifacts/org.agileware/smartunit/ -->
<dependency>
    <groupId>org.agileware</groupId>
    <artifactId>smartunit</artifactId>
    <version>0.10.2</version>
</dependency>
// https://jarcasting.com/artifacts/org.agileware/smartunit/
implementation 'org.agileware:smartunit:0.10.2'
// https://jarcasting.com/artifacts/org.agileware/smartunit/
implementation ("org.agileware:smartunit:0.10.2")
'org.agileware:smartunit:jar:0.10.2'
<dependency org="org.agileware" name="smartunit" rev="0.10.2">
  <artifact name="smartunit" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.agileware', module='smartunit', version='0.10.2')
)
libraryDependencies += "org.agileware" % "smartunit" % "0.10.2"
[org.agileware/smartunit "0.10.2"]

Dependencies

compile (4)

Group / Artifact Type Version
junit : junit jar 4.12
org.mockito : mockito-core jar 1.10.19
org.seleniumhq.selenium : selenium-java Optional jar 2.47.1
org.hamcrest : hamcrest-library Optional jar 1.3

test (4)

Group / Artifact Type Version
info.cukes : cucumber-spring jar 1.2.4
org.springframework : spring-context jar 4.1.6.RELEASE
info.cukes : cucumber-junit jar 1.2.4
org.springframework : spring-test jar 4.1.6.RELEASE

Project Modules

There are no modules declared in this project.

SmartUnit is intended to be a place where unit test utility and helper classes can be collected to be shared.

SmartUnit artifacts, including sources and javadocs, are available on the central Maven repository.

Have a look at our wiki for more information.

TravisCI Build Status

Release

Before initiating a release it's strongly adviced to execute the full integration test suite which is normally not executed during the common install phase. During the release phase the additional ie, chrome and firefox Maven profiles are enabled which execute browser specific tests: this means the releaser need to have a Windows box (due to Internet Explorer dependency) with the Selenium IE and Chrome drivers installed (Firefox does not need a driver). The easiest way to provide the additional drivers path is to use system properties:

mvn integration-test -Pfirefox,chrome,ie -Dwebdriver.ie.driver=<path>\IEDriverServer.exe -Dwebdriver.chrome.driver=<path>\chromedriver.exe

Please note that the Selenium driver for Internet Explorer requires to set the protection mode to be the same on all zones, otherwise the browser will detach unexpectedly.

Do not proceed to the release process unless the above command executes without errors

To prepare and perform the release multiple unix like commands needs to be on the path, the simplest way to have them all is to perform the release within the Git Bash shell.

The gpg command must be on the PATH in order to sign the artifacts so it's better to double check the environment configuration and your passphrase by running:

$> gpg --output test.sig --sign <anyfile>

Additionally git, ssh and ssh-agent executables must be on the PATH, the latter with your Github SSH key loaded:

$> eval$(ssh-agent)
$> ssh-add ~/.ssh/id_rsa
$> ssh -T [email protected]

Release Keys

Three keys are required for the release: a GPG one to sign the artifacts, an RSA one to commit release changes on Github and an RSA one to push the artifacts onto the Maven Central repository (hosted by Sonatype).

You can use the same RSA key for both Github and Sonatype to reduce the amount of passwords and configurations if you wish.

Versions

Version
0.10.2
0.10.1
0.10.0
0.9.0
0.8.0
0.7.0
0.6.0