Changes between Version 50 and Version 51 of pyrunner

Timestamp:

01/09/25 13:42:49 (3 months ago)

Author:

wouter

Comment:

--

pyrunner

@@ -116 +116 @@
 Theoretically, for debugging you would need to **install** pytest ({{{sudo apt install python3-pytest}}}) after which you can do {{{pytest-3 --trace path/to/YOURTESTCLASS.py}}}. Unfortunately there seems a bug in pytest-3 and it does not break at the first test. This makes this approach mostly useless.
 }}}
+
+
+
+== Error handling
+PyRunner uses the stdin and stderr channels to communicate with python.
+
+If an IOException occurs on these channels, this error is forwarded to you.
+
+If a python call writes something to stderr, this is always interpreted as an error message. A PythonError will be thrown containing this message.
+
+If you just used {{{call()}}}, then the text that came back through stdin is forwarded to you are a result.
+
+If you called {{{test()}}} however, then the stdout stream is used to report the test results. If you write anything to the stdout stream (eg with print()) then this will corrupt the stdout stream, resulting in a parsing error.