You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Folke Behrens (JIRA)" <ji...@apache.org> on 2010/06/27 01:19:50 UTC
[jira] Created: (CASSANDRA-1233) Tests use "assert" instead of
JUnit's assertTrue()
Tests use "assert" instead of JUnit's assertTrue()
--------------------------------------------------
Key: CASSANDRA-1233
URL: https://issues.apache.org/jira/browse/CASSANDRA-1233
Project: Cassandra
Issue Type: Improvement
Components: Core
Reporter: Folke Behrens
A lot of test classes use the assert statement instead of JUnit's assertTrue() or assertFalse(). Though JUnit catches AssertionErrors by "assert" it's still too risky for explicit testing because assertions could accidentally be switched off.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CASSANDRA-1233) Tests use "assert" instead of
JUnit's assertTrue()
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-1233.
---------------------------------------
Resolution: Not A Problem
Requiring tests to be run with -ea is a good idea anyway, since we use asserts in non-test code as well.
> Tests use "assert" instead of JUnit's assertTrue()
> --------------------------------------------------
>
> Key: CASSANDRA-1233
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1233
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Folke Behrens
>
> A lot of test classes use the assert statement instead of JUnit's assertTrue() or assertFalse(). Though JUnit catches AssertionErrors by "assert" it's still too risky for explicit testing because assertions could accidentally be switched off.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.