public class MD5SumTest
extends junit.framework.TestCase
| Constructor and Description |
|---|
MD5SumTest() |
| Modifier and Type | Method and Description |
|---|---|
void |
testMD5Sum() |
void |
testOOMEMD5Sum()
Note that this test creates a large 100MB file in /tmp
and then does an md5sum on the file.
|
assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertFalse, assertFalse, assertNotNull, assertNotNull, assertNotSame, assertNotSame, assertNull, assertNull, assertSame, assertSame, assertTrue, assertTrue, countTestCases, createResult, fail, fail, failNotEquals, failNotSame, failSame, format, getName, run, run, runBare, runTest, setName, setUp, tearDown, toStringpublic void testMD5Sum()
throws java.lang.Exception
java.lang.Exceptionpublic void testOOMEMD5Sum()
throws java.lang.Exception
<junit forkmode="once" fork="yes" printsummary="off" showoutput="yes"
haltonfailure="${halt-tests-on-failure}"
failureproperty="junit_test_failure" maxmemory="256m">
The new implementation uses less memory and thus passes the test below when ran
from Junit CLI.java.lang.Exception - something bad happened