Re: Advice for beginner
User (firstname.lastname@example.org) posted:
Focus on attaining a reasonable level of modularity. You can always
improve on what you already have later on. You have to balance the cost
of rework against the up-front cost of doing everything "right" the first
time. It's easy to get carried away with abstracting every possible
object/property in an application. I largely avoid the above issues by
encapsulating the actions for each functional area in one or more common
subroutines (e.g., 3 subs for areas that support Add, Update" and Delete
operations) almost always stored in library files, NOT in test scripts).
I also build test evaluation/logging logic for the most common scenarios
into each test sub. I write modular helper subs/funs whenever I think
they will be useful elsewhere (avoid ending up with 17 different
variations of each).
Advice for beginner
User MArk B. (email@example.com) posted:
Use somebody else's. :-)
You might find ComboBoxes.zip especially appropriate.
Yet another wheel...
"Gordon Hill" <firstname.lastname@example.org> wrote in message