#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 cwitty):
''the code is not trivially small''
Actually, it is; random_testing is 26 lines of code by my count, ignoring
docstrings and comments :)
But yes, once you include the tests, the documentation, and the comments,
it does look pretty big. I'll move it into its own file.
I'm not sure what to do about the iteration loop idea. I wouldn't want
iteration to be always handled in the wrapper; for example, that could
vastly slow down testing if the tester were written in Cython, or if the
testing function needed to do some non-trivial setup before starting the
loop. And there's no good way to tell the wrapper whether the wrapper or
the wrappee should handle iteration (it could key off the argument name,
but that doesn't sound like a good way).
Also, unfortunately, the primary source of random numbers in Sage (GMP's
Mersenne Twister implementation) doesn't let you read back the current
state.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5318#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
