As you may have noticed, I am currently working on Binary Clock 3.0 for Palm OS. The WristPDA suport basically is there, but there still is this one little annoying fatal alert that I can’t reproduce, don’t know where it hides and generally can’t do much against.
Anyways, since I have my silent Acer notebook, running Gremlins over night is finally possible without getting my family in a “Kill him” mood. For all of you new to the term, gremlins are the automatical testing tool in the Palm OS emulator/simulator. What they do is simple – they fire random clicks, taps, drags and characters at your application until it breaks.
Sounds good…but totally sucks for Binary Clock for a variety of reasons:
They tend to hang around Global Find all the time
Don’t ask me why, but 50% of the time I see the gremlins taping around global find entering crap text. Basically, they waste my poor Centrino Duo’s cycles testing the Palm OS…as if PalmSource couldn’t afford an Acer Aspire .
They seem to restart the application way to often
Same thing as above. Binary Clock gets restarted all the time, and thus the gremlins keep hanging around the hint form. Great!
They dont seem to exercise the functions “hidden behind menus” very much
Dont ask me why this happens…but 10000 gremlins didnt manage to change the Binary Clock color…
Please don’t take this as “gremlins are bad” – but gremlins or any other “screen mass tappers” are IMHO not useful as sole testing tool. They may find the one or the other bug, but can not replace the human testing crew doing a few “hammer tests”… . What do you think?