I prefer Google Docs, since I don't know the wiki code very well. I think, the most logical approach is to enumerate most of the notebook functionality, as well as notebook-related bugs that are open or have been closed in recent versions, and only then compile a testing checklist. I will give it a lot more thought when I get home.
Igor On Wed, Aug 27, 2008 at 9:36 AM, Timothy Clemans <[EMAIL PROTECTED]>wrote: > So should we first write tests for all the new bugs in released > versions? Igor do you want write this up together on the Sage Wiki or > using Google Docs? > > On Wed, Aug 27, 2008 at 12:22 PM, William Stein <[EMAIL PROTECTED]> wrote: > > > > On Wed, Aug 27, 2008 at 9:13 AM, Igor Tolkov <[EMAIL PROTECTED]> wrote: > >> > >> Wow, it's worse than I thought. I have the same problem, but thought > >> it was due to my local changes. Apparently not. > >> > >> I believe this is in direct consequence to a bug that William and I > >> were discussing. When viewing published worksheets, the active > >> username is "pub", instead of your username. > >> > > > > Well just for clarification this is a *brand new* bug that was just > > introduced in the newest version of Sage, by I think either Timothy, > > you, me or Mike Hansen. > > > > It's amazing the number of notebook bugs that have been > > introduced recently by so many people working on the notebook > > code. > > > > I think I should spend a day and fix all the known notebook books, > > then declare a 100% freeze on notebook development until there > > is a rigorous testing framework in place. > > > > For the people working on the notebook for pay -- Timothy Clemens > > and Igor Tolkov -- you two *need* to make a by hand checklist > > so you can test the notebook by hand. You're being paid, so I'm > > officially requesting that you sit down and make a step-by-step > > checklist that would take at most 30 minutes to test by > > hand, and which allows us to verify that there aren't any > > obvious notebook bugs. This list should have tests that reveal > > all known notebook bugs, and tests lots of other stuff as well. > > It will be gone through step by step before sage-3.1.2 gets > > released. > > > > Again, you're being paid and I'm asking you both to do absolutely > > NO FURTHER WORK for pay on Sage until you've made a > > step-by-step testing checklist as outlines above. > > > > Once a fancy Selineum or whatever testing method exists, > > then it can have the step-by-step testing system you device > > input into it. Still, I want the testing system laid out in > > writing first. E.g., it could be something like: > > > > (1) Create a new fresh notebook. > > (2) Create a new user. > > (3) Create a worksheet as that user. > > (4) Enter 2+2 in the first cell and press shift enter. > > > > etc. > > > > Also, it should test loading an old notebook. For example, > > sage-3.1 contained a major bug where loading all old notebooks > > resulted in data loss, etc. (Good thing I caught it.) > > > > -- William > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
