Dan,

In my experience, you need both kinds of testing. The automated tests are best suited for regression testing, making sure you didn't break something that worked before. Also, as you find bugs, you write tests that verify the bug, helping the programmer reproduce the problem, and making sure it's been fixed when the programmer submits the patch. Also, automated testing is great for a continuous integration setup. Every time a programmer checks in a module, you kick off a build that runs all your tests as it builds the distribution. Then it sends out an automated message with the results.

One of the tools I'm looking at, Jameleon, allows you to organize your tests functionally. Once you've got the basic tests encoded, almost anyone can write test cases without knowing much programming. It also allows for reuse of a lot of the testing code, which reduces the maintenance required. (Maintenance of test cases is one of the biggest problems.) I'm hoping it will help us keep this job manageable.


The biggest problem we face is that we don't have many testers. I'm hoping that if I put together a reasonable test infrastructure, we might be able to recruit a few more.

Ray

Dan Polansky wrote:
Hello Ray,

thank you for this kind of testing. I think it is very useful, much more so than a search for automatic testing tools, which would never discover the kind of bugs you have found. Admittedly, I have no experience with automated GUI tests; I am quite sceptical of them based on what I have heard from experienced people.

Dan


On 8/27/07, *Ray Benjamin* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Did some quick testing on latest code. Most of what I've found is
    minor and cosmetic. One thing that does concern me, is that the
    Preferences dialog doesn't work anymore. Is this something that is
    happening only on my machine?

    1) Selecting Tools -> Preferences, does nothing.
    2) There is no way to see what Physical Style a node is set to.
    (As a side note, why use the term Physical Style, when most people
    are probably familiar with the term style from CSS stylesheets and
    word processors? Just curious.)
    3) In Manage Patterns ..., the column that holds the name of the
    physical style/pattern, is too narrow for many of the names and
    can't be resized.
    4) Why use the term /Manage Patterns .../ for managing /Physical
    Styles/?
    5) No way to add or remove Physical Style in the Manage Patterns
    dialog. (Also, might be good to allow user to create a
    pattern/style based on the selected node. But that's probably an
    enhancement for later.)
    6) While Rich Formatting and Plain Text might do something, it
    isn't obvious that they do anything, and nothing happens when I
    use them. There should be some feedback to the user.
    7) Wouldn't it be clearer to use the term /Node Text Color/ or
    /Node Foreground Color,/ rather than /Node Color/?
    8) There should be some indication when a node has Blended Color.
    There should be a way to remove the blended color. If a node
    doesn't have colors that can be blended, the menu choice should be
    grayed out.

    Ray


------------------------------------------------------------------------

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
------------------------------------------------------------------------

_______________________________________________
Freemind-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freemind-developer

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Freemind-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freemind-developer

Reply via email to