#5318: [with patch, needs review] ideas for improving random testers (like 
#4779)
-------------------------+--------------------------------------------------
 Reporter:  cwitty       |       Owner:  mabshoff  
     Type:  enhancement  |      Status:  new       
 Priority:  major        |   Milestone:  sage-3.4.2
Component:  doctest      |    Keywords:            
-------------------------+--------------------------------------------------

Comment(by nthiery):

 Hi!

 Cool stuff. I am about to give it a thumb up!

 Three comments:
  - When the category stuff will be in there, we should merge this into the
 category-held tests.
    But let's not wait for that.

  - The code is not trivially small, so I would put it in a separate file
 with the same name as the decorator

  -  while we are at saving on boiler plate: would it be possible for the
 wrapper
     to also handle the iteration loop?

    One nice side benefit is that the wrapper would be aware of the value
 of the seed at the begining of each iteration, and therefore could report
 it in case of trouble (I have not yet played with random generators in
 python, but I assume that we can access the current value of the seed
 after a couple random generation). Reproducing  the error would then
 involve a single iteration.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5318#comment:3>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to