Page History

...

Lines 9-13 set up a very simple driver. In line 14, it is submitted it for execution and line 15 fails the test if it did not run successfully. Note that the interaction between the test and the actual runtime is mediated via the TestEnvironment interface. This allows us to write integration tests that are portable across all of the runtimes supported. In order to allow for the runtime to pefrom setup and teardown operations, we have to call it in the @Before and @After methods of the test class accordingly.

...

Integration tests can fail on the Client, the Driver or any of the Evaluators spawned by the test. In order to propagate the test failures from Driver and Evaluator back to the client, we use REEF's exception propagation mechanism. If a test fails on the Driver side, throw a "DriverSideFailure". For the task side, throw a "TaskSideFailure". And don't worry: The exception propagation itself is tested within the reef-tests module.

Registering your test / test suite

In order for us to run the new test (suite) as part of our release validation, please add it to org.apache.reef.tests.AllTestsSuite.