1. 23
  1.  

  2. 6

    We have an interview in an upcoming episode with Hypothesis author on the podcast I cohost: http://pythonpodcast.com/

    1. 1

      Might have some python work coming up, whats recommended testing wise? I’d like to try TDD, should I be using multiple libraries?

      1. 6

        py.test, steer clear of unittest or any port/fork of it.

        1. 3

          Links: py.test, unittest

          1. 1

            steer clear of unittest or any port/fork of it.

            Why?

            1. 5

              it forces you to use classes as if they were modules. After all it is a port of Java’s JUnit, and comes with the same symptoms.

            2. 1

              This looks a lot simpler and more pleasant than unittest, thanks!

              1. 1

                I won’t defend unittest, but I will say that unittest.mock can be used independently and is a pretty nice mocking library: https://docs.python.org/3/library/unittest.mock.html

              2. 2

                I blogged about pyrhon test runners http://www.holger-peters.de/why-i-use-pytest.html (doesnt include hypothesis though). But hypothesis can be a good complement.