kevinrr888 opened a new issue, #4903:
URL: https://github.com/apache/accumulo/issues/4903
**Is your feature request related to a problem? Please describe.**
MultipleStoresIT should be refactored to function more similarly to how
other Fate tests are run (e.g., FateIT) where the two stores are tested in
their own separate concrete classes. The existing tests use FateTestRunner, but
that doesn't work as nicely here since those function under the assumption of
one of each store type, which is not the case with this new test.
**Describe the solution you'd like**
MultipleStoresIT to be an abstract class implemented by two new classes:
UserMultipleStoresIT and MetaMultipleStoresIT, and a new interface similar to
how FateTestRunner is currently used.
**Describe alternatives you've considered**
The current impl is another alternative, which works but isn't as nice as
the above suggestion: it isn't consistent with the structure of the existing
Fate tests, and consider this in the current impl:
```
@Test
public void testReserveUnreserve() throws Exception {
testReserveUnreserve(FateInstanceType.META);
testReserveUnreserve(FateInstanceType.USER);
}
```
If the first call fails, USER will not be run. Would be nicer to have both
run irrespective of order and failures.
**Additional context**
See comment
https://github.com/apache/accumulo/pull/4524#discussion_r1702305419
See changes from https://github.com/apache/accumulo/pull/4524
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
