---

layout: page title: Tests

Samza's unit tests are written on top of JUnit, and license checking is done with Apache Rat. An extensive integration test suite is not currently available. This is being actively worked on in SAMZA-6 and SAMZA-14.

Running Unit Tests Locally

To run all tests, and license checks:

./gradlew clean check

To run a single test:

./gradlew clean :samza-core:test -Dtest.single=TestSamzaContainer

Test results are located in:

<module name>/build/reports/tests/index.html

Testing Scala and Java

Samza's unit tests can also be run against all supported permutations of Scala and Java.

To run the tests against a specific combination:

./gradlew -PscalaVersion=2.10 -PyarnVersion=2.4.0 clean check

To run Samza's unit tests against all permutations, run:

bin/check-all.sh

When run on Linux, this command requires you to set three environment variables:

JAVA6_HOME is not set.
JAVA7_HOME is not set.
JAVA8_HOME is not set.

On Mac, check-all.sh will default to the appropriate path for each environment variable if it's not already set:

JAVA6_HOME is not set.
JAVA6_HOME defaulted to /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
JAVA7_HOME is not set.
JAVA7_HOME defaulted to /Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home
JAVA8_HOME is not set.
JAVA8_HOME defaulted to /Library/Java/JavaVirtualMachines/jdk1.8.0_20.jdk/Contents/Home

Travis CI

Travis CI has been configured to run Samza‘s unit tests after every commit to Samza’s master branch. The test results are mailed to the developer mailing list, and posted in the IRC channel.