On 28 February 2015 at 10:07, Pranjal Yadav wrote:
> Abhilash,
>
> Thanks! it worked as you said. But renaming clean method is not
> conventional. I changed the names and it looks like 'clean_password_repeat'
> is good and that is the last input for that test as well, so I don't
> understand why b
Abhilash,
Thanks! it worked as you said. But renaming clean method is not
conventional. I changed the names and it looks like 'clean_password_repeat'
is good and that is the last input for that test as well, so I don't
understand why but that works.
The 'except' part for 'clean_email' is not func
On 27 February 2015 at 20:39, Pranjal Yadav wrote:
> Hi Abhilash,
>
> Thanks for your help. I read that we need to define methods as
> clean_ however I missed
> I was cleaning multiple fields. For the listname method it works the way you
> told me but I tried something
> similar ( http://pastebin.
Abhilash,
renaming 'clean_password' to 'clean' did help in running all the tests
successfully but looking at the
coverage stats I realized the 'invalid_email' test is still not functional
since those lines are shown as 'missing'
in stats, So it was just a work around and it didn't actually help.
Hi Abhilash,
Thanks for your help. I read that we need to define methods as
clean_ however I missed
I was cleaning multiple fields. For the listname method it works the way
you told me but I tried something
similar ( http://pastebin.com/p40A19hU ) and it didn't work. If you could
tell me why is th
Hi Pranjal,
I was able to run the tests in ListNewTest, and kind of debug the
other test too.
In ListNewTest you have two tests doing the same thing, probably you intended
at doing something else, but there is nothing in there right now.
there is a method of django forms called as `errors`. So y
