No Test Results Created

Hi Mike,



Are you running individual tests (for example, .mds /run /p /t or .mds /run /p /u /r) instead of the entire project suite (.pjs /run)? If you are, the test logs are created in the project's Logs folder instead of the project suite's Logs folder.

Hi Helen,



Yes, I'm running individual tests (you helped me a week or so ago with the syntax).  There still are no logs either at the project level or anywhere else if I run it through Test Execute.  On the development machine (Test Complete) logs are created just fine.



[edit]  Here's the commandline call:



start /wait "TestExecute" "C:\Program Files (x86)\Automated QA\TestExecute 8\Bin\TestExecute.exe" "\\mb-swtest-dc\tc_scripts\NDCA\AnalysisRequest\AnalysisRequest.mds" /p:AnalysisRequest /t:"Script|testCreateRequests|testCreateRequests" /r /e /SilentMode

Mike,



You might try creating an event handler for OnStopTest and then explicitly saving your result files.

We're also  running Hudson jobs to start our TestExecute scripts

although I only recently turned off the TestExecute logging.



Regards,  Curt Hicks





function GeneralEvents_OnStopTest(Sender)

{



   Log.Message("about to save results on stop test event");

   Log.SaveResultsAs("c:\\TestCompleteLogs", 1, true);

   Log.Message("done saving results");

}

Hi Mike,



I see your project is in a network folder, so it's probably opened in networked mode. In this case, you should be able to find the logs at the following location:

\\<project-suite-folder>\[your-computer-name]\<project-name>\Log



Please let me know if this is the case, otherwise, we'll have to do some more investigations.

Hi Helen,



Yes, the log files are there, thanks for the pointer.  Possible to "undo" this?  I vaguely remember the network option, and I thought I clicked 'No" on the dialog.  I deleted all log files and the contents ion the Log file directories.  When I run again, it creates the <machine-name> directory again.



I suppose I can implement Curt's method (Thanks Curt!), but that's not optimal.  Essentially I'd like to be able to run tests via TestExecute, and then on a different machine (via Test Complete) look at the latest logs, without having to figure out which machine it ran on, etc.  Like Curt, I'm running the test remotely via Hudson(Jenkins), so you never know what machine it ran on unless you do some digging to find out.



I'd like to just be able to run the tests remotely, launch Test Complete, load the project and view the latest results for the project(s) and the tests.

Hi Mike,

Possible to "undo" this?

Yes, please see the following thread:

Switching networked mode on

Thanks Helen, I removed it.



I suppose that I'll have to implement Curt's suggestion.  When I run on Test Execute, the remote <computer-name> directory is created, and inside there are the logs.  The problem is that when I load the project, the logs are not available.  They don't load into the Project Suite Logs, I'd have to manually add them, and that's just too clumsy and too time consuming to load them up.  I know if the tests pass/fail by looking at the results in Jenkins, but there's really no easy way to know via Test Complete.



I have 10 machines that the test could run on, and I'm assuming that the <computer-name> directory will also be created when/if the test runs on that directory.  That's just too many levels to go through to find results.



So, what are my options?  I'd like to have one place (per project, inside the Project Suite) that ALL logs go to.  Once I figure that out, can Test Complete be configured to look at those directories by default and/or start up?