I looked over the testing page and saw we're recommending nosetests
with self.assertEqual(). That seems a bit schizophrenic since
"nosetests -d" is supposed to unpack assert expressions for you, and
show you the actual values of variables. However, my experience with
"nosetests -d" shows it some
On Jan 7, 2008 10:24 PM, Mike Orr <[EMAIL PROTECTED]> wrote:
>
> I looked over the testing page and saw we're recommending nosetests
> with self.assertEqual(). That seems a bit schizophrenic since
> "nosetests -d" is supposed to unpack assert expressions for you, and
> show you the actual values
On Jan 8, 2008 12:17 AM, Lawrence Oluyede <[EMAIL PROTECTED]> wrote:
>
>
> On Jan 7, 2008 10:24 PM, Mike Orr <[EMAIL PROTECTED]> wrote:
> >
> > I looked over the testing page and saw we're recommending nosetests
> > with self.assertEqual(). That seems a bit schizophrenic since
> > "nosetests -d"
> How do you get it to show the variables' values then?
With -d when I need to.
nosetests -s -d
--
Lawrence, stacktrace.it - oluyede.org - neropercaso.it
"It is difficult to get a man to understand
something when his salary depends on not
understanding it" - Upton Sinclair
--~--~-~--~
On 1/8/08, Mike Orr <[EMAIL PROTECTED]> wrote:
>
> > Never used assertEqual with nose, HTH
Same here.
How do you get it to show the variables' values then?
from nose.tools import eq_
eq_("one", "two")
Max.
--~--~-~--~~~---~--~~
You received this message beca
