/** Test Exprs. * See http://www.radford.edu/itec380/2021spring/Homeworks/Project/ * * This file includes both some specific tests for Z0 and Z1, * as well as some helper-functions which are helpful for Z0-Z3. * HOWEVER, they aren't a cure-all -- * no tests are made against the expected internal representation (Expr-tree). * For example, testParseToString just checks that parse and * 'toString' are inverses of each other; if they are both * the identity function, it would pass all tests. * * Compiling this function may generate a warning * ('unchecked generic array creation', due to using Arrays.asList * and varargs). * * For compiling with junit (if your IDE doesn't automatically recognize it), * see the note at end of this file. * * @author Ian Barland * @version 2021.Nov.08 */ import java.util.*; public class ExprTest extends junit.framework.TestCase { /** Manually call our test-functions * (in case calling JUnit from your IDE isn't easy). */ public static void main(String... args) { ExprTest t = new ExprTest(); t.setUp(); t.testMyStuff(); t.tearDown(); t.setUp(); t.testTowardsAutomating(); t.tearDown(); t.setUp(); t.testParseToString(); t.tearDown(); t.setUp(); t.testEval(); t.tearDown(); // alternately, this might work, but might require declaring a package // rather than the un-named package. // org.junit.runner.JUnitCore.main("ExprTest"); dbg("Testing complete.\n"); } static final double TOLERANCE = 0.000001; String e0 = "43"; String e1 = "<43>"; String e2 = "[add 4 3]"; String e3 = "<<[add 4 <3>]>>"; String e4 = "[add <43> [mul 42 3]]"; java.util.List> allTests; /* allTests should be a list of pairs: * a Z0 Expr, and what that expression evaluates to. * Use a Double, for Num values. */ // Some expressions to test in a non-automated way: public void testMyStuff() { // parsing dbg("testMyStuff: parsing\n"); assertEquals( Expr.parse("34"), new Num(34) ); assertEquals( Expr.parse("-34"), new Num(-34) ); assertEquals( Expr.parse("<34>"), new Paren( new Num(34) ) ); assertEquals( Expr.parse("[add 3 4]"), new BinOp( "add", new Num(3), new Num(4) ) ); assertEquals( Expr.parse("[add 3 4]"), new BinOp( "add", new Num(3), new Num(4) ) ); assertEquals( Expr.parse("[add <34> [mul 3 4]]"), new BinOp( "add", new Paren(new Num(34)), new BinOp( "mul", new Num(3), new Num(4)) ) ); assertEquals( Expr.parse("zero 3 ? 7 : 9"), new IfZero( new Num(3), new Num(7), new Num(9) ) ); assertEquals( Expr.parse("zero <34> ? [add <34> [mul 3 4]] : zero 3 ? 7 : 9"), new IfZero( new Paren(new Num(34)), new BinOp("add", new Paren(new Num(34)), new BinOp("mul", new Num(3), new Num(4)) ), new IfZero( new Num(3), new Num(7), new Num(9) ))); //eval dbg("testMyStuff: testing eval\n"); assertEquals( new Num(34).eval(), new Num(34) ); assertEquals( Expr.parse("<34>").eval(), new Num(34) ); assertEquals( Expr.parse("[add 3 4]").eval(), new Num(7) ); assertEquals( Expr.parse("[sub 3 4]").eval(), new Num(-1) ); assertEquals( Expr.parse("[mul 3 4]").eval(), new Num(12) ); assertEquals( Expr.parse("zero 3 ? 4 : 5").eval(), new Num(5) ); assertEquals( Expr.parse("zero 0 ? 4 : 5").eval(), new Num(4) ); assertEquals( Expr.parse("zero [sub 2 2] ? [add 1 2] : [add 3 4]").eval(), new Num(3) ); assertEquals( Expr.parse("zero 7 ? [add 3 4] : 5").eval(), new Num(5) ); // toString dbg("testMyStuff: testing toString\n"); assertEquals( Expr.parse("34").toString(), "34"); assertEquals( Expr.parse("<34>").toString(), "<34>"); assertEquals( Expr.parse("[add 3 4]").toString(), "[add 3 4]"); assertEquals( Expr.parse("[sub 3 4]").toString(), "[sub 3 4]"); assertEquals( Expr.parse(" [ mul 3 4 ] ").toString(), "[mul 3 4]"); assertEquals( Expr.parse("zero 3 ? 4 : 5").toString(), "zero 3 ? 4 : 5"); assertEquals( Expr.parse("zero 0 ? [add 3 4] : 5").toString(), "zero 0 ? [add 3 4] : 5"); // Add more specific tests here, // if you want things more specific that provided via adding to `allTests` below. } public void testTowardsAutomating() { dbg("testTowardsAutomating\n"); // we can automate checking that parse! is the (right)inverses of expr->string: for( String e : Arrays.asList(e0,e1,e2,e3,e4) ) { assertEquals( Expr.parse(e).toString(), e ); } // Though we also want to check that e0..e4 eval to 43,43,7,7,169 respectively. Iterator exps = Arrays.asList(e0,e1,e2,e3,e4).iterator(); Iterator dubs = Arrays.asList(43.0, 43.0, 7.0, 7.0, 169.0).iterator(); while (exps.hasNext()) { Num actual = (Num)(Expr.parse(exps.next()).eval()); Num expected = new Num(dubs.next()); assertEquals( actual, expected ); } // The above is a promising start, to automating tests. // Okay, we'll generalize the above to a more complete test-harness. // One thing, is that we don't want to have two parallel-lists; // instead keep a list of pairs. // Three sorts of tests we want to make, for many different exprs: assertEquals( Expr.parse("[add 4 3]"), new BinOp("add", new Num(4), new Num(3)) ); assertEquals( Expr.parse("[add 4 3]").eval(), new Num(7) ); assertEquals( Expr.parse("[add 4 3]").toString(), "[add 4 3]"); } /** * Sets up the test fixture. * * Called before iphry test case method. */ public void setUp() { /* allTests should be a list of pairs: * a Z0 Expr, and what that expression evaluates to. * Use a Double, for Num values. */ allTests = java.util.Arrays.asList( /* Z0 tests: */ new Pair( "7", 7 ) ,new Pair( "7", 7.000000001 ) // confirm that we compare `double`s merely within a tolerance ,new Pair( "<3>", 3 ) ,new Pair("[add 3 4]", 7 ) ,new Pair("[mul 3 4]", 12 ) ,new Pair("[add [add 3 4] [mul 3 4]]", 19 ) ,new Pair("[mul <3> <[add 2 3]>]", 15 ) ,new Pair("zero 0 ? 1 : 2", 1 ) ,new Pair("zero 1 ? 1 : 2", 2 ) ,new Pair("zero [add 3 -3] ? 1 : 2", 1 ) ,new Pair("zero [add zero zero 0 ? 1 : 2 ? 3 : 4 -3] ? 1 : 2", 2 ) /* *** Z1 tests: *** */ /* Uncomment these tests, once `mod` is implemented: ,new Pair("[mod 3 4]", 3) ,new Pair("[mod [add 5 6] 3]", 2) ,new Pair("[mod 8.1 3]", 2.1) ,new Pair("[mod 8 3.1]", 1.8) ,new Pair("[mod -8.1 3]", 0.9) ,new Pair("[mod -8 3.1]", 1.3) ,new Pair("[mod 8.1 -3]", -0.9) ,new Pair("[mod 8 -3.1]", -1.3) ,new Pair("[mod -8.1 -3]", -2.1) ,new Pair("[mod -8 -3.1]", -1.8) ,new Pair("[mod 8 2]", 0) ,new Pair("[mod -8 2]", 0) ,new Pair("[mod 8 -2]", 0) ,new Pair("[mod -8 -2]", 0) ,new Pair("[mod 8 3]", 2) ,new Pair("[mod -8 3]", 1) ,new Pair("[mod 8 -3]", -1) ,new Pair("[mod -8 -3]", -2) YOU MUST CREATE SOME TESTS FOR pows (two can suffice), and IfGT's *** */ ); } /** For every element in allTests, * parse the string, and then call toString on the result, * checking that we get back exactly the input string * (up to whitespace). */ public void testParseToString() { dbg("testParseToString\n"); for ( Pair t : allTests ) { String expected = t.first(); String actual = Expr.parse( t.first() ).toString(); if (! UtilIan.equalsIgnoreWhitespace(expected, actual, Expr.PUNCTUATION)) { // This assert will fail; just present it to the user: assertEquals( expected, actual ); } else { logPassedTest(); } } dbg("\n"); } /** For every element in allTests, * parse the string and eval the result, * checking that we get back the second item in the pair. * If the second item is a Java Number, convert it to an Z0 Num, * and leave the double-comparison to Num.equals(Object). */ public void testEval() { dbg("testEval\n"); for ( Pair t : allTests ) { assertEquals( Expr.parse( t.first() ).eval(), Number.class.isInstance(t.second()) ? new Num( ((Number)t.second()).doubleValue() ) : t.second() ); logPassedTest(); } dbg("\n"); } private int testCaseNum = 0; public void logPassedTest() { ++testCaseNum; System.err.printf(".%s", (testCaseNum % 5 == 0) ? " " : "" ); } /** * Tears down the test fixture. * Called after every test case method. */ public void tearDown() { } /** Just like `System.err.printf` but for debugging-output; * comment out its body to disable. * (This same method might be repeated in multiple classes, so that * you turn messages on/off on a per-file basis.) * @see java.io.PrintStream#printf * @param fmt the format string * @param infos Any data needed by the `fmt` (one item per '%' in `fmt`) */ public static void dbg( String fmt, Object... infos ) { System.err.printf( fmt, infos ); } } /* In the Z0-java code, a couple of classes extend junit.framework.TestCase. In order to compile these, you'll need to have that class (and others) in your CLASSPATH. I know that BlueJ comes with the junit-classes automatically, and I imagine that Eclipse does, as well. If you're getting an error "package junit.framework does not exist", you'll want to download 'junit.jar' (I got it from junit.org), and extract it somewhere in your classpath (e.g., in the same dir as your project). To run the tests [again, BlueJ and Eclipse have buttons to do this] from the command line, you'd type: java org.junit.runner.JUnitCore TestExpr Some slight further info at http://www.radford.edu/itec380/2019spring-ibarland/Lectures/how-to-run-junit.html */