Fix testing type annotations.

pymatgen/util/testing.py

@@ -72,7 +72,7 @@ def get_mp_structure(cls, mpid: str) -> Structure:
         return m.get_structure_by_material_id(mpid)
 
     @staticmethod
-    def assertArrayAlmostEqual(actual, desired, decimal=7, err_msg="", verbose=True) -> bool:
+    def assertArrayAlmostEqual(actual, desired, decimal=7, err_msg="", verbose=True):
         """
         Tests if two arrays are almost equal to a tolerance. The CamelCase
         naming is so that it is consistent with standard unittest methods.
@@ -96,25 +96,24 @@ def assertDictsAlmostEqual(actual, desired, decimal=7, err_msg="", verbose=True)
                 if not pass_test:
                     return False
             elif isinstance(v, (list, tuple)):
-                pass_test = nptu.assert_almost_equal(v, v2, decimal, err_msg, verbose)
-                if not pass_test:
-                    return False
+                nptu.assert_almost_equal(v, v2, decimal, err_msg, verbose)
+                return True
             elif isinstance(v, (int, float)):
                 PymatgenTest().assertAlmostEqual(v, v2)  # pylint: disable=E1120
             else:
                 assert v == v2
         return True
 
     @staticmethod
-    def assertArrayEqual(actual, desired, err_msg="", verbose=True) -> bool:
+    def assertArrayEqual(actual, desired, err_msg="", verbose=True):
         """
         Tests if two arrays are equal. The CamelCase naming is so that it is
          consistent with standard unittest methods.
         """
         return nptu.assert_equal(actual, desired, err_msg=err_msg, verbose=verbose)
 
     @staticmethod
-    def assertStrContentEqual(actual, desired, err_msg="", verbose=True) -> bool:
+    def assertStrContentEqual(actual, desired, err_msg="", verbose=True):
         """
         Tests if two strings are equal, ignoring things like trailing spaces, etc.
         """