[Health-dev] [bug #61850] Issues with package testing

[Axel Braun]

Follow-up Comment #2, bug #61850 (project health):

Yes, testing can become quite tricky, as the setup is not 'simple', see below.
In any case it should be optional.

I think in the trytond-testsuite there is a workaround for the below issue:

 [    6s] ==================================== ERRORS
====================================
[    6s] ____________________ ERROR collecting tests/test_health.py
_____________________
[    6s] tests/test_health.py:2: in <module>
[    6s]     import trytond.tests.test_tryton
[    6s] <frozen importlib._bootstrap>:971: in _find_and_load
[    6s]     ???
[    6s] <frozen importlib._bootstrap>:955: in _find_and_load_unlocked
[    6s]     ???
[    6s] <frozen importlib._bootstrap>:656: in _load_unlocked
[    6s]     ???
[    6s] <frozen importlib._bootstrap>:626: in _load_backward_compatible
[    6s]     ???
[    6s] /usr/lib/python3.6/site-packages/_pytest/assertion/rewrite.py:293: in
load_module
[    6s]     six.exec_(co, mod.__dict__)
[    6s] /usr/lib/python3.6/site-packages/trytond/tests/test_tryton.py:44: in
<module>
[    6s]     DB_NAME = os.environ['DB_NAME']
[    6s] /usr/lib64/python3.6/os.py:669: in __getitem__
[    6s]     raise KeyError(key) from None
[    6s] E   KeyError: 'DB_NAME'


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61850>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/