From 4b0c0810df8e0fae9529d879539b8926b5b278a3 Mon Sep 17 00:00:00 2001 From: Eli Schwartz Date: Wed, 16 Mar 2022 18:36:25 -0400 Subject: unittests: convert python tests to project tests Perhaps when this test case was originally created, project tests could not use a matrix of options? This is certainly possible today, so don't write special unittest handling for this instead. This adds proper visibility into what gets run and what doesn't. Now we know which python executables got tested and which got skipped. --- test cases/python/8 different python versions/blaster.py | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100755 test cases/python/8 different python versions/blaster.py (limited to 'test cases/python/8 different python versions/blaster.py') diff --git a/test cases/python/8 different python versions/blaster.py b/test cases/python/8 different python versions/blaster.py new file mode 100755 index 000000000..163b6d426 --- /dev/null +++ b/test cases/python/8 different python versions/blaster.py @@ -0,0 +1,14 @@ +#!/usr/bin/env python + +import sys +import tachyon + +result = tachyon.phaserize('shoot') + +if not isinstance(result, int): + print('Returned result not an integer.') + sys.exit(1) + +if result != 1: + print('Returned result {} is not 1.'.format(result)) + sys.exit(1) -- cgit v1.2.3