How to best structure tests for bigger projects
My question isn't really covered in the video as the scope of the video was smaller. But I'm working on a project alongside doing these videos and I was wondering how you would go about placing your test folders. Would you want a /tests alongside your project folder (for example: projects/microblog/tests/) for all project wide tests and then individual /tests folders within the individual app folders to test their functionality?
Answers
Implementation answers like this are hard because, often, it depends on the rest of the project structure.
Your proposed solution is fine and would probably work well if the rest of the project follows a similar structure (for example, with template directories in each application).
I know many authors, especially of reusable libraries, package the tests in a top-level directory (alongside manage.py) and then have a sub-directory for each application/logical separation.
kennethlove (Staff)
on