Great... I'll work on cleaning it up a bit (it's kind of fugly right
now) and circle back once it's ready...
Thanks!
Chris
On 8/28/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On 8/29/07, Chris H. <[EMAIL PROTECTED]> wrote:
> >
> > Sorry for spamming, wasn't sure if I should combine t
Russ,
I submitted it as a ticket here:
http://code.djangoproject.com/ticket/5296
Take a look at the patch I think I addressed the multiple content
checks (by leveraging the assertContains) and though I didn't put it
in the patch, I think it could easily do the same thing for templates
and check
Can't wait to see it!
On 7/24/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 7/24/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> > I've just uploaded a patch to #4460 which adds the ability to start
> > individual tests or test cases from a test suite.
>
> Woo!
>
> > Are there any
On 7/15/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> I'm always interested in improving the testing capabilities built into
> Django. Can you elaborate on the types of tests/assertions/helpers
> that you have built, and the situations in which they would be useful?
>
> Yours,
> Russ Mage
Slightly OT...
We've got similar assertion functions on a custom testhelper at work
and we haven't had any problem with the "sometimes you feel like a
list, sometimes you don't" nature of test responses and test contexts.
I was actually going to re-work our custom testhelper a bit (clean up
some
I'd also be interested in the memory usage of strings vs. importing
the functions directly.
At work, we tend to use the string method when it's an undecorated
view function, and the pythonic way when we're going to decorate them:
usually caching, but sometimes login_required, etc.
The mixing and
