5 Commits (main)

Author SHA1 Message Date
Jeremy L Thompson a8f010243f
test - faster test suite by only initalizing once (#11) 2 years ago
Krzysztof G 95d5584ef1
fix: use correct method for list comparing (#4)
`assertAlmostEqual` is able to determine if lists are equal, but it cannot
determine if corresponding elements are almost equal. `assertCountEqual`
checks if lists have the same elements, regardless of the order.
2 years ago
PBM 1a010b2c49
fix: typos in README file and tests (#6)
* test: fix typo in test assertion error message

* docs: fix typo in README file
3 years ago
ngschaider c887194ed6
Unit tests raising Error. (#2)
* fixed assertAlmostEqual calls in tests

As you can see in the docs the signature of assertAlmostEqual is `assertAlmostEqual(first, second, places=7, msg=None, delta=None)`
Since the message is originally provided using a positional argument and only three arguments where given, the message effectively took the place of the `places` argument.

The default of places=7 is fine, we just have to use a keyword argument instead and this will resolve the resulting `TypeError`s when testing

* change assertAlmostEqual to assertEqual for string

assertAlmostEqual only makes sense when asserting ints/floats

* no need for keyword argument

Signature of method is `assertEqual(first, second, msg=None)`
Using a keyword argument is not required here.

Co-authored-by: ngschaider <gschaiderniklas@gmail.com>
3 years ago
moT01 ecb71658a1 init 4 years ago