Now maybe it's changed, I havn't looked at any QP official docs as of late,
but it used to say, it would be tested for functionality per your
documentation. In fact, we had to provide either (a) a test plan, or (b) a
manual.
We opted for option (b) and failed becuase:
1) We misspelled a word in a 'tip' screen
2) The manual indicated a field would hold 72 characters when in actuality,
it would only hold 71.
(Which do you think we changed the app or the manual ?)
3) We did not support Global Find and did not specifically state that we
didn't in our manual (this is where we got an exception, it made no sense
to support find in our application).
The application I'm looking at right now fatal errors if you delete more
than 2 records and try to open any one or create new with an invalid index.
That is something that certification testing 'should' catch. But in a lot
of apps it's very easy to trap gremlins into only exercising a couple of
screens and not let it wander too far. ;-) perhaps that's what happened
here.
-MD
-----Original Message-----
From: Elia J. Freedman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, March 03, 1999 12:23 PM
Subject: RE: Graffiti/Indicator question
>Doing what the docs say is one of the guidelines, but they don't test other
>cases besides examples or statements in the docs. They aren't there to
make
>sure your app works correctly. Their purpose is to make sure it adheres to
>the visual and use guidelines specified by Palm.
>Elia
