On Wed, Jun 22, 2016 at 10:08 AM, Stephan Ehlen
<stephan.j.eh...@gmail.com> wrote:
>> > d) test unpickling of objects which seems to break rather often and is
>> > not covered at all by any of the doctests
>>
>> This can be done with doctests (possibly using the pickle jar).
>
>
> How would the pickles be stored/distributed?
I wrote something to solve "tested working pickles" problem that has
been in use in Sage forever. Please type
sage: search_src('pickle_jar')
and follow the trail... The actual pickles end up in a tarball in ext/.
Doctests seem to work very well for Sage, since the doctest framework
is very refined due to a lot of work over the years (e.g., parallel
testing, support for optional components, etc.), and having paste-able
guaranteed-to-work examples of all code is very useful. Doctests
*suck* for certain other types of software projects, where unit tests
(and libraries like node) are vastly better. I have at various
points written a lot of code to randomly test things in Sage, throw
random input at Sage, and we used to do things like collect all
timings of all doctests and compare between releases. I'm really
glad to see you're interesting in improving this functionality in
Sage. The one thing to be careful about is not to increase the burden
of the release manager.
-- William
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
