Changes between Initial Version and Version 5 of Ticket #12191
- Timestamp:
- Jun 12, 2011, 8:11:00 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12191
- Property Owner changed from to
- Property Status new → closed
- Property Triage Stage Unreviewed → Accepted
- Property Severity → Normal
- Property Type → Cleanup/optimization
- Property Easy pickings unset
- Property Resolution → duplicate
- Property UI/UX unset
-
Ticket #12191 – Description
initial v5 1 The simple django looks for tests in either models.py or tests.py. This is unfortunate for large applications since tests.py in each app becomes rather large and unwieldy. Apps with a large number of tests can break out their tests further by creating a method called suite() that returns a TestSuite. This works for test separation but because the runner still looks for test cases in models.py or tests.py it is no longer possible to run an individual TestCase or TestCase.test_method. 1 The simple django test runner looks for tests in either models.py or tests.py. This is unfortunate for large applications since tests.py in each app becomes rather large and unwieldy. Apps with a large number of tests can break out their tests further by creating a method called `suite()` that returns a `TestSuite`. This works for test separation but because the runner still looks for test cases in models.py or tests.py it is no longer possible to run an individual `TestCase` or `TestCase.test_method` . 2 2 3 Proposal: 3 4 In addition to supporting the ability to specify tests to run as: 4 o app 5 o app.TestCase 6 o app.TestCase.test_method 5 6 * `app` 7 * `app.TestCase` 8 * `app.TestCase.test_method` 7 9 8 10 also support: 9 o app.module.TestCase.test_method 10 o app.module.TestCase.* 11 12 * `app.module.TestCase.test_method` 13 * `app.module.TestCase.*` 11 14 12 15 I'm including a patch which adds this functionality.