{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.

If a function has a decoration nose will not pick it up for testing, it is of type 'function proxy' instead of 'function'.

This was tested on Debian testing with version 0.9.0-1

Test case:

def my_decor(func):
        return lambda: func()

def test_decor():
        assert False

@my_decor
def test_decor1():
        assert False

In the above test case we have two functions, one decorated and one not. Running it through nosetests shows only one detected function which fails while we expect two functions failing.

Running it in verbose mode will show that test_decor1 is not picked up for testing.

In nose main page, http://somethingaboutorange.com/mrl/projects/nose/, the section titled **Writing tests** says:

[quote]

Like py.test, functional tests will be run in the order in which they appear in the module file. TestCase derived tests and other test classes are run in alphabetical order.

[endquote]

nose 0.9.1 does not seem to do this at all. It seems that it performs the tests in the following order:

- run test functions that are defined with the raises decorator - runs the other test functions in alphabetical order of the test function names

py.test does run the test functions in order of appearance in the module and I'd like to be able to depend on that when using nose.

@raises is useful for some users, but others want to be able to stack up several raises tests inside of one test case, so it would be helpful to have an assert_raises that they can call directly.

Create a setuptools command that exposes the full functionality of nose and all plugins.

Hi,

I tried to write the following code:

@raises(NotEnoughBytes?) @with_setup(setup1) def test32():

...

This failed in a strange way. It seems nose either called the wrong setup function (I have different setup functions for different tests), or didn't call one at all (I didn't investigate very far). The fix came by inverting the decorator order:

@with_setup(setup1) @raises(NotEnoughBytes?) def test32():

...

If you define both the environmental variable and give the command-line variable, you get:

