Probably I was not very clear. I do not want to do anything more that what you are suggesting, ie, writing scripts that will use all my code paths. The question is whether there are suggestion on how to do it and, more importantly, how would you make use of the results of this "stub" script: if the script you are testing interact with the log file, how can you discriminate when your stub script is testing a "normal" code path and when it is proofing an "error handling" path.
Here an example: the datadriverSetUp return true if a ADO connection was succesful, false otherwise.
function Test_datadriverSetUp()
{
Log.Message("Test Excel driver connection:");
var hasWorked = datadriverSetUp("testdata\\Sample_Testcases.xls", "PC control");
var hasFailed = (datadriverSetUp("testdata\\Sample_Testxxxxx.xls", "PC control") == false);
if (hasWorked && hasFailed)
Log.Checkpoint("libPrepare.datadriverSetUp() is functional");
else
Log.Error("libPrepare.datadriverSetUp() is corrupted.", "");
}
In case of an error in the connection, datadriverSetUp will write an
error on the log. The script is working fine, and I write add a
checkpoint to the log, but in the same log I will have the error that
correctly my tested function raised. I would like to see whether my scripts are all working properly: I was thinking of creating a txt file where writing all the script-testing result, but maybe you have a better idea.