I didn't find that hypothesis was slowing me down during development. When a bug combination is found, hypothesis checks this combination early. It means that until you fix the bug running hypothesis is almost exactly as running a special hand-written test for just this sequence of commands. If the bug is fixed then you'll have to wait more to see if there is another one.
Almost all serious bugs were found in less than 10s, and each next run until bug was fixed took less than a second. If there is no more bugs you'll have to wait a lot for the test to finish, but for me it is a pleasure waiting and knowing that thousands of tests are passing. The biggest challenge was not the time hypothesis takes for testing. Many bugs were causing hard crashes so hypothesis could not finish its job. This is because we have to deal with Qt. In pure python development hard crashes never happen. Vitalije > Vitalije, would you say Hypothesis is most useful during development? We > don't want to take 300+ seconds for routine unit tests, but Hypothesis did > find several unexpected edge cases. Would it make sense to test for these > edge cases explicitly in unitTest.leo? > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/f2e35be9-f8a9-4398-b1c3-0cb1acfa040d%40googlegroups.com.
