[SOLVED] plan to implement a nose plugin and look for advice

dy20082250 · 09-20-2017, 09:07 PM

now i am learning a python test framework ----nose

and i found that when something went wrong, such as "assert 8==9"
the output is ugly like below:

Code:

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/Users/wdy/Documents/noselearn/test.py", line 5, in test3
    assert a == 9
AssertionError:
    8 = 8

while what i really want to get is something like this:

Code:

in /Users/wdy/Documents/noselearn/test.py, [method]  test3 Failed
and the reason is that line 5,  assert 8==9

I googled and get some idea as following:
use nose's API and implement a plugin ,but i am a newbie to nose and its plugin, is there anyone who can give some detailed advice?

astrogeek · 09-21-2017, 03:40 PM

The best advice would be to review the documentation for nose and its API.

I am not familiar with nose myself, but a quick search turns up many references. This looks like a good nose introduction, and includes a separate section for asert_equals and plugins.

Please review these docs and see where additional online searches of related terms leads you, then post back here if you do not understand what you find.

Good luck!

dugan · 09-21-2017, 03:54 PM

Show us your noselearn/test.py file and the command you're using to run the tests.

One or both are wrong.

dy20082250 · 09-22-2017, 03:41 AM

Quote:

Originally Posted by dugan

Show us your noselearn/test.py file and the command you're using to run the tests.

One or both are wrong.

Sorry I don't think so.

the content of test.py is following:

def test():
assert 8==9

and the command that i use to run is:

nosetests --detailled-error test.py

there is nothing special ,the Traceback info that show on stdout is coming from python interpreter
what i want to do is filter the Traceback and only keep some information that are meaningful to the testcase itself.

dy20082250 · 09-22-2017, 03:45 AM

Quote:

Originally Posted by astrogeek

The best advice would be to review the documentation for nose and its API.

I am not familiar with nose myself, but a quick search turns up many references. This looks like a good nose introduction, and includes a separate section for asert_equals and plugins.

Please review these docs and see where additional online searches of related terms leads you, then post back here if you do not understand what you find.

Good luck!

Thanks for your reply

I am reading the nose API document and I think if there is some similar plugin would help me quickly to get to know how to start

all beginning are hard!

dugan · 09-22-2017, 12:05 PM

I stand corrected. Your test file and command are fine.