Re: Unable to get tests to work

Fri, 19 Aug 2016 09:37:58 -0700

Matt,

At a glance, the directory structure looks OK.  Seems odd though
that you have some *.pyc files with no corresponding *.py file.
For example, frontend/tests.pyc and nas/tests.pyc.  Could such
a file be tripping up the test runner?  That might explain why it
fails when no arguments -- searching for all tests and getting
confused -- but succeeds when told to run only backups.tests.

Same for all of the erp/*.pyc files.

Perhaps try deleting all *.pyc file in the entire tree and then run
the tests, letting them be recreated from the *.py files as needed.

Also, I see a backup/tests.py with no *.pyc file.  Is there a syntax
error in that file that makes it not compile?  Or is it just not
getting that far?

Also, what is in pytest.ini?  Is it perhaps directing the test runner
to look for tests that don't exist?

--Fred
Fred Stluka -- mailto:f...@bristle.com -- http://bristle.com/~fred/
Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
Open Source: Without walls and fences, we need no Windows or Gates.

On 8/18/16 3:49 PM, Matt wrote:
Sorry replied to the wrong thread: https://dpaste.de/OF8j

On Wednesday, August 17, 2016 at 11:16:27 PM UTC-6, Gergely Polonkai wrote:

Hello,

this “refreshes.backups.tests” thing bothers me a lot. Could you show us your directory structure, please?

Best,
Gergely


On Wed, Aug 17, 2016, 23:03 Matt <kicke...@gmail.com> wrote:
Ok a step forward. When I spell out the tests it works: 


But when I run test without arguments, it fails out:


There is more than the backups app here, but I plan to replicate out the fix when I get it.

On Wednesday, August 17, 2016 at 2:34:45 PM UTC-6, Fred Stluka wrote:
Matt,

Oops!  Right.  I just noticed that in the dpaste.

My next guess is you may need to change the name "good_index_text"
to something that starts with "test_" to get it to be recognized as a
test.

Or maybe something to do with "refreshes"?  The test trace shows
it trying to run testcase "refreshes.backups.tests", but in the manual
import you did from the python shell, you only import "backups.tests"

--Fred
Fred Stluka -- mailt...@bristle.com -- http://bristle.com/~fred/
Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
Open Source: Without walls and fences, we need no Windows or Gates.

On 8/17/16 4:27 PM, Matt wrote:
Sorry for the typo, but I have already do that way. I have the output in the the first link.

On Wednesday, August 17, 2016 at 2:24:19 PM UTC-6, Fred Stluka wrote:
Matt,

Drop the "s" from "tests":

./manage.py test backups

--Fred
Fred Stluka -- mailt...@bristle.com -- http://bristle.com/~fred/
Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
Open Source: Without walls and fences, we need no Windows or Gates.

On 8/17/16 4:17 PM, Matt wrote:
When I'm trying to get tests to work it simply states that its unable to import <app>.tests. I'm not sure what I'm missing here. Here is some output please let me know if you need more:

./manage.py tests backups

The test file:
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/89d6fac7-0848-4e35-8b4a-62d24178c3aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/404f7e22-6f34-4c0d-bfdd-f277f6fb7543%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/bd711254-a2f0-4b6d-bd49-b7cb3cc82006%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/6a7f4bf4-be4b-77cb-f2ce-58896e2ffa8a%40bristle.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to