Search

VS 2012 Test runner generates Intellitrace files when running unit tests that call an executable by Ka_Shing

Active

4
0
Sign in
to vote
Type: Bug
ID: 780705
Opened: 3/5/2013 9:46:19 AM
Access Restriction: Public
0
Workaround(s)
3
User(s) can reproduce this bug

We discovered that the Visual Studio 2012 Test runner always generating IntelliTrace files and the results are that our servers run out of disk space.

It happens when we use VSTest to run the unit tests and if the unit test calls an executable it will always create IntelliTrace files. It doesn't matter what version of Visual Studio (Premium or Ultimate) is installed.

I didn't find a way to disable IntelliTrace by using a runconfig file.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

What category (if any) best represents this feedback?

 

Steps to reproduce


To reproduce the issue I've attached a zip file that contains a solution.
Run the batch file ExecuteTests.bat. The batch file will call the vstest.console.exe to run the unit test.

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

In the folder C:\Windows\temp you can find the intellitrace file.

Expected results

When running the batch file the Visual studio 2012 test runner will run a unit test. The unit test will call a console application.

Locale

 
File Attachments
File Name Submitted By Submitted On File Size  
Reproduction VSTest and Intellitrace problem.zip (restricted) 3/5/2013 -
Sign in to post a comment.
Posted by Microsoft on 3/5/2013 at 8:10 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 3/5/2013 at 9:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.