I'm familiar with the concept of a TestDeploymentDirectory which Visual Stuido uses when running a unit test or test list.
Studio creates a structure like:
Test Results\
User_Machine\
\In
\Out
All files needed to execute the test are copied to the Out folder, ie "Deployment Items" Any screenshots, logs, etc generated by the test can be stored in the In folder for later analysis. This structure makes solid logical sense to have a "folder per execution" to isolate the collateral and results.
Test Studio on the other hand doesn't seem to have this type of structure.. Logs goto c:\WebAiiLog and I see no "result" folder for a specific test list execution. I would like to add code to my tests to output screenshots from my tests and it would be nice to somehow associate them with a test list execution. Not just a bunch of files in c:\WebAiiLog
Is there any built in mechanism or best practice for this?
Studio creates a structure like:
Test Results\
User_Machine\
\In
\Out
All files needed to execute the test are copied to the Out folder, ie "Deployment Items" Any screenshots, logs, etc generated by the test can be stored in the In folder for later analysis. This structure makes solid logical sense to have a "folder per execution" to isolate the collateral and results.
Test Studio on the other hand doesn't seem to have this type of structure.. Logs goto c:\WebAiiLog and I see no "result" folder for a specific test list execution. I would like to add code to my tests to output screenshots from my tests and it would be nice to somehow associate them with a test list execution. Not just a bunch of files in c:\WebAiiLog
Is there any built in mechanism or best practice for this?