From 034ee380d549cee507e80344e87bc016549750eb Mon Sep 17 00:00:00 2001
From: Kevin Van Brunt <kmvanbrunt@gmail.com>
Date: Tue, 23 Apr 2019 23:38:06 -0400
Subject: Added unit test for stdout capture in pyscript

---
 tests/pyscript/stdout_capture.py | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 tests/pyscript/stdout_capture.py

(limited to 'tests/pyscript')

diff --git a/tests/pyscript/stdout_capture.py b/tests/pyscript/stdout_capture.py
new file mode 100644
index 00000000..dfc39627
--- /dev/null
+++ b/tests/pyscript/stdout_capture.py
@@ -0,0 +1,20 @@
+# flake8: noqa F821
+# This script demonstrates when output of a command finalization hook is captured by a pyscript app() call
+import sys
+
+# The unit test framework passes in the string being printed by the command finalization hook
+hook_output = sys.argv[1]
+
+# hook_output will not be captured because there are no nested calls to onecmd_plus_hooks
+res = app('help')
+if hook_output not in res.stdout:
+    print("PASSED")
+else:
+    print("FAILED")
+
+# hook_output will be captured in the nested call to onecmd_plus_hooks that occurs in do_history()
+res = app('history -r -1')
+if hook_output in res.stdout:
+    print("PASSED")
+else:
+    print("FAILED")
-- 
cgit v1.2.1