From 739de7b088614e811b8f68ab8357e088239aafa7 Mon Sep 17 00:00:00 2001
From: Eli Schwartz <eschwartz@archlinux.org>
Date: Tue, 19 Oct 2021 19:51:44 -0400
Subject: unittests: use better assert methods

assertTrue and assertFalse are recommended against, if you can get a
more specific assertion. And sometimes it is considerably shorter, for
example we have a custom assertPathExists which we can take advantage
of.
---
 unittests/windowstests.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'unittests/windowstests.py')

diff --git a/unittests/windowstests.py b/unittests/windowstests.py
index 1e5964c..bd75c74 100644
--- a/unittests/windowstests.py
+++ b/unittests/windowstests.py
@@ -318,7 +318,7 @@ class WindowsTests(BasePlatformTests):
 
         def sanitycheck_vscrt(vscrt):
             checks = self.get_meson_log_sanitychecks()
-            self.assertTrue(len(checks) > 0)
+            self.assertGreater(len(checks), 0)
             for check in checks:
                 self.assertIn(vscrt, check)
 
-- 
cgit v1.1