Set up pytest
With this change, you can run py.test from the Chromite root, and it
will pass.
Lots of tests are explicitly marked as skipped via pytestmarks. We will
need to address these. Until then, py.test does not replace run_tests.
BUG=chromium:934414
TEST=Run both py.test and run_tests, both inside and outside the chroot.
Outside the chroot, try run_tests with and without pytest installed.
Outside the chroot, expect failures from lib/operation_unittest and
lib/cros_test_lib_unittest; this is consistent with ToT.
With py.test outside the chroot, need to add 'inside_only' to the
excluded markers in pytest.ini. Later, when py.test is run from a
script, or when the runtime env is standardized via venv, this will not
be necessary.
Change-Id: Iee21130b7afd519d264e813974834d301f05bb94
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/chromite/+/1995734
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Greg Edelston <gredelston@google.com>
Tested-by: Greg Edelston <gredelston@google.com>
diff --git a/scripts/cros_generate_sysroot_unittest.py b/scripts/cros_generate_sysroot_unittest.py
index 95a1b45..bdcdff4 100644
--- a/scripts/cros_generate_sysroot_unittest.py
+++ b/scripts/cros_generate_sysroot_unittest.py
@@ -58,6 +58,7 @@
def setUp(self):
self.cg_mock = self.StartPatcher(CrosGenMock())
+ @cros_test_lib.pytestmark_redirected_stdin_error
def testTarballGeneration(self):
"""End-to-end test of tarball generation."""
with mock.patch.object(cros_build_lib, 'IsInsideChroot'):