Whil Hentzen had an article in Foxtalk about a year ago on testing ideas. One that I remember is that they hire high-school students to test.

>This goes beyond the scope of the original thread, so I'll start a new one:
>
>>>I've only seen this when my brain has left the building but I haven't. < g >
>>
>>ROFL.
>>It's a good starting position to run 11 concurrent copies of application, eh? :).
>>
>>>Just a suspicion here. How are you handling your READ EVENTS/CLEAR EVENTS. Are you using a Top Level Form and is the form that "disappears" a modal/modeless form done in the screen or top level form?
>>>
>>>>We have an error where we randomly have a screen disappear (apparently from memory). Has anyone else seen this behavior?
>
>Running 11 copies could be one way of testing it. We've done worse things to our apps: the final test was laying both hands with fingers spread over the keyboard, pressing at least a dozen keys at once (with accent on the gray keys), and seeing what happens. The framework was OK if it survived without any damage to data :). The origin of this is my custom of just pressing Enter on various machines at exhibitions and fairs - half of them crash or burn after that :).
>
>Anybody else for weird testing techniques?