---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52306/
---
Review request for geode.
Repository: geode
Description
---
GEODE-1769:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52269/
---
(Updated Sept. 27, 2016, 5:25 p.m.)
Review request for geode, Jared Stewart,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52306/
---
(Updated Sept. 27, 2016, 6:13 p.m.)
Review request for geode, Jared Stewart,
Some of the very basic best practices for JUnit:
1) never catch an unexpected exception
Yes:
public void myTest() throws Exception {
doSomething();
validation();
}
No:
public void myTest() {
try {
doSomething();
validation();
} catch (Exception e) {
fail(e.getMessage());
}
We are using Categories to aid in separating UnitTests, IntegrationTests,
etc.
A UnitTest is:
/**
* JUnit Test Category that specifies a test with very narrow and well
defined
* scope. Any complex dependencies and interactions are stubbed or mocked.
*
* A {@code UnitTest} should not do any
