reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (REEF-1352) Add exception classes for integration tests
Date Fri, 22 Apr 2016 20:23:13 GMT

     [ https://issues.apache.org/jira/browse/REEF-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Markus Weimer updated REEF-1352:
--------------------------------
    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.

  was:
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.


> Add exception classes for integration tests
> -------------------------------------------
>
>                 Key: REEF-1352
>                 URL: https://issues.apache.org/jira/browse/REEF-1352
>             Project: REEF
>          Issue Type: New Feature
>          Components: REEF.NET
>            Reporter: Markus Weimer
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message