Hello,<div><br></div><div>I think nosetest does not report the individual times then.</div><div><br></div><div>As to your second problem. You might want to run nosetest with --verbose which defaults to a verbosity level of 2 that might give you more output or --verbosity=3 for even more verbose output.</div>
<div><br></div><div>But it seems like 2 errors occured which usually relate to exceptions or other things that went wrong (I'm no expert here)</div><div>And 10 failures which usually means that the tests failed e.g asserts fail.</div>
<div><br></div><div>-Tim</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Nov 5, 2012 at 1:55 PM, Prasanna Santhanam <span dir="ltr"><<a href="mailto:prasanna.santhanam@citrix.com" target="_blank">prasanna.santhanam@citrix.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wed, Oct 31, 2012 at 12:44:27PM +0530, Tim Aerdts wrote:<br>
> Hello Prasanna,<br>
><br>
> For me it seems like this is enabled by default.<br>
><br>
> <testsuite name="nosetests" tests="3" errors="0" failures="0" skip="0"><br>
> <testcase classname="test_someclass" name="test_some_method" time="2.042" /><br>
> <testcase classname="test_someclass" name="test_some_other" time="0.058" /><br>
> <testcase classname="test_someclass" name="test_some_other" time="0.022" /><br>
> </testsuite><br>
><br>
> I run my nosetests with the following parameters.<br>
><br>
> nosetests --with-xunit --verbose --with-coverage --cover-xml --cover-package=mypackage<br>
><br>
> Hope this helps your case.<br>
><br>
> -Tim<br>
<br>
</div>Hello Tim - Thanks for your response. I do have the times for individual<br>
tests in my nosetests.xml but for some reason it won't show them in<br>
stdout. Guess this is a plugin setting (in xunit) For eg:<br>
<br>
With xUnit plugin I see:<br>
$ nosetests -v --with-marvin --marvin-config=../cloud-autodeploy/$hypervisor.cfg --load --with-xunit integration/smoke/test_service_offerings.py<br>
Test to create service offering ... ok<br>
Test to update existing service offering ... ok<br>
Test to delete service offering ... ok<br>
<br>
----------------------------------------------------------------------<br>
XML: nosetests.xml<br>
----------------------------------------------------------------------<br>
Ran 3 tests in 0.143s<br>
<br>
OK<br>
<br>
With unittest-xml-reporting I see:<br>
$ python -m marvin.deployAndRun --config=$hypervisor.cfg --load --xml integration/smoke/test_service_offerings.py<br>
<br>
test_01_create_service_offering (test_service_offerings.TestCreateServiceOffering)<br>
Test to create service offering ... OK (0.057s)<br>
test_02_edit_service_offering (test_service_offerings.TestServiceOfferings)<br>
Test to update existing service offering ... OK (0.036s)<br>
test_03_delete_service_offering (test_service_offerings.TestServiceOfferings)<br>
Test to delete service offering ... OK (0.035s)<br>
<br>
<br>
Additionally, I wanted to understand what nose is using to determine the<br>
overall result of a run. In the above run you see 'OK' printed at the end. In<br>
the actual environment where I run many more tests I see<br>
<br>
----------------------------------------------------------------------<br>
XML: nosetests.xml<br>
----------------------------------------------------------------------<br>
Ran 73 tests in 11938.352s<br>
<br>
FAILED (SKIP=3, errors=2, failures=10)<br>
<br>
Many tests have passed, but why has nose determined FAILED? How can I fix this?<br>
<br>
<br>
Thanks,<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Prasanna.,<br>
</font></span><div class="im HOEnZb"><br>
> On Wed, Oct 31, 2012 at 7:27 AM, Prasanna Santhanam <<a href="mailto:prasanna.santhanam@citrix.com">prasanna.santhanam@citrix.com</a><mailto:<a href="mailto:prasanna.santhanam@citrix.com">prasanna.santhanam@citrix.com</a>>> wrote:<br>
> Hi All,<br>
><br>
> Is it possible to retrieve the time for each test fixture when using<br>
> the nosetests xunit plugin? By default I didn't see any options on the<br>
> cmd line for doing this.<br>
><br>
> I've used unittest-xml-reporting with some success and it reports the<br>
> fixture run times which is quite useful for optimizing and speeding up<br>
> tests.<br>
><br>
<br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
testing-in-python mailing list<br>
<a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Kind regards,<br>Tim Aerdts<br><a href="http://www.tuimz.nl">http://www.tuimz.nl</a><br>
</div>