Skip to content
ScalaWebTest is a library for writing ScalaTest/Selenium based integration tests for web applications. It helps you with your basic setup and provides a new and very efficient approach to testing.
Scala Java HTML Dockerfile
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.


Type Name Latest commit message Commit time
Failed to load latest commit information.


Build Status Join the chat at

ScalaWebTest is a library for writing ScalaTest/Selenium based integration tests for websites. It helps you with your basic setup and provides a new and very efficient approach to testing.

In manufacturing it is common to use gauges (also called checking gauges or testing gauges) to verify whether a workpiece meets predefined criteria and tolerances. ScalaWebTest transfers this concept to the world of web integration testing. You can define a gauge in HTML, and use it to verify your web application. This greatly improves the readability, simplicity of your integration tests.

Read the full documentation on our website

Getting Started with development


Get familiar with the sbt build tool because this is used to manage the project.

See Getting Started Guide

Compile, test, package

$ sbt compile test package

Run whole integration test

Before running the integration tests, you will need to configure WEBDRIVER_CHROME_DRIVER environment variable. To do so, run the following command:

$ export WEBDRIVER_CHROME_DRIVER="$(which chromedriver)"

And then run the tests using the command below:

$ sbt inttest

This will start a Jetty server, executes the integration tests and stops the server again.

Start Jetty server and run single tests

If you would like to run the Jetty server and in parallel work on integration tests and some code changes, you can do the following:

# Enter the sbt console first, enter 'sbt' in root folder
$ sbt

# Start Jetty server
sbt> jetty:start

# Or if you would like that sbt automatically restarts Jetty after code changes then do:
sbt> ~jetty:start

# Open separate command window and enter the sbt console agains
# Run a single integration tests
sbt> it:testOnly org.scalawebtest.integration.gauge.ContainsSpec

How to Release


Create the following file ~/.sbt/1.0/plugins/gpg.sbt

Add the following line to gpg.sbt addSbtPlugin("com.jsuereth" % "sbt-pgp" % "1.1.1")

Copy the private key (Sonatype PGP Private and Public Key from our company password store), to ~/.sbt/gpg/secring.ast

Create the file ~/.sbt/1.0/sonatype.sbt

Add the following content and replace username, password

credentials += Credentials("Sonatype Nexus Repository Manager",
                           "<your username>",
                           "<your password>")


The release process of ScalaWebTest is currently done manually. The process is done as follows:

  1. Switch the version in build.sbt to that which is to be released (e.g. from 0.0.1-SNAPSHOT to 1.0.0)
  2. In your command line type in the following:
    1. the long way:
      1. sbt - enters the sbt interactive mode r. + clean - deletes all generated files (target)
      2. + compile - compiles the main sources
      3. + doc - generate scaladoc
      4. mimaReportBinaryIssues - execute the Migration Manager to verify binary compatibility
      5. inttest - compile and run the integration tests
      6. + publishSigned - creates all of the below plus the poms
      7. Enter the Sonatype PGP Key Password as stored in our company password store
      8. Go to verify and close the staging repository
      9. exit - exits the sbt interactive mode
  3. Commit your changes with the commit message "Release x.x.x" (e.g. Release 1.0.0)
  4. Tag this commit with the release version git tag -a x.x.x -m "x.x.x"
  5. Switch the version in build.sbt to the snapshot version (e.g. from 1.0.0 to 1.0.0-SNAPSHOT) and update the documentation if needed
  6. Finally commit those changes with the commit message "Bump version to x.x.x-SNAPSHOT" (e.g. Bump version to 1.0.0-SNAPSHOT)
  7. Push you changes and the tag
You can’t perform that action at this time.