[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Axiom-developer] Re: Executed Examples in documentation ---> Testsuite

From: Ralf Hemmecke
Subject: [Axiom-developer] Re: Executed Examples in documentation ---> Testsuite
Date: Mon, 18 Aug 2008 14:14:50 +0200
User-agent: Thunderbird (X11/20080707)

You could also move some checking time to the users machine. At the time the documentation is rendered, the commands in ++E are executed and compared internally with the ++R stuff. Since execution might take some time, first show the ++R output and spawn a background process that compares the output of ++E with ++R. If that is equal, everything is fine. If it is different. That is a bug. So notify the user with all the information (about his system) that s/he should send to a bugtracker.

This could potentially introduce a lot of overhead into the execution
of the )display operation command. The "map" function, for instance,
has about 80 instances which would introduce 80 background executions.
If we could do that in parallel (since each test is independent) this
might make sense on a multicore machine. But we can certainly test at
build time.

Of course you could (and should) test at build time. And failure probablility for doc execution tests is certainly low if a user installs for example a binary axiom debian package (that was tested at

But you remember there were pages in hyperdoc that could be explicitly executed by pressing a button. So if that is connected to ++E and ++R that would not be a problem, because the user asked for it. Well of course, you must check that the user did not modify the ++E stuff before you compare with ++R.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]