Menu

#32 Test cases are not passing in current version (1.11.223)

Next Minor Release
closed
nobody
None
1
2019-07-27
2015-07-08
Anonymous
No

tin@wazowski:~/Yapsy-1.11.223$ python runtests.py
..................................................................F...........................
======================================================================
FAIL: test_default_plugins_place_is_parent_dir (test.test_PluginFileLocator.PluginFileLocatorTest)
Test a non-trivial default behaviour introduced some time ago :S


Traceback (most recent call last):
File "/home/tin/Yapsy-1.11.223/test/test_PluginFileLocator.py", line 195, in test_default_plugins_place_is_parent_dir
self.assertTrue("package/yapsy" in pl.plugins_places[0])
AssertionError: False is not true


Ran 94 tests in 0.109s

FAILED (failures=1)

Discussion

  • Thibauld Nion

    Thibauld Nion - 2015-07-08

    The tests are passing quite well on automatic testing: https://travis-ci.org/tibonihoo/yapsy

    Here it's failing because you move the sources and tests outside the package folder.

    I don't mean it's your fault, just that the "external" settings have changed and there is no real bug in yapsy related to that.

    The best I can do is to see how to make this test more flexible, but this is low priority.

     

    Last edit: Thibauld Nion 2015-07-08
  • Igor Gnatenko

    Igor Gnatenko - 2016-05-11

    Actually I just run python3 setup.py test which is proper way I think.

     
  • Thibauld Nion

    Thibauld Nion - 2016-05-11

    Sure, the test is just too strict for the way you unpacked yapsy: it expects the "yapsy" folder to be in the "package" folder, but in your case it's directly below the Yapsy-1.11.123.

     
  • Thibauld Nion

    Thibauld Nion - 2016-05-11
    • status: open --> accepted
     
  • Thibauld Nion

    Thibauld Nion - 2018-09-02
    • status: accepted --> pending
     
  • Thibauld Nion

    Thibauld Nion - 2019-07-27
    • status: pending --> closed
     
  • Thibauld Nion

    Thibauld Nion - 2019-07-27

    I haven't heard of the pb coming back since the fix mentionned above, so closing this ticket.

     

Anonymous
Anonymous

Add attachments
Cancel