[Jython-checkins] jython: Test we get a PlainConsole when we should.

jeff.allen jython-checkins at python.org
Sat Sep 7 19:12:50 CEST 2013


http://hg.python.org/jython/rev/0c4829021a3b
changeset:   7118:0c4829021a3b
parent:      7116:c71cbf98acf1
user:        Jeff Allen <ja.py at farowl.co.uk>
date:        Sat Sep 07 16:34:15 2013 +0100
summary:
  Test we get a PlainConsole when we should.

files:
  tests/java/org/python/util/jythonTestPlain.java |  64 ++++++++++
  1 files changed, 64 insertions(+), 0 deletions(-)


diff --git a/tests/java/org/python/util/jythonTestPlain.java b/tests/java/org/python/util/jythonTestPlain.java
new file mode 100644
--- /dev/null
+++ b/tests/java/org/python/util/jythonTestPlain.java
@@ -0,0 +1,64 @@
+package org.python.util;
+
+import static org.junit.Assert.*;
+
+import org.junit.Test;
+import org.python.core.Console;
+import org.python.core.PlainConsole;
+import org.python.core.Py;
+
+/**
+ * Tests of creating and getting the right interactive console.
+ * <p>
+ * System initialisation is a one-time thing normally, and the embedding of a console handler
+ * similarly, so it is difficult to test more than one console choice in a single executable. For
+ * this reason, there are two programs like this one: one that follows the native preference for a
+ * {@link JLineConsole} and this one that induces selection of a {@link PlainConsole}
+ * <p>
+ * <p>
+ * Automated testing of the console seems impossible since, in a scripted context (e.g. as a
+ * subprocess or under Ant) Jython is no longer interactive. To run it at the prompt, suggested
+ * idiom is (all one line):
+ *
+ * <pre>
+ * java -cp build/exposed;build/classes;extlibs/* -Dpython.home=dist
+ *              org.junit.runner.JUnitCore org.python.util.jythonTestPlain
+ * </pre>
+ */
+public class jythonTestPlain {
+
+    private static final String PYTHON_CONSOLE = "python.console";
+    private static String[] commands = {"-c", "import sys; print type(sys._jy_console)"};
+
+    /**
+     * Test that specifying an invalid console class falls back to a plain console. No, really,
+     * "org.python.util.InteractiveConsole" is not a {@link Console}! A warning to that effect will
+     * be issued when the test runs.
+     */
+    @Test
+    public void testFallbackConsole() {
+        System.out.println("testFallbackConsole");
+        System.getProperties().setProperty(PYTHON_CONSOLE, "org.python.util.InteractiveConsole");
+        jython.run(commands);
+        Console console = Py.getConsole();
+        assertEquals(PlainConsole.class, console.getClass());
+    }
+
+    /**
+     * Show that a {@link PlainConsole} may be replaced with a {@link JLineConsole}.
+     */
+    @Test
+    public void testChangeConsole() throws Exception {
+        System.out.println("testChangeConsole");
+        // In the case where this test is run in isolation, cause initialisation with PlainConsole
+        System.getProperties().setProperty(PYTHON_CONSOLE, "org.python.core.PlainConsole");
+        PythonInterpreter interp = new PythonInterpreter();
+        // Now replace it
+        Py.installConsole(new JLineConsole(null));
+        jython.run(commands);
+        Console console = Py.getConsole();
+        assertEquals(JLineConsole.class, console.getClass());
+        interp.cleanup();
+    }
+
+}

-- 
Repository URL: http://hg.python.org/jython


More information about the Jython-checkins mailing list