{6} All Tickets By Milestone (Including closed) (121 matches)

I am trying to use nose with the NoseXML plugin. When I call:

nose.run(argv=['--with-nosexml','--xml-report-file=some_file']),

I get my NoseXML output in some_file. This is nice.

On the other hand, it would be nicer if I could specify a StringIO that the NoseXML could write to instead of a file in the filesystem.

I have managed to do this by poking around inside the nose.core.TestProgram? class and nose.core.configure function, but my solution is not really acceptable for long-term use. I manually insert a StringIO into the configuration information after argv is parsed and before it is passed to the plugins.

Please consider providing a different means for specifying configuration information to nose when it is run using nose.run(). I would be glad to help with this if it would be an acceptable change.

And if I've missed the proper way to do something like this, please let me know.

Thanks, Matthew Desmarais

Hi

First of all I'm new to nose and I like what I see, I always complained about JUnit/pyUnit because it's too much troubles ... nose takes that away from me.

but when I try to test for a method that should raises a certain type of exception I found out that the only way to do this is with TestCase, at least to catch a certain specific type of test.

So how abotu adding a reimplementation (basically transform the methods into functions of TestCase.* into module level nose functions?

So we can implement this

class TestMyApp(TestCase):
    def test_create(self):
        self.failUnlessRaises(NotImplementedError, source.create)

as

def test_create():
    nose.failUnlessRaises(NotImplementedError, source.create)

here is the original thread. http://tinyurl.com/mvssg

Missing unittests for many core functions:

• loader testsInModule
• loader FunctionTestCase?
• loader MethodTestCase?
• LazySuite?.run

When using nose.tools.raises, the test reports look like:

nose.tools.<testfunc>

Instead of:

<testmod>.<testfunc>

raises needs to set the name or module of the wrapper it returns properly.

• Is this desirable? (YES)
• Is it possible to do, dependably, cross-platform? (YES)

Plugin import errors need to be reduced to warnings, since the import happens before users have a chance to disable the plugin.

Example: If profile module is not installed, nosetests exits with exception without running any tests.

this might be better fixed in the loader since I think at least for the wantMethod bug, it should not get something that's not a method. But this patches was necessary to allow a large ETL suite to run that I'm trying to use attributes in. a patch against branches/0.9-stable is to follow

Update mkrelease to make svn/svk branch and tag instead of bzr.

• Update the CHANGELOG and NEWS files.
• Update module, package and class docstrings
• Update TestProgram? usage
• Update mkindex, make sure it is pulling all relevant info
• Update hacking, etc, on index to include new svn repos information
• Add to this ticket as I think of more doc updates that are needed

Since nose is likely to be run in unstable environments where users are setting their root or other loggers to debug to debug their own code, and those users are probably not interested in nose's debug info, nose should explicitly override the root logger settings in the 'nose' domain. Don't use basicConfig, but compose a handler and formatter and set the log level to whatever is appropriate for the selected verbosity level.

eval() can't take an instance in 2.3, so the attrib eval() option must be disabled in 2.3.

When given a bad file name, nosetests loads tests from all modules instead of issuing a warning.

Trying to run with profiler enabled results in errors from the hotshot stats loader:

Could not identify fileId 10
Could not identify fileId 10
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/hotshot/stats.py", line 12, in load
    return StatsLoader(filename).load()
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/hotshot/stats.py", line 29, in load
    for event in log:
  File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/hotshot/log.py", line 120, in next
    filename = self._filemap[fileno]
KeyError: 91

The test loader's loadTestsFromNames behavior isn't compatible with single-test-file unittest-style command lines, eg:

python unit_tests/test_loader.py TestNoseTestLoader.test_generate_func

It needs to be revised for compatibility with unittest.

The coverage plugin should have an option to allow the user to erase accumulated stats before a test run.

Create nose.tools module and move with_setup there. Also add:

• @raises
• @timed

And try to think of some more useful, general test-writing tools to add.

Need controls and options for those controls for the profiler plugin. Including:

• formatting options -- sort, restrict func names, % of list
• prof data filename option (file to store profile data in during run)
• print/no print report
• print to report stream
• output to file

The following case will currently result in wrong behavior:

class TestA:
    def test_a(self):
        pass

class TestB(TestA):
    def test_b(self):
        pass

TestB will collect and run both test_a and test_b; it should only run test_a

In addError and addFailure, pass captured output (if any) to plugin calls.

make it easier for watcher plugins to access test results... possibly call addError, etc, in plugins from TextTestResult?.

Much as I hate camelCase, unittest uses it and some overridden methods must use it, so for consistency, everythingShouldLookLikeThis.

In the documentation, it says you can use 'setUpModule' as the setup function for a module. In the code though, it actually uses 'setupModule' (note the different case on the 'u')

nosetests deals badly with a common package layout:

pack
  lib
    foo.py
  test
    test_foo.py

To be friendlier to that layout, selector should be updated to want directories that look like common source directories (lib and src at least).

The attrib plugin is currently broken because the option defaults are strings, but the option type is append.

Add command line option/env var to activate the pdb on error/fail feature.

This patch adds selecting test cases based on their attributes.

Examples of test function/method attribute usage with patched nose

Simple syntax (-a, --attr) examples:

• nosetests -a status=stable => only test cases with attribute "status" having value "stable"

• nosetests -a priority=2,status=stable => both attributes must match

• nosetests -a tags=http => attribute list "tags" must contain value "http" (see test_foobar() below for definition)

• nosetests -a slow => attribute "slow" must be defined and its value cannot equal to False (False, [], "", etc...)

• nosetests -a !slow => attribute "slow" must NOT be defined or its value must be equal to False

Eval expression syntax (-A, --eval-attr) examples:

• nosetests -A "not slow"
• nosetests -A "(priority > 5) and not slow"

This example and the accompanied patch is in public domain, free for any use.

In the unittests in selftest, each class or instance that can take a config argument should get a fresh _Config(), so that the configuration of the driving test runner doesn't leak into the test cases.

Include a plugin in core that resets the state of sys.modules between after each test module is run.

Generate HTML docs for built-in plugins and post them to the site and wiki.

Install a man page for nosetests on install. A man page contributed by Gustavo Noronha Silva is attached to this ticket.

These instructions are wrong:

Install nose using setuptools:

easy_install nose

Or, if you don't have setuptools installed, use the download link 
at right to download the source package, and install in the normal
fashion: Ungzip and untar the source package, cd to the new
directory, and:

python setup.py install

You cannot run python setup.py install without setup_tools upgraded to at least the version that nose is configured to work with, as per this error message:

$ sudo python setup.py install                                                ~/src/nose-0.9.1
The required version of setuptools (>=0.6c2) is not available, and
can't be installed while this script is running. Please install
 a more recent version first.

(Currently using setuptools 0.6c1 (/usr/lib/python2.4/site-packages/setuptools-0.6c1-py2.4.egg))
zsh: 32149 exit 2     sudo python setup.py install

I recommend ammending the instructions to say

python ez_setup.py
python setup.py install

and note that the installation will cause easy_install to be installed. Perhaps a link to ez_setup.py would be good too.