Namespace testcase fails to pass
See original GitHub issueIn a fresh checkout of pydap
in a clean venv, the namespace
testcase does not pass:
======================================================================
FAIL: Test the namespace.
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/gvaillan/.virtualenvs/pydap/src/pydap/src/pydap/tests/test_pydap.py", line 20, in test_namespace
pydap.__doc__, "Declare the namespace ``pydap`` here.")
AssertionError: None != 'Declare the namespace ``pydap`` here.'
----------------------------------------------------------------------
Ran 311 tests in 0.582s
Indeed, if I manually run:
>>> import pydap
>>> print(pydap.__doc__)
None
I am wondering whether this test case is actually useful, beyond increasing the code coverage?
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
php - Why is my custom TestCase class not being found when ...
I have double checked the class name, the namespace and use statement (which should not be necessary, since both classes are in the...
Read more >Using namespace with Laravels TestCase (integrated testing)
I've tried updating my composer file to have a namespace as the regular App has, but then the TestCase class is not found....
Read more >setMockClassName will not work with namespaces · Issue #134
When building a mock object with a class name that is in a namespace a Parse error will occur. How to reproduce. Run...
Read more >Customization - Codeception Docs
In this chapter we will explain how you can extend and customize the file structure and test execution routines. Namespaces. To avoid naming...
Read more >Advice on how to pass long list of testcases in NUnit Console ...
Hi all,. I'm using NUnit Console and --test=<full_testcase_name> option to run our tests by sending all testcases explicitly via command line, e.g.:.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve tried a few things but can’t seem to make it work. Should we simply remove this line? It does not seem to be testing much after all…
@jameshiebert I can reproduce the problem when using
python3 -m venv
on Debian Stretch (Python 3.5.2). This issue is still alive I am afraid.