Issue 603: Making it easier to correctly run the test suite - Roundup issue tracker

Title	Making it easier to correctly run the test suite
Milestone	0.11.10	Priority	feature
Waiting On		Status	resolved
Superseder		Nosy List	aviendhasl, paulproteus
Assigned To	paulproteus	Keywords

Created on 2011-10-04.17:22:45 by paulproteus, last changed 2011-10-24.19:59:15 by paulproteus.

Files
File name	Uploaded	Type	Edit	Remove
patch	paulproteus, 2011-10-04.17:25:57	application/octet-stream

Messages
msg2598 (view)	Author: paulproteus	Date: 2011-10-24.19:59:15
I've pushed this and marked it resolved! I have updated https://openhatch.org/wiki/Automated_testing also.
msg2585 (view)	Author: paulproteus	Date: 2011-10-04.17:25:57
I'm attaching a patch here that implements the suggested behavior. I'd like someone's saying "Yes, this is a good idea" or "No, this is not"!
msg2584 (view)	Author: paulproteus	Date: 2011-10-04.17:22:45
As of this moment, if you run: ./bin/mysite test You get this useless stack trace that ends with: from djangox.test.depth import alltests ImportError: No module named djangox.test.depth This is because one of a packaging bug in one of the apps we depend on. Let's fix that: for the future, I propose that when you run: ./bin/mysite test custom OpenHatch code notices you're running the test runner without any arguments, and reconfigures things so that you test all the OpenHatch apps and nothing else. There are also scripts in bin/*_test that djangorecipe generates; they are hard to use properly. I think we should also remove this.

History
Date	User	Action	Args
2011-10-24 19:59:15	paulproteus	set	status: need-review -> resolved messages: + msg2598
2011-10-04 17:25:57	paulproteus	set	status: unread -> need-review nosy: + aviendhasl messages: + msg2585 files: + patch
2011-10-04 17:22:45	paulproteus	create