× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Chevalier, Rick wrote:
I have a question about testing with this method.  In our shop, if I
have multiple procedures in a single source member that compiles into
a module and I change one of the procedures or add a new procedure I
will probably be required to test every procedure because the source
changed.  How do you handle this?  Can you get by with testing only
the changed/added code?

I would suggest that you only test the code that changes ... and code that interacts with the changed code.


If you have a procedure in a module that isn't called by any other procedure in that module, there's no need to test it.

Keep in mind that global variables could be considered implicit interactions (which is why I don't like using them). If you set a value in a global variable, other procedures in that module can be affected by it.

david



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.