non-uniform behaviour between directly naming a test file or not

Issue #88 resolved
Ronny Pfannschmidt
created an issue

the test file:
{{{

!python

def test_a():
(
}}}

Comments (5)

  1. Ronny Pfannschmidt reporter
    13:14:40 | ~/test/wd
    $ cat <<EOF >test.py
    def test_pass():
      pass
    def test_fail():
     assert 0
    EOF
    
    13:14:48 | ~/test/wd
    $ py.test test.py 
    inserting into sys.path: /home/ronny/Projects/py
    ============================= test session starts ==============================
    python: platform linux2 -- Python 2.6.5 -- pytest-1.3.0
    test object 1: test.py
    
    ===============================  in 0.00 seconds ===============================
    13:15:01 | ~/test/wd
    
  2. Ronny Pfannschmidt reporter

    its actually related to a plugin being enabled

    $ py.test test_listing.py --collectonly
    inserting into sys.path: /home/ronny/Projects/py
    <PyCheckerCollector 'test_listing.py[code-check]'>
    
  3. Holger Krekel repo owner

    This issue is actually about the fact that 1.3.0 treats the initial argument specially - one bad effect is that custom collectors like the codecheckers collector and the internal module collector may not both be collected if the file is directly specified.

  4. Holger Krekel repo owner

    refactor all collection related logic - drop all pickling support (for now) - perform collection completely ahead of test running (no iterativity) - introduce new collection related hooks - shift all keyword-selection code to pytest_keyword plugin - simplify session object - besides: fix issue88

    96d023b72b75

  5. Log in to comment