Changes between Version 94 and Version 95 of j2p

Timestamp:

07/01/24 10:06:06 (4 months ago)

Author:

wouter

Comment:

--

j2p

@@ -186 +186 @@
 }}}
 
-== Unit Tests, @Test
-In python, a class with tests must extend {{{unittest.TestCase}}}. This allows discovery by the py test tools. In Python the mechanism is slightly different, requiring the test class to extend TestCase. To support the translation mechanism and make our lives a bit easier, j2p requires all tests to be annotates with @RunWith. Use the following, depending on what kind of test you want to run:
-
-||= test type in java =||= use java annotation =||
-||normal @Test methods||@RunWith(JUnit4ClassRunner.class)||
-||parametric test||@RunWith(Parameterized.class)||
-
-
-
 
 === More notes:
@@ -295 +286 @@
 then l is of type List (the Interface) and l.get is a function in the interface which needs to be translated. Note that in general any type of List can end up in l at runtime, the compiler has to compile it such that the compiled code will work regardless (thus using only functions available in python's equivalent of the List class).
 
+
+
+=== Unit Tests, @Test
+The junit-t plugin helps translation of org.junit components. 
+In python, a class with tests must extend {{{unittest.TestCase}}}. This allows discovery by the py test tools. In Python the mechanism is slightly different, requiring the test class to extend TestCase. To support the translation mechanism and make our lives a bit easier, j2p requires all tests to be annotates with @RunWith. Use the following, depending on what kind of test you want to run:
+
+||= test type in java =||= use java annotation =||
+||normal @Test methods||@RunWith(JUnit4ClassRunner.class)||
+||parametric test||@RunWith(Parameterized.class)||
+
+
+
+
+
 == Resulting file