No need to shout

[tooxie]

% grep -nIHR "!" . ./basic_doctests.rst:10:Django's testing framework, so that we don't have to worry about them! I will ./index.rst:5:Welcome to Django Testing Docs's documentation! ./index.rst:10:If you want to help contribute, please fork the docs and help out! Hopefully this will make it's way back into the Django documentation at some point. ./basic_unittests.rst:53:up in your output! You need to go into your __init__.py in your tests ./basic_unittests.rst:87:Awesome! ./basic_unittests.rst:131:classes and files should start with test! If not, they will not be run! If ./basic_unittests.rst:133:your problem. Also note that they cannot be named the same thing! These will ./fixtures.rst:53:Testing your fixtures (how meta of us!) ./fixtures.rst:65:fixture back out. Pretty neat! Note, your normal database name will be ./fixtures.rst:158:all we need to worry about is testing our logic! This makes the test a lot ./views.rst:16:source Django apps, and write some tests for it! Everyone loves getting ./views.rst:41:well! ./views.rst:87:to coding apply to testing too! Then the tests go on to create a Category, ./views.rst:99:tests is better than 90% of other open source projects! I'm sure if we asked ./views.rst:222:method breaks down, because you don't know if the output is correct! ./views.rst:329:Wow! That was a long post. I'm glad I decided to split the testing up into ./views.rst:330:separate posts! I hope this has been enlightening for everyone, and I'm sure

Aren't those too many exclamation marks? =)