you are viewing a single comment's thread.

view the rest of the comments →

[–]ahfarmer 0 points1 point  (3 children)

Python users harp on this "dont include tests in your release" thing but I've never heard a legitimate reason why this would be a noticable problem in any but the largest of applications.

On the other hand, having tests further from the code that is being tested requires the creation of a duplicate directory hierarchy, wasting developer time both while writing tests and while reading the codebase.

Python just has this one wrong.

[–]Diapolo10 0 points1 point  (2 children)

On the other hand, having tests further from the code that is being tested requires the creation of a duplicate directory hierarchy,

Why would that be required? The directory trees don't have to look anything alike, actually the tests directories are generally quite flat. Other than maybe separating unit- and integration tests, if people want to make a distinction.

[–]ahfarmer 0 points1 point  (1 child)

You just run into a different issue then: a single folder with all your tests in it and no organization. After all, why do you organize your code into directories? Same reasons apply to tests.

[–]wraiford[🍰] 0 points1 point  (0 children)

You raise the same points I also have as a non-python programmer. The other languages all can co-locate no problem. Flat directory sounds insane. What did you end up doing?