Re: [Django] #10973: simpler doctesting

[Django]

#10973: simpler doctesting
-+-
 Reporter:  pcicman  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  Version:  1.0
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  doctest modules  | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Time has passed since this ticket was last discussed, and it no longer
 looks like a good idea. The trend is to remove custom support for
 doctests, not to extend it. See #18727 for more details.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10973: simpler doctesting

[Django]

#10973: simpler doctesting
-+-
   Reporter:  pcicman|Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  Testing framework
  Milestone: | Severity:  Normal
Version:  1.0| Keywords:  doctest modules
 Resolution: |Has patch:  1
   Triage Stage:  Design |  Needs tests:  1
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by SmileyChris):

 * type:   => New feature
 * severity:   => Normal


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #10973: simpler doctesting

[Django]

#10973: simpler doctesting
+---
  Reporter:  pcicman| Owner:  nobody 
Status:  new| Milestone: 
 Component:  Testing framework  |   Version:  1.0
Resolution: |  Keywords:  doctest modules
 Stage:  Unreviewed | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  1  
Needs_better_patch:  0  |  
+---
Changes (by Nate):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * needs_tests:  => 1
  * needs_docs:  => 0

Comment:

 For what it's worth, I agree with this suggestion. I had actually done
 something similar to automate the doctesting of my own modules. Pcicman, I
 took the liberty of making a patch out of your code. It could use some
 tests, though.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #10973: simpler doctesting

[Django]

#10973: simpler doctesting
---+
 Reporter:  pcicman|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Testing framework  | Version:  1.0   
 Keywords:  doctest modules|   Stage:  Unreviewed
Has_patch:  0  |  
---+
 First of all, i found doctests very useful in last time, i just think the
 way how django does executes can be little bit simplified.
 (I know i can write my own test runner, and define it in settings)

 By default django takes look only to models.py and tests.py, if they
 exists, but there may be other modules in application which should be
 tested, but there isn't any 'magic' way how to do it.

 The nice thing is - suite can be defined it tests.py, so its possible to
 add any other modules to suite, e.g:
 {{{
 suite = unittest.TestSuite()
 for mod in ['crawl.page.utils', __name__]:
 suite.addTest(doctest.DocTestSuite(mod))
 }}}
 So i'm able to make doctests on other modules also, it just requires few
 imports and few lines of code.
 I think i can be easier, the only one required thing will be to add some
 stuff to test.simple.build_suite.

 There can be by convenience check for existence of some variable, e.g.
 '''doctest_modules'''. If it exists, all the modules founded inside can be
 added to suite, so:

 == in tests.py ==
 {{{
 from some app import foo
 doctest_modules = ['someapp.utils', foo]
 }}}

 == then to build_suite function can be just added ==
 {{{
 if hasattr(test_module, 'doctest_modules'):
 for module in test_module.doctest_modules:
 suite.addTest(doctest.DocTestSuite(module,
   checker=doctestOutputChecker,
   runner=DocTestRunner))
 }}}
 And it will do all the magic.

 I just personally think this may be helpful, mostly for bigger
 applications.

 It can be also more generalized, maybe '''test_modules''' instead of
 '''doctest_modules''', then just import them in the test framework, check
 for suite, or doctests, and so on... but i dont think this it is a good
 idea - to create unitest suites in every module, they should just stay in
 tests.py.

 On other side, i think i will be just nice to have simple possibility to
 run doctests on other modules, simple variable (list/tuple) can be a
 solution.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---