The test directory https://github.com/ClickSend/clicksend-python/tree/master/test does contains a number of automatically generated tests (by clicksend-codegen it seems). However, none of the tests actually do anything. For example:
class TestAccount(unittest.TestCase):
"""Account unit test stubs"""
def setUp(self):
pass
def tearDown(self):
pass
def testAccount(self):
"""Test Account"""
# FIXME: construct object with mandatory attributes with example values
# model = clicksend_client.models.account.Account() # noqa: E501
passThe only part that might do something is commented out. Technically, it does pass, (litterally, in this case), so Travis CI probably thinks it's fine. Most of the tests follow a similar pattern - some of them perform a setup step or so, but they don't do anything else.
I'm guessing, then, that this library is entirely untested? If this is the case, I wouldn't consider using this in a production app.
The test directory https://github.com/ClickSend/clicksend-python/tree/master/test does contains a number of automatically generated tests (by clicksend-codegen it seems). However, none of the tests actually do anything. For example:
The only part that might do something is commented out. Technically, it does pass, (litterally, in this case), so Travis CI probably thinks it's fine. Most of the tests follow a similar pattern - some of them perform a setup step or so, but they don't do anything else.
I'm guessing, then, that this library is entirely untested? If this is the case, I wouldn't consider using this in a production app.