On Oct 6, 1:43 am, Simon Willison <[email protected]> wrote:
>
> Option 6 would be welcome if anyone has any ideas.
>
Do what Grok does:
$ grokproject newapp
$ cd newapp
$ ./bin/test
Running tests at level 1
Total: 0 tests, 0 failures, 0 errors in 0.000 seconds.
That is, if it's a fresh project, and no code has been written, why
are there already tests?
Another way to make testing more popular in Django-based apps would be
to expand the intro tutorial to briefly show how a test is created and
run - that would certainly raise the awareness of the testing
facilities available. Or additionally inject some boilerplate test
suites into a new project when one runs 'django-admin.py
startproject' (e.g. the Grok and BFG project creation tools create a
bare-bones tests.py file in the root of the project directory).
(Incidentally, 'django-admin.py startproject' is probably overdue for
an overhaul ... why is there no setup.py file? Why is library code
being intermingled with scripts - manage.py should not be alongside an
__init__.py!)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
