New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CASSANDRA-16012 sstablesplit tool unit testing #762
Conversation
test/unit/org/apache/cassandra/tools/StandaloneSplitterWithCQLTesterTest.java
Outdated
Show resolved
Hide resolved
Well that was a surprise @yifan-c The new custom junit executor was wrong. Adding that new test method you suggested I noticed I couldn't get any failures. The tests were green despite I knew they were broken. I found out the new executor was swallowing all errors. So I removed that and overrode the Now everything works as expected, it's cleaner and has the extra test method. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. Like the overriding approach better. It's cleaner.
So.. in order to make the custom runner correctly ignores After
or so and not swallow errors, the override need to just return the input statement. In the super class, the runner detects if after exists and run.
@Override
protected Statement withAfters(FrameworkMethod method, Object target, Statement statement)
{
return statement;
}
test/unit/org/apache/cassandra/tools/StandaloneSplitterWithCQLTesterTest.java
Outdated
Show resolved
Hide resolved
test/unit/org/apache/cassandra/tools/StandaloneSplitterWithCQLTesterTest.java
Outdated
Show resolved
Hide resolved
Latest review comments pushed. Thx. |
test/unit/org/apache/cassandra/tools/StandaloneSplitterWithCQLTesterTest.java
Show resolved
Hide resolved
e726554
to
5d01484
Compare
5d01484
to
f9b552d
Compare
CI for latest force push here |
No description provided.