Russell Keith-Magee wrote:
> On 9/5/06, JP <[EMAIL PROTECTED]> wrote:
> >
> >
> > Now that syncdb can be run non-interactively, I can switch the plugin
> > over to calling that instead. It will take some time, however, because
> > I need to figure out how to do that and use the new create/drop tes
On 9/5/06, JP <[EMAIL PROTECTED]> wrote:
Now that syncdb can be run non-interactively, I can switch the pluginover to calling that instead. It will take some time, however, becauseI need to figure out how to do that and use the new create/drop test db
functions from djagnoo.test.utils when they are
Ned Batchelder wrote:
> I've also tried Jason's nose-django plugin, and it uses
> management.install(app) to create the test database. This doesn't fire
> a signal I can hook, so I wasn't able to create my initial data.
Now that syncdb can be run non-interactively, I can switch the plugin
over
On 9/4/06, Ned Batchelder <[EMAIL PROTECTED]
> wrote:
I've been experimenting with the new test frameworks, and am veryexcited about their potential.I've hit a snag, and am wondering if it reveals a flaw in the currentmanagement.py, or if there is something I don't understand yet (most
likely the l
I've been experimenting with the new test frameworks, and am very
excited about their potential.
I've hit a snag, and am wondering if it reveals a flaw in the current
management.py, or if there is something I don't understand yet (most
likely the latter). Russ's test runner uses management.sy
