So, I just started an interest on python tests and I would like to share what I learned so far.<\/p>\n
Let’s skip all that theory about how tests are important for the code, bla bla bla, if you want to learn test, probably you already have your own reason, so, let’s jump to the part you actually write code!<\/p>\n
Here a\u00a0 simple code that calculates fibonacci. Let’s save it in the file fibonacci.py<\/p>\n
\ndef fibonacci(number):\n if number < 2:\n return number\n return fibonacci(number - 1) + fibonacci(number - 2)\n\n<\/pre>\nSo, as you can see, it’s a very simple code that calculates the fibonacci number, so, how can we ensure that this is working? Well, the easiest way is just invoke the code with different values, and check if the result will be the expected. So, in other words, you’re doing exactly what doctest intent to do!
\nso, probably you would write a python file, let’s say, test_fibonacci.py with the following content:<\/p>\n\nfrom fibonacci import fibonacci\n\ndef test_fibonacci():\n expected_result = [0, 1, 1, 2, 3, 5]\n for x in range(0, 5):\n result = fibonacci(x)\n if result != expected_result[x]:\n print "Failing on calculate fibonacci %s" % x\n\nif __name__ == '__main__':\n print "Testing fibonacci"\n test_fibonacci()\n\n<\/pre>\nWell, it might work, until you want to calculate fibonacci(200), then you gonna need to add a new list, alter the test code, etc.
\nWhat if we now only accept positive numbers and negative numberes throws an exception? Try\/catch block? Well, soon you’re writing more code, and adding more complexity than you were expecting. Maybe you gonna need to test your test code itself to ensure that it’s working fine (are you feeling the inception here?)<\/p>\nDoctest<\/h5>\n
So, doctest can help you with some of these problems! Let’s see, first of all, you’re gonna need to create a simple txt file and add the following content:<\/p>\n
\n>>> from fibonacci import fibonacci\n\n>>> fibonacci(0)\n0\n\n>>> fibonacci(1)\n1\n\n>>> fibonacci(2)\n1\n\n>>> fibonacci(3)\n2\n\n>>> fibonacci(4)\n3\n\n>>> fibonacci(7)\n12\n<\/pre>\nSo, basically, doctest expect every line starting with “>>>” to be a python code (we are importing fibonacci function in the line number 1 for example. And any other line as the result, looking just like the python shell.<\/p>\n
Assuming that both fibonacci.py and fibonacci.txt are in the same directory, you can run the doctest with the command:<\/p>\n
\n$ python -m doctest fibonacci.txt\n**********************************************************************\nFile "fibonacci.txt", line 18, in fibonacci.txt\nFailed example:\n fibonacci(7)\nExpected:\n 12\nGot:\n 13\n**********************************************************************\n1 items had failures:\n 1 of 7 in fibonacci.txt\n***Test Failed*** 1 failures.\n<\/pre>\nOops! Something went wrong! Don’t worry, that was expected. As you can see, the doctest shows a very good output when some error occurs, it shows you the line where the error happened, what was the expected result, and what was the result doctest gots. So, after fixing it, and runing again, we got no error<\/p>\n
\n>>> from fibonacci import fibonacci\n\n>>> fibonacci(0)\n0\n\n>>> fibonacci(1)\n1\n\n>>> fibonacci(2)\n1\n\n>>> fibonacci(3)\n2\n\n>>> fibonacci(4)\n3\n\n>>> fibonacci(7)\n13\n<\/pre>\n\n$ python -m doctest fibonacci.txt\n<\/pre>\nNow let’s go further, and say: Hey, I don’t want negative numbers to be allowed, I want it to throw an exception. So, in this case, we just need to add a new like in our fibonacci.txt testing the fibonacci(-1) and of course, checking if the result will be an exception.
\nIf we would do that in our test_fibonacci.py code, we should use a try\/catch block, call the fibonacci(-1) inside it, and of course, this woudln’t be in the initial loop, and if something goes wrong, you wouldn’t have the cool output from doctest.<\/p>\nSo, let’s change our fibonacci.py to not accept negative numbers:<\/p>\n
\ndef fibonacci(number):\n if number == 1 or number == 0:\n return number\n if number < 0:\n raise ValueError('Number is negative')\n return fibonacci(number - 1) + fibonacci(number - 2)\n\n<\/pre>\nEven if we run our doctest after this changes, we got no error, but we are not testing the negative number yet. so, let’s add a fibonacci(-1) in our fibonacci.txt test.<\/p>\n
Just a heads up, if we run fibonacci(-1) we will get a exception like this:<\/p>\n
\nTraceback (most recent call last):\n File "<stdin>", line 1, in <module>\n File "fibonacci.py", line 5, in fibonacci\n raise ValueError('Number is negative')\nValueError: Number is negative\n<\/pre>\nAnd you’re probably thinking that you can copy and paste this error on our fibonacci.txt and it will work, but\u00a0 what if the file can change? You can add more code on the file, and the line where the error is being raised (in this case, line 5) might change. Being so, doctest only cares about the first and last lines, so our code in fibonacci.txt file will look like this:<\/p>\n
\n>>> fibonacci(-1)\nTraceback (most recent call last):\nValueError: Number is negative\n<\/pre>\nAnd we are done! now we have a set of tests to our fibonacci code!<\/p>\n
But what if you don’t want to have a txt and still have your tests? You can write doctest directly in your code on the docstring:<\/p>\n
\ndef fibonacci(number):\n '''\n This is a fibonacci function.\n Example of usage:\n >>> fibonacci(0)\n 0\n >>> fibonacci(1)\n 1\n >>> fibonacci(2)\n 1\n >>> fibonacci(3)\n 2\n >>> fibonacci(4)\n 3\n >>> fibonacci(7)\n 13\n >>> fibonacci(-1)\n Traceback (most recent call last):\n ValueError: Number is negative\n '''\n if number == 1 or number == 0:\n return number\n if number < 0:\n raise ValueError('Number is negative')\n return fibonacci(number - 1) + fibonacci(number - 2)\n\n<\/pre>\nand you can run python -m doctest fibonacci.py.<\/p>\n
More<\/h5>\n
Doctest have more features, as you can see below:<\/p>\n
ELLIPISIS<\/h6>\n
According our fibonacci code, if you pass a negative number, it will raise a ValueError exception with the message ‘Number is negative’. There are some cases, that we don’t need to know which message is returning, we just want to know that an exception is being raised. Another example is when the output is the default __repr__ output, every time is a different memory address and you can’t control it. For this kind of situations, we can use the ELLIPISIS like in the example below.<\/p>\n
\n>>> fibonacci(-1) #doctest: +ELLIPSIS\nTraceback (most recent call last):\nValueError: ...\n\n<\/pre>\nThe line containing #doctest: + ELLIPSIS tells to doctest that the ‘…’ can match anything after ‘ValueError: ‘<\/p>\n
SKIP<\/h6>\n
As the name says, it skips a test. This can be usefull when you know that some test is failing due some know bug, but it’s not fixed yet.<\/p>\n
\n>>> fibonacci(-1) #doctest: +ELLIPSIS +SKIP\nTraceback (most recent call last):\nValueError: ...\n<\/pre>\nAs you can see, you can use the two options, ELLIPSIS and SKIP together.<\/p>\n
Conclusion<\/h5>\n
Tests can be fun and easy, and it helps to keep you code working properly in the whole cycle of development.
\nFor more information about doctest, visit doctest website<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"