fi.jumi.api.drivers

Class Driver

java.lang.Object

fi.jumi.api.drivers.Driver

@NotThreadSafe
public abstract class Driver
extends Object

Each testing framework should provide its own Driver implementation so that the Jumi test runner will know how to run tests written using that testing framework.

Constructor Summary

Constructors

Constructor and Description
Driver()

Method Summary

Methods

Modifier and Type	Method and Description
abstract void	findTests(Class<?> testClass, SuiteNotifier notifier, Executor executor) Starts the execution of the tests in testClass.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

Driver

public Driver()

Method Detail

findTests

public abstract void findTests(Class<?> testClass,
             SuiteNotifier notifier,
             Executor executor)

Starts the execution of the tests in testClass.

The provided Executor should be used to run the tests, so that they can be executed in parallel, each test in a different thread.^[1] If the Runnables passed to executor are Serializable, then each of the tests in one class could potentially be executed on different machine in a server cluster.^{[citation needed]} Otherwise any potential clustering is at class-granularity^{[citation needed]} (which may be a hindrance for classes with many slow tests).

Parameters:

testClass - contains the tests to be executed.

notifier - through which Jumi is told about test executions.

executor - recommended for executing tests asynchronously, instead of running them synchronously in this method.

References:

[1]: tests_are_run_in_parallel