How to disable TestResults folder in Visual Studio?
up vote
4
down vote
favorite
Visual Studio is generating a lot of empty folders in the TestResults subfolder of C# projects. Is there a way to disable it? I often delete more then 5k of them.
Deploy_UserName 2017-10-31 18_13_17
Deploy_UserName 2017-10-31 18_57_15
Deploy_UserName 2017-10-31 19_18_32
Deploy_UserName 2017-10-31 19_19_47
Deploy_UserName 2017-10-31 19_20_21
Deploy_UserName 2017-10-31 19_20_26
Deploy_UserName 2017-11-02 16_33_32
Deploy_UserName 2017-11-02 16_34_11
Deploy_UserName 2017-11-02 16_45_12
Deploy_UserName 2017-11-02 16_45_39
Deploy_UserName 2017-11-02 17_09_55
And this goes like that a few thousand tiems. All are empty.
I'm not sure if they actually slow VS down but I'd rather not have them.
visual-studio-2017
add a comment |
up vote
4
down vote
favorite
Visual Studio is generating a lot of empty folders in the TestResults subfolder of C# projects. Is there a way to disable it? I often delete more then 5k of them.
Deploy_UserName 2017-10-31 18_13_17
Deploy_UserName 2017-10-31 18_57_15
Deploy_UserName 2017-10-31 19_18_32
Deploy_UserName 2017-10-31 19_19_47
Deploy_UserName 2017-10-31 19_20_21
Deploy_UserName 2017-10-31 19_20_26
Deploy_UserName 2017-11-02 16_33_32
Deploy_UserName 2017-11-02 16_34_11
Deploy_UserName 2017-11-02 16_45_12
Deploy_UserName 2017-11-02 16_45_39
Deploy_UserName 2017-11-02 17_09_55
And this goes like that a few thousand tiems. All are empty.
I'm not sure if they actually slow VS down but I'd rather not have them.
visual-studio-2017
add a comment |
up vote
4
down vote
favorite
up vote
4
down vote
favorite
Visual Studio is generating a lot of empty folders in the TestResults subfolder of C# projects. Is there a way to disable it? I often delete more then 5k of them.
Deploy_UserName 2017-10-31 18_13_17
Deploy_UserName 2017-10-31 18_57_15
Deploy_UserName 2017-10-31 19_18_32
Deploy_UserName 2017-10-31 19_19_47
Deploy_UserName 2017-10-31 19_20_21
Deploy_UserName 2017-10-31 19_20_26
Deploy_UserName 2017-11-02 16_33_32
Deploy_UserName 2017-11-02 16_34_11
Deploy_UserName 2017-11-02 16_45_12
Deploy_UserName 2017-11-02 16_45_39
Deploy_UserName 2017-11-02 17_09_55
And this goes like that a few thousand tiems. All are empty.
I'm not sure if they actually slow VS down but I'd rather not have them.
visual-studio-2017
Visual Studio is generating a lot of empty folders in the TestResults subfolder of C# projects. Is there a way to disable it? I often delete more then 5k of them.
Deploy_UserName 2017-10-31 18_13_17
Deploy_UserName 2017-10-31 18_57_15
Deploy_UserName 2017-10-31 19_18_32
Deploy_UserName 2017-10-31 19_19_47
Deploy_UserName 2017-10-31 19_20_21
Deploy_UserName 2017-10-31 19_20_26
Deploy_UserName 2017-11-02 16_33_32
Deploy_UserName 2017-11-02 16_34_11
Deploy_UserName 2017-11-02 16_45_12
Deploy_UserName 2017-11-02 16_45_39
Deploy_UserName 2017-11-02 17_09_55
And this goes like that a few thousand tiems. All are empty.
I'm not sure if they actually slow VS down but I'd rather not have them.
visual-studio-2017
visual-studio-2017
asked Nov 12 '17 at 17:45
t3chb0t
19012
19012
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
I didn't find a way how to disable it completely but at least an acceptable workaround. It moves them to a location that is more appropriate for them. It goes like that:
Create a
.runsettingsfile in your solution directory (you can give it any name - just keep the extension unchanged) with the following contents which will place theTestResultsdirectory in the%temp%location of your machine. If you're not sure where it is, you can always check it in the command-line by callingecho %test%or just pick any other location.
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
<RunConfiguration>
<ResultsDirectory>%temp%TestResults</ResultsDirectory>
</RunConfiguration>
</RunSettings>
You now have to inform your test runner about it.
- for MSTest users: go to
Test > Test Settings > Select Test Settings File
- for ReSharper users: go to
ReSharper > Options > Tools > Unit Testing > Ms Testand pick theUse specific test settings file.
- for MSTest users: go to
btw, these folders are created always and just won't be deleted if you interrupt the test-runner so it won't clean them up.
(Inspired by Configure unit tests by using a .runsettings file)
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
I didn't find a way how to disable it completely but at least an acceptable workaround. It moves them to a location that is more appropriate for them. It goes like that:
Create a
.runsettingsfile in your solution directory (you can give it any name - just keep the extension unchanged) with the following contents which will place theTestResultsdirectory in the%temp%location of your machine. If you're not sure where it is, you can always check it in the command-line by callingecho %test%or just pick any other location.
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
<RunConfiguration>
<ResultsDirectory>%temp%TestResults</ResultsDirectory>
</RunConfiguration>
</RunSettings>
You now have to inform your test runner about it.
- for MSTest users: go to
Test > Test Settings > Select Test Settings File
- for ReSharper users: go to
ReSharper > Options > Tools > Unit Testing > Ms Testand pick theUse specific test settings file.
- for MSTest users: go to
btw, these folders are created always and just won't be deleted if you interrupt the test-runner so it won't clean them up.
(Inspired by Configure unit tests by using a .runsettings file)
add a comment |
up vote
0
down vote
accepted
I didn't find a way how to disable it completely but at least an acceptable workaround. It moves them to a location that is more appropriate for them. It goes like that:
Create a
.runsettingsfile in your solution directory (you can give it any name - just keep the extension unchanged) with the following contents which will place theTestResultsdirectory in the%temp%location of your machine. If you're not sure where it is, you can always check it in the command-line by callingecho %test%or just pick any other location.
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
<RunConfiguration>
<ResultsDirectory>%temp%TestResults</ResultsDirectory>
</RunConfiguration>
</RunSettings>
You now have to inform your test runner about it.
- for MSTest users: go to
Test > Test Settings > Select Test Settings File
- for ReSharper users: go to
ReSharper > Options > Tools > Unit Testing > Ms Testand pick theUse specific test settings file.
- for MSTest users: go to
btw, these folders are created always and just won't be deleted if you interrupt the test-runner so it won't clean them up.
(Inspired by Configure unit tests by using a .runsettings file)
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
I didn't find a way how to disable it completely but at least an acceptable workaround. It moves them to a location that is more appropriate for them. It goes like that:
Create a
.runsettingsfile in your solution directory (you can give it any name - just keep the extension unchanged) with the following contents which will place theTestResultsdirectory in the%temp%location of your machine. If you're not sure where it is, you can always check it in the command-line by callingecho %test%or just pick any other location.
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
<RunConfiguration>
<ResultsDirectory>%temp%TestResults</ResultsDirectory>
</RunConfiguration>
</RunSettings>
You now have to inform your test runner about it.
- for MSTest users: go to
Test > Test Settings > Select Test Settings File
- for ReSharper users: go to
ReSharper > Options > Tools > Unit Testing > Ms Testand pick theUse specific test settings file.
- for MSTest users: go to
btw, these folders are created always and just won't be deleted if you interrupt the test-runner so it won't clean them up.
(Inspired by Configure unit tests by using a .runsettings file)
I didn't find a way how to disable it completely but at least an acceptable workaround. It moves them to a location that is more appropriate for them. It goes like that:
Create a
.runsettingsfile in your solution directory (you can give it any name - just keep the extension unchanged) with the following contents which will place theTestResultsdirectory in the%temp%location of your machine. If you're not sure where it is, you can always check it in the command-line by callingecho %test%or just pick any other location.
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
<RunConfiguration>
<ResultsDirectory>%temp%TestResults</ResultsDirectory>
</RunConfiguration>
</RunSettings>
You now have to inform your test runner about it.
- for MSTest users: go to
Test > Test Settings > Select Test Settings File
- for ReSharper users: go to
ReSharper > Options > Tools > Unit Testing > Ms Testand pick theUse specific test settings file.
- for MSTest users: go to
btw, these folders are created always and just won't be deleted if you interrupt the test-runner so it won't clean them up.
(Inspired by Configure unit tests by using a .runsettings file)
answered Nov 18 at 10:18
t3chb0t
19012
19012
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1267698%2fhow-to-disable-testresults-folder-in-visual-studio%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown