The fundamental rule for testing functions requires that every function be tested in an already fully tested and debugged program. How can this be accomplished? Impossible! The main function must have all the functions it calls attached to get it to compile and run properly. The main function is tested with stub functions replacing each function. Write drivers for the stub functions to test them. Add each non-stub function in turn for testing. Write drivers for the function implementations one at a time to test them independently. Which of these "properties" of testing using stubs and drivers are correct? Using drivers and stubs is a lot of work for not much gain. Using drivers and stubs avoids trying to debug a large program all at once. Testing the pieces is difficult to do in any significant way. You need the entire program to run a meaningful test. Drivers run the pieces individually. They are temporary. They can be minimal, without i/o, having only data generating code, and not doing much (except possibly validating) with the information they return. Stubs are short programs that are fairly easy to write. They return only minimum data necessary for the caller to be debugged. Which of these remarks about overloading a function name is correct? C++ distinguishes between function overloaded implementations by examining differences in return types. C++ distinguishes between overloaded function versions by examining differences in the argument lists. C++ does not support function name overloading. To decide which version of overloaded functions, C++ looks first for an exact match in the argument list types and the parameter list types. If there is no match between the argument list types and the parameter list types C++ expects the programmer to supply type conversions to get a match