When projects get large it's nearly impossible to check everything by hand and see if your recent changes haven't broken something else. Testing is a good way to ensure your feature isn't broken later on, but also helps you think about writing very well isolated code.
Other programmers love it when you have tests, because we have high confidence that your feature won't break on us when we go to work on it. It is also nice because it works as a living spec for how the code ought to work, and can give you insight into what was intended.
When projects get large it's nearly impossible to check everything by hand and see if your recent changes haven't broken something else. Testing is a good way to ensure your feature isn't broken later on, but also helps you think about writing very well isolated code.
Try adding a few tests based on the tutorial docs https://docs.djangoproject.com/en/1.10/topics/testing/overview/ https://docs.djangoproject.com/en/1.10/intro/tutorial05/#writing-our-first-test
Other programmers love it when you have tests, because we have high confidence that your feature won't break on us when we go to work on it. It is also nice because it works as a living spec for how the code ought to work, and can give you insight into what was intended.