In
[EMAIL PROTECTED],
on 09/08/2006
at 09:11 AM, Darth Keller [EMAIL PROTECTED] said:
Are you suggesting having test cases for your non-SMS datasets?
Not specifically; I'm suggesting retaining test cases for every
important component of your system and applications.
--
Shmuel (Seymour
In
[EMAIL PROTECTED],
on 09/07/2006
at 03:04 PM, Darth Keller [EMAIL PROTECTED] said:
I'd also strongly recommend that if you're going to work much with
SMS that you learn to use Naviquest and start building a library of
Test Cases.
Don't limit your test-case library to SMS; regression
Don't limit your test-case library to SMS; regression testing is a
goodness.
Are you suggesting having test cases for your non-SMS datasets? I'd have
to agree to that too. Regression testing is also why I vary rarely change
or delete older test cases. The non-SMS and the older test cases
I strongly recommend adding WRITE statements to your SMS routines. Some
of the people on the list only use them when debugging a problem. I put
them in and leave them in. Basically my code stubs look like:
When (condition)
Set
Write
Exit
End
Yes, applications batch jobs see
4 matches
Mail list logo
