python-unittest

Could someone please help me with this error message: Could not find a version that satisfies the requirement unittest I installed the latest Python and PyCharm and try to install the package unittest but get the above error. So far my experience with Python is a bit like dll hell ... If you tried this: $ pip install unittest Collecting unittest Could not find a version that satisfies the requirement unittest (from versions: ) No matching distribution found for unittest It's normal to have an error because unittest is not a valid package on Pypi. The only distribuable is unittest2-0.0.0.tar.gz

I would like to iterate over a list of items, and run an assertion on each of them. One example might be checking whether each number in a list is odd. TestCase : class TestOdd(unittest.TestCase): def runTest(self): """Assert that the item is odd""" self.assertTrue( NUMBER %2==1, "Number should be odd") Test suite : if __name__ == '__main__': suite = unittest.TestSuite() suite.addTest(TestOdd()) # I would like to have: # suite.addTest(TestOdd(1)) # suite.addTest(TestOdd(2)) # suite.addTest(TestOdd(3)) # ... unittest.main() How can I instantiate a TestOdd object with an argument - for example,

After submitting queries to a service, I get a dictionary / a list back and I want to make sure it's not empty. I am on Python 2.7. I am surprised I don't see any assertEmpty method for the unittest.TestCase class instance. The existing alternatives such as: self.assertTrue(bool(d)) and self.assertNotEqual(d,{}) and self.assertGreater(len(d),0) just don't look right. Is this kind of method is missing in the Python unittest framework? If yes, what would be the most pythonic way to assert that an iterable is not empty? Empty lists/dicts evaluate to False, so self.assertTrue(d) gets the job done.

For instance, I want these to run in the order they appear in the file. import unittest class Test_MyTests(unittest.TestCase): def test_run_me_first(self): pass def test_2nd_run_me(self): pass def test_and_me_last(self): pass class Test_AnotherClass(unittest.TestCase): def test_first(self): pass def test_after_first(self): pass def test_de_last_ding(self): pass if __name__ == "__main__": unittest.main(verbosity=2) Running this gives test_after_first (__main__.Test_AnotherClass) ... ok test_de_last_ding (__main__.Test_AnotherClass) ... ok test_first (__main__.Test_AnotherClass) ... ok test_2nd

Wow. I found out tonight that Python unit tests written using the unittest module don't play well with coverage analysis under the trace module. Here's the simplest possible unit test, in foobar.py : import unittest class Tester(unittest.TestCase): def test_true(self): self.assertTrue(True) if __name__ == "__main__": unittest.main() If I run this with python foobar.py , I get this output: . ---------------------------------------------------------------------- Ran 1 test in 0.000s OK Great. Now I want to perform coverage testing as well, so I run it again with python -m trace --count -C .