Thanks for helping make community forums a great place. We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
You can send your idea there and people can vote. The Visual Studio product team is listening to user voice there. Life is too short to be spent doing unnecessary things.Īs you said that if it is not the workaround you want to get, my suggestion is that you could submit this feature request: MSTest needs get its things together and not require of us developers to spend time adding meaningless instructions that add complexity to This is not a problem with other test tools such as nUnit and. All I want is for MSTEST to run my tests where they actually are and not do something completely differentĪny and all help would be much appreciated.įor this issue, if you really don’t want to use the attribute, like TejasJ’s suggestion, the testsetting file would be a workaround.
#HOW TO TROUBLESHOOT UNIT TESTS PYTHON IN VISUAL STUDIO CODE CODE#
Please note that I am not at all interested in polluting my code with attributes. Why is this happening and what can I do about it. For some reason some of my "copy-always" files do not make it over to the TestResults folder and thus my tests fail. The fact that all files from my project output directory are NOT copied. This is NOT what I wanted but I could have accepted it if it wasn't for But, if I choose to RunAll, the output directory is no longer the same but instead a directory called TestResults located in the solution file directory. If I run an individual test this works just fine as the test runs in the projects output directory, whereĪll necessary file are located. These files are used by unit tests and contain various input that they need. I have several test files that are set to be copied to the bin directory.
0 kommentar(er)