Traceback (most recent call last):
  File "/usr/local/bin/nosetests", line 7, in ?
    sys.exit(
  File "/usr/local/lib/python2.4/site-packages/nose-0.9.0-py2.4.egg/nose/core.py", line 438, in main
    return sys.exit(not run(*arg, **kw))
  File "/usr/local/lib/python2.4/site-packages/nose-0.9.0-py2.4.egg/nose/core.py", line 446, in run
    result = TestProgram(*arg, **kw).success
  File "/usr/local/lib/python2.4/site-packages/nose-0.9.0-py2.4.egg/nose/core.py", line 199, in __init__
    self.parseArgs(argv, env)
  File "/usr/local/lib/python2.4/site-packages/nose-0.9.0-py2.4.egg/nose/core.py", line 206, in parseArgs
    self.conf = configure(argv, env)
  File "/usr/local/lib/python2.4/site-packages/nose-0.9.0-py2.4.egg/nose/core.py", line 322, in configure
    options, args = parser.parse_args(argv)
  File "/usr/lib/python2.4/optparse.py", line 1278, in parse_args
    stop = self._process_args(largs, rargs, values)
  File "/usr/lib/python2.4/optparse.py", line 1318, in _process_args
    self._process_long_opt(rargs, values)
  File "/usr/lib/python2.4/optparse.py", line 1393, in _process_long_opt
    option.process(opt, value, values, self)
  File "/usr/lib/python2.4/optparse.py", line 710, in process
    return self.take_action(
  File "/usr/lib/python2.4/optparse.py", line 723, in take_action
    values.ensure_value(dest, []).append(value)
AttributeError: 'str' object has no attribute 'append'

Test packages are not documented very well. It seems all modules living in a test package are automatically considered test modules, irrespective whether their names match the testMatch regular expression or not. Is this by design? At least it should be documented.

No handlers could be found for logger "nose.plugins" is spammed to the console sometimes(?) on startup.

When a package is organized like:

 /lib
    module.py
 /tests
    test_module.py

nose loads test_module but even though it has already seen lib, it has failed to put it on sys.path, unless a plugin has asked to load all modules.

Possible solution: when addPaths is on, always add the surrounding directory of any .py file we see.

Multiple --include arguments should result in everything that matches any of them being included, instead of the current behavior, which is that only the last --include issued is used.

It looks like package.mod:Class is broken; it doesn't select all of the tests in the class -- it selects nothing.

Add a function to core that works like unittest.main, that is, collects test in main only. Usage would be like:

import nose

def test_a():
    pass

def test_b():
    pass

if __name__ == '__main__':
    nose.runtests()

using nose-0.9.0-py2.4.egg ... I'm getting some strange behavior trying to run `python setup.py test` It only finds my doctests. However, if I run `nosetests -v --with-doctest --doctest-tests` all tests are found. In setup.py I am setting the env vars which would be the equivalent of the above command line options, i.e.

os.environ['NOSE_WITH_DOCTEST'] = '1'
os.environ['NOSE_DOCTEST_TESTS'] = '1'

I will dig around the code a little more to see if I can figure out where it's going wrong, but wanted to submit this ticket in the meantime since you might know where to look in nose.collector

here is how to reproduce :

svn co --revision 197 http://svn.testtools.python-hosting.com/trunk testtools
cd testtools
python setup.py test

and this is what I was expecting :

nosetests -v --with-doctest --doctest-tests

am I missing anything?

The missing file warning repeats once for every test file compared against a requested missing file. It would be better to output only once per run per missing file.

Add unittests for weirdo calls that might come up, such as calling want_function() with something that doesn't have a __name__.

the command line option '--exe' is documented as causing more files to be included. Therefore it should increase the number of tests run. In my tests adding this option actually decreases the number of tests run.

C:\data\code\aa\Newman\POS\gui>python "c:\Program Files\Python23\Scripts\nosetes
ts-script.py" -d --with-doctest --doctest-tests -v
doctest of DialogExceptHook.DialogExceptHook ... ok

----------------------------------------------------------------------
Ran 1 test in 0.359s

OK

C:\data\code\aa\Newman\POS\gui>python "c:\Program Files\Python23\Scripts\nosetes
ts-script.py" -d --with-doctest --doctest-tests -v --exe

----------------------------------------------------------------------
Ran 0 tests in 0.015s

OK

I think I've tracked this down to the following code starting on line 241 of source:branches/0.9-stable/nose/selector.py#40

if not self.conf.ignoreExe and os.access(file, os.X_OK):
    log.info('%s is executable; skipped', file)
    return False

that 'not' looks like it should not be there.

This exception is thrown when running:

nosetests --with-doctest .

And it's thrown by trying to iterate over the result of DocTest?.py::loadTestsFromPath(), which returns None.

My expectation (although I've only read the code diagonally), is for loadTestsFromModule() to find my doctests, and loadTestsFromPath() to be used for loading doctests from other places. I really haven't understood the purpose of loadTestsFromPath(), have I?

I'll attach a patch right away, but I'm afraid I'm only masking the error somehow; please do look it over to see if that is what's correct.

Missing unittests for many core functions:

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

my directory structure:

proj/module1/__init__.py(has setup/teardown)
            module1.py
proj/module2/__init__.py(has setup/teardown)
            module2.py

When I run below in proj dir:

nosetests module1 -vv I found although only module1.py is running but both module1 package setup/teardown and module2's has run. that means I have to run: nosetests module1 -e module2 to exclude module2.

is there a way to run module1 package's test only? I know I could run `nosetest -w module1`, but this way can't call package setup/teardown.

It would be convenient/efficient/and future-safe to access all of nose's internal test wrappers with a common interface. That is, convenient for the nose-watch plugin ;)

Here is an initial idea, open to suggestions. I should point out that these are the only things that nose-watch needs to access, so a complete interface might want more.

• wrapper.getTestObject()
  • the actual test (i.e. FunctionTestCase.testFunc or TestModule.module or unittest.TestCase._'_class_'_)
• wrapper.getTestFile()
  • this one has proven itself really tricky and maybe nose has a better way to do it since it is already looking for tests in the filesystem. Currently I am working around unloadable modules by overloading the load_source() method in ihooks.Hooks. There is also a big problem that I'm not sure is solvable in aliased modules (i.e. "from main import foo" when when foo.py exists in main/foo/foo.py, concealed by main/foo/init.py). I think inspect.getfile() is the one to blame for that, but I haven't looked into it too far other than knowing it's not working how I would like it.
• wrapper.getTestAddress()
  • get a string "address" of a test. That is, a name that could be put on the command line of a nosetests call to run this test again. I'm thinking that any unittest.TestCase method could only return the filename of its module?

We should talk before you start work on this ... or perhaps I will just add a patch or two to this ticket if I get around to it first. I'll wait until 0.9.1 is out the door.

nose's --with-doctest will fail with the following class doctest's:

class CatalogHeader:
    """Representation of a gettext catalog header"""
    def __init__(self, encoding='utf-8'):
        self.encoding = encoding
        self._comments = []
        self._headers = {
            ProjectIdVersion: (
                u'Project-Id-Version', u'PROJECT VERSION'
            ),
            ReportMsgidBugsTo: (
                u'Report-Msgid-Bugs-To', u'ADDRESS@EMAIL'
            ),
            POTCreationDate: (
                u'POT-Creation-Date', u'YEAR-MO-DA HO:MI+ZONE'
            ),
            PORevisionDate: (
                u'PO-Revision-Date', u'YEAR-MO-DA HO:MI+ZONE'
            ),
            LastTranslator: (
                u'Last-Translator', u'FULL NAME <EMAIL@ADDRESS>'
            ),
            LanguageTeam: (
                u'Language-Team', u'LANGUAGE <LL@li.org>'
            ),
            MIMEVersion: (
                u'MIME-Version', u'1.0'
            ),
            ContentType: (
                u'Content-Type', u'text/plain; charset=UTF-8'
            ),
            ContentTransferEncoding: (
                u'Content-Transfer-Encoding', u'8bit'
            ),
            PluralForms: (
                u'Plural-Forms', u'nplurals=INTEGER; plural=EXPRESSION;'
            )
        }
        self.fuzzy = False

    def __str__(self):
        output = self.generate()
        if not isinstance(output, str):
            output = output.encode(self.encoding)
        return output

    def __unicode__(self):
        output = self.generate()
        if not isinstance(output, unicode):
            output = unicode(output, self.encoding)
        return output

    def __repr__(self):
        return '<%s>' % self.__class__.__name__

    def generate(self):
        """Generates the catalog header output."""
        txt = u''.join([u'# %s\n' % x for x in self._comments]) + u'#\n'
        if self.fuzzy:
            txt += u'#, fuzzy\n'
        txt += u'msgid ""\nmsgstr""\n'
        for key, val in self._headers.values():
            txt += u'"%s: %s\\n"\n' % (key, val)
        return txt

    def comments(self):
        """Get the comments the header has

        >>> ch = CatalogHeader()
        >>> ch.add_comment('Translation Template for Project XY')
        >>> ch.add_comment('Copyright FooBar 2010')
        >>> ch.comments()
        [u'Translation Template for Project XY', u'Copyright FooBar 2010']
        """
        return self._comments

    def headers(self):
        """Returns the headers.

        >>> ch = CatalogHeader()
        >>> ch.headers()            #doctest: +SKIP
        [(u'Project-Id-Version', u'PROJECT VERSION'),
         (u'Report-Msgid-Bugs-To', u'ADDRESS@EMAIL'),
         (u'POT-Creation-Date', u'YEAR-MO-DA HO:MI+ZONE'),
         (u'PO-Revision-Date', u'YEAR-MO-DA HO:MI+ZONE'),
         (u'Last-Translator', u'FULL NAME <EMAIL@ADDRESS>'),
         (u'Language-Team', u'LANGUAGE <LL@li.org>'),
         (u'MIME-Version', u'1.0'),
         (u'Content-Type', u'text/plain; charset=UTF-8'),
         (u'Content-Transfer-Encoding', u'8bit'),
         (u'Plural-Forms', u'nplurals=INTEGER; plural=EXPRESSION;')]
        """
        return self._headers.values()

    def add_comment(self, comment):
        """Add comments to the catalog header.

        >>> ch = CatalogHeader()
        >>> ch.add_comment('Translation Template for Project XY')
        >>> ch.add_comment('Copyright FooBar 2010')
        >>> print ch
        # Translation Template for Project XY
        # Copyright FooBar 2010
        #
        msgid ""
        msgstr""
        "Project-Id-Version: PROJECT VERSION\n"
        "Report-Msgid-Bugs-To: ADDRESS@EMAIL\n"
        "POT-Creation-Date: YEAR-MO-DA HO:MI+ZONE\n"
        "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
        "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
        "Language-Team: LANGUAGE <LL@li.org>\n"
        "MIME-Version: 1.0\n"
        "Content-Type: text/plain; charset=UTF-8\n"
        "Content-Transfer-Encoding: 8bit\n"
        "Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n"
        <BLANKLINE>
        """

        if comment not in self._comments:
            self._comments.append(unicode(comment))

    def set_project_id_version(self, project, version):
        """Set the 'Project-Id-Version' header.

        >>> ch = CatalogHeader()
        >>> ch.set_project_id_version('Foo Project', 0.2)
        >>> print ch
        #
        msgid ""
        msgstr""
        "Project-Id-Version: Foo Project 0.2\n"
        "Report-Msgid-Bugs-To: ADDRESS@EMAIL\n"
        "POT-Creation-Date: YEAR-MO-DA HO:MI+ZONE\n"
        "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
        "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
        "Language-Team: LANGUAGE <LL@li.org>\n"
        "MIME-Version: 1.0\n"
        "Content-Type: text/plain; charset=UTF-8\n"
        "Content-Transfer-Encoding: 8bit\n"
        "Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n"
        <BLANKLINE>
        """
        self._headers[ProjectIdVersion] = (
            self._headers[ProjectIdVersion][0],
            u'%s %s' % (unicode(project), unicode(version))
        )

    def set_report_msgid_bugs_to(self, value):
        self._headers[ReportMsgidBugsTo] = (
            self._headers[ReportMsgidBugsTo][0],
            unicode(value)
        )

    def set_pot_creation_date(self, value):
        self._headers[POTCreationDate] = (
            self._headers[POTCreationDate][0],
            unicode(value)
        )

    def set_po_revision_date(self, value):
        self._headers[PORevisionDate] = (
            self._headers[PORevisionDate][0],
            unicode(value)
        )

    def set_last_translator(self, value):
        self._headers[LastTranslator] = (
            self._headers[LastTranslator][0],
            unicode(value)
        )

    def set_language_team(self, value):
        self._headers[LanguageTeam] = (
            self._headers[LanguageTeam][0],
            unicode(value)
        )

    def set_mime_version(self, value):
        self._headers[MIMEVersion] = (
            self._headers[MIMEVersion][0],
            unicode(value)
        )

    def set_content_type(self, ctype, charset):
        self._headers[ContentType] = (
            self._headers[ContentType][0],
            u'%s; charset=%s' % (unicode(ctype), unicode(charset))
        )

    def set_content_transfer_encoding(self, value):
        self._headers[ContentTransferEncoding] = (
            self._headers[ContentTransferEncoding][0],
            unicode(value)
        )

    def set_plural_forms(self, nplurals, expression):
        self._headers[PluralForms] = (
            self._headers[PluralForms][0],
            u'nplurals=%s; plural=%s;' % (unicode(nplurals), unicode(expression))
        )

    def set_custom_header(self, name, value):
        self._headers[len(self._headers)+1] = (unicode(name), unicode(value))

    def set_fuzzy(self):
        self.fuzzy = True

    def unset_fuzzy(self):
        self.fuzzy = False

nosetests --with-doctest catalog.CatalogHeader

----------------------------------------------------------------------
Ran 0 tests in 0.008s

OK

The problem seems to be on methods add_comment() and set_project_id_version().

In setup.cfg there's no way to define multiple packages to produce coverage output for since repeating options overrides the previous values:

[nosetests]
cover-package=foo
cover-package=bar

The second value of "bar" will override the first.

Since the option parsing for "--cover-package" uses action="append" the value is already a list, so when it's passed to tolist() it's not split, so using comma separated values like "cover-package=foo,bar" also does not work.

Mac OSX Python 2.4.4 Nose-0.10.0b1 Coverage-2.77

nosetests works just fine

nosetests --with-coverage breaks like this:

Traceback (most recent call last):

File "/usr/local//bin/nosetests", line 7, in ?

sys.exit(

File "/usr/local/lib/python2.4/site-packages/nose-0.10.0b1-py2.4.egg/nose/core.py", line 188, in init

argv=argv, testRunner=testRunner, testLoader=testLoader)

File "/usr/local/lib/python2.4/unittest.py", line 758, in init

self.parseArgs(argv)

File "/usr/local/lib/python2.4/site-packages/nose-0.10.0b1-py2.4.egg/nose/core.py", line 203, in parseArgs

self.config.configure(argv, doc=TestProgram?.doc)

File "/usr/local/lib/python2.4/site-packages/nose-0.10.0b1-py2.4.egg/nose/config.py", line 170, in configure

self.plugins.configure(options, self)

File "/usr/local/lib/python2.4/site-packages/nose-0.10.0b1-py2.4.egg/nose/plugins/manager.py", line 201, in configure

cfg(options, config)

File "/usr/local/lib/python2.4/site-packages/nose-0.10.0b1-py2.4.egg/nose/plugins/manager.py", line 79, in call

return self.call(*arg, **kw)

File "/usr/local/lib/python2.4/site-packages/nose-0.10.0b1-py2.4.egg/nose/plugins/manager.py", line 135, in simple

result = meth(*arg, **kw)

File "/usr/local/lib/python2.4/site-packages/nose-0.10.0b1-py2.4.egg/nose/plugins/cover.py", line 66, in configure

import coverage

File "/usr/local/bin/coverage.py", line 5, in ?

pkg_resources.run_script('coverage==2.77', 'coverage.py')

File "/usr/local/lib/python2.4/site-packages/setuptools-0.6c7-py2.4.egg/pkg_resources.py", line 448, in run_script

self.require(requires)[0].run_script(script_name, ns)

File "/usr/local/lib/python2.4/site-packages/setuptools-0.6c7-py2.4.egg/pkg_resources.py", line 1166, in run_script

execfile(script_filename, namespace, namespace)

File "/usr/local/lib/python2.4/site-packages/coverage-2.77-py2.4.egg/EGG-INFO/scripts/coverage.py", line 8, in ?

coverage.the_coverage.command_line(sys.argv[1:]) AttributeError?: 'module' object has no attribute 'the_coverage'

let me know if you need any more info.

chris chris@percious.com

If you don't yield a function with arguments, but rather just a function, nose will not work. Patch to fix this attached.

Startup time for layouts like:

- lib/ - test/

Or:

- package/ - test/

Is very bad, since nose examines everyting in package/ and lib/ before looking in test/. This should be fixable, since it's only looking in the libs first to be sure that their root dirs are in sys.path before the tests are loaded.

nose-django fails at nosedjango.py line 141, for any app which has no models.py (e.g. django/contrib/markup)

Since it's not required to have a models.py file in every app, should begin() protect itself, e.g. only run management.install where load_app(app) is not None ?

or you could say it's a fault in django. a blank models.py fixes it.

I could be missing something obvious, but this has me completely stumped. I figure you know more about the environment that nose imports code into so, I dunno, take a look and let me know what you think.

Try this:

svn co --revision=238 http://svn.testtools.python-hosting.com/trunk/ testtools_238
cd testtools_238
nosetests -v testtools/testself/test_fixtures/test_storable.py

all tests should pass. now, open up testtools/testself/test_fixtures/test_storable.py and edit a few things :

• change mknewfile2 on line 241 to mknewfile
• change mknewfile2 on line 249 to mknewfile

now run it again and you should get :

Traceback (most recent call last):
  File "/Users/kumar/tmp/tt_nose_flop/testtools/testtools/testself/test_fixtures/test_storable.py", line 246, in test_mknewfile
    class MyAutoCsv(CsvFixture):
  File "/Users/kumar/tmp/tt_nose_flop/testtools/testtools/testself/test_fixtures/test_storable.py", line 247, in MyAutoCsv
    class meta:
  File "/Users/kumar/tmp/tt_nose_flop/testtools/testtools/testself/test_fixtures/test_storable.py", line 249, in meta
    mknewfile = mknewfile
NameError: name 'mknewfile' is not defined

now ... to make sure we're all sane, shouldn't the exact same error happen when we simply compile the code?

python testtools/testself/test_fixtures/test_storable.py

Yet it does not. In addition, I have tried to reproduce a similar NameError? in the python shell without success. And I've also tried taking that test function out of the unittest.TestCase class so that it is a standalone def, it still failed. I guess it's some kind of referencing issue but I can't think of any reason why this could happen *only* in nose.

- kumar

I often like to put a few tests in my Python modules, and it would be nice to use 'nosetests' on them. However, nosetests fails to discover any tests because the modules aren't named test_*. Can we have a command-line option that looks for tests in the specified module regardless of its name? I tried making the module executable and using --exe but that didn't work.

I think that you should be able to activate other loggers for your application through --debug. Imagine I am unit testing a piece of code that uses the logger "application.component". Now, in the normal run of the application the handler for this is set up by some piece of code that is not being run during the unit test. However, the unit tests fail, and I want to quickly activate the logger so I can see what went wrong. I think I should be able to write "nosetests ---debug=application.component" and see the log messages.

I have attached a patch that fixes this.