' string, or perhaps the view is
> actually returning queryset results. Dig around a bit. Getting comfortable
> with tests and good at writing them will give you a deeper understanding of
> the framework than simply writing views, models and templates ever wil.
>
> JDB
>
>
&
l05/#testing-our-new-viewwhich
> demonstrates how to create test cases that inherit from TestCase that
> can be found and executed by the Django test runner which will also handle
> creating the test database for you.
>
> JDB
>
>
> On Thu, Feb 13, 2014 at 10:20 AM, Paul Se
error
> you're receiving and the command that causes it.
>
> JDB
>
>
> On Thu, Feb 13, 2014 at 3:19 AM, Paul Sermon
>
> > wrote:
>
>> This is the tutorial:
>> https://docs.djangoproject.com/en/1.6/intro/tutorial05/
>>
>> I've followed
other fixtures that your tests are referencing (likely in
> their setUp method)
>
> If none of the items above are correct, feel free to provide a link to the
> tutorial you're going through and I'll take a look.
>
> JDB
>
>
> On Wed, Feb 12, 2014 at 2:33 PM, Paul Sermon
So I'm working my way through the Django tutorials, and have got as far as
the view tests. It seems that when running the test client, rather than
returning data from an empty test database (is this what is meant to
happen?) it is returning polls from the existing database, which has the
polls
5 matches
Mail list logo
