[REEF-1352] Add exception classes for integration tests

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: REEF.NET
• Assignee: Unassigned
• Reporter: Markus Weimer
• Created: 22/Apr/16 20:22
• Updated: 30/Oct/17 14:51
• Resolved: 30/Oct/17 14:51

Description

We currently rely on ad-hoc exception messages in the REEF.NET integration tests. Once the work to properly propagate exceptions from Evaluator to Driver to Client is done, we can do better than that. Namely, I propose to introduce a set of new exception types in the Org.Apache.REEF.Tests.Exceptions namespace:

Expected Exceptions

• DriverSideExpectedException: The test expects this exception and will check its contents (cause, message) to decide whether the test passes.
• EvaluatorSideExpectedException: Same, but on the driver side.

Exceptions indicating test failure

• DriverSideTestFailure: The test failed because of a check on the Driver side.
• EvaluatorSideTestFailure: Same, but on the driver side.

Exceptions indicating bugs in untested parts of REEF

• DriverSideSystemException: The test encountered unexpected behavior that it didn't test for. In other words: A change broke the test.
• EvaluatorSideSystemException: Same, but on the driver side.

Issue Links

• Is contained by: REEF-1271 Add better test reporting APIs to REEF.NET
• is related to: REEF-1271 Add better test reporting APIs to REEF.NET