Changes between Version 23 and Version 24 of GSoC/2014/TestingFrameworkForGRASS

Timestamp:

May 30, 2014, 11:12:55 AM (10 years ago)

Author:

wenzeslaus

Comment:

suggestion to deal with dependecies of test code

GSoC/2014/TestingFrameworkForGRASS

@@ -239 +239 @@
 ==== Dependencies of testing code ====
 
-The testing code could use some third party tools to compare results of GRASS to results of these tools. This of course might be very different set of dependencies than the GRASS itself code has. For example, we can compare result of some computation to result of a function available in [http://www.scipy.org/ SciPy]. These test will probably be not allowed.
+The testing code could use some third party tools to compare results of GRASS to results of these tools. This of course might be very different set of dependencies than the GRASS itself code has. For example, we can compare result of some computation to result of a function available in [http://www.scipy.org/ SciPy]. These test will probably be not allowed. If the tests would be allowed the most simple thing is probably check the dependencies in `setUp` or `setUpClass` methods. In case of import, it would need to be done once again in the actual test method (or we can assign the necessary imported classes to attributes).
+
+{{{
+#!python
+# loading the dependency in setUp method and using it later
+def setUp(self):
+    # will raise import error which will cause error in test (as opposed to test failure)
+    from scipy import something
+    # save this for later user in test method(s)
+    self.something = something
+
+def test_some_test(self):
+    a = ...
+    b = self.something(params, ...)
+    self.assertEqual(a, b, "The a result differs from the result of the function from scipy")
+}}}
 == Reports from testing ==