Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Stefan Forsberg
    @stefanforsberg
    @COsborn2 We have some code coverage active in one of our test projects. Take a look here: https://github.com/formulahendry/vscode-dotnet-test-explorer/blob/master/test/xunittests/.vscode/settings.json
    You should not have to perform some sed:ing so if you're using something else in terms of collecting code coverage data that does not work with our extension please provide more details and we'll see if we can fix it
    Janaka Abeywardhana
    @janaka
    @COsborn2 are you trying to generate coverage reports using the dotnet (vs)test command or a tool like Coverlet? Sounds like the former.
    @stefanforsberg have you looked into how dotnet test coverage generation works? I know something exists as I've seen chatter about it in Github issues but not sure how it works.
    Cameron J Osborn
    @COsborn2
    I am using Coverlet from dotnet test
    Stefan Forsberg
    @stefanforsberg
    @COsborn2 Yea, I think that's what other people who are doing (successful) coverage with our extensions are using too. Take a look at the xunittests project linked above and see if that gives any hints perhaps
    Cameron J Osborn
    @COsborn2
    Right, they do work, but I had to string a sed behind the command to better match my workflow. Thanks!
    digikiwam
    @digikiwam
    How do you stop a test that is hung in running state?
    Stefan Forsberg
    @stefanforsberg
    @digikiwam There isn't an easy way to do this now, the best way it probably outlined here https://github.com/formulahendry/vscode-dotnet-test-explorer/issues/133#issuecomment-416840103
    digikiwam
    @digikiwam
    @stefanforsberg thanks, until there is a better solution, we will use timeouts in our tests and/or run them from terminal.
    Stefan Forsberg
    @stefanforsberg
    @digikiwam Let's say the extension came with a "stop all running tests"-button, what would the expected behavior be after the button is pressed (besides stopping the tests)?
    Perform a test discovery again and re-generate the tree?
    digikiwam
    @digikiwam
    Just stop the hung test, exactly like stopping the process when running from CLI. It reverts back to "Not Run"
    The purpose of which, is not having to close VSCode and reopen it again, when a test hangs.
    Stefan Forsberg
    @stefanforsberg
    Well, when you stop the process you don't get any actual results though do you? So we don't really know what test is was running as it stopped or anything really besides that the user chose to stop the test runner.
    digikiwam
    @digikiwam
    That's the whole purpose, just to stop the code/process from executing. Say I am running Selenium .Net Core tests, there is something wrong with the webdriver finding the right browser driver. This can cause the test to just sit there and spin. A simple "cancel process" button or even a right click "cancel process" would be awesome. Yes, we won't get an error message to assist in debugging the issue (maybe that could come later) but it would at least mean we could keep the VSCode UI open.
    Stefan Forsberg
    @stefanforsberg
    @digikiwam We have started to implement this with 0.5.5 which was just released. It's non trivial to implement though so please give it a try and please provide some feedback if you have any (https://github.com/formulahendry/vscode-dotnet-test-explorer#new-in-055)
    Janaka Abeywardhana
    @janaka
    @stefanforsberg @formulahendry Just spotted Azure CI pipelines for extension publishing mentioned in the VS Code 1.29.x release notes. It mentions concurrent test run support on Windows, macOS, and Linux. I don't even remember what we use at the moment but that multi-platform bit caught my attention. https://code.visualstudio.com/docs/extensions/testing-extensions#_continuous-integration
    Janaka Abeywardhana
    @janaka
    Guys finally managed to get a bit more time on PR #83 Did some initial comparisons of discovery performance with 100+ tests. VS Test Platform is fast on initial discover it would seem. But on refreshes it is the same each time while to cli method is much quicker. Not sure why that is. Going to hookup execution next and see how that compares.
    Code pushed up to the branch which is also up-to-date with master. If anybody is interested in having a play. I've been using the Xunit launch config to test. Timing info is logged to the console.
    Edison Costa
    @EdisonCostaBR_twitter
    Can not make .NET Core Test Explorer working. Seams it not working with my VS Code C# environment. Always shows "Please open or set the test project and ensure your project compiles". I set testProjectPath property in user settings, but it still not discovering none of my msTests. Someone could help?
    Stefan Forsberg
    @stefanforsberg
    What do you see in the log (button to the right in the explorer top menu)? If you paste the text here it might be able to help us figure it out.
    Kai
    @Kai44881308_twitter
    Hey Guys, any hint on why Test Explorer does not find my Tests? csproj get's found correctly; log gives call of 'dotnet test -t -v=q' in correct path. Running the dotnet cmd by myself in the same Folder works too and gives me my Tests. Any idea?
    Stefan Forsberg
    @stefanforsberg
    @Kai44881308_twitter Can you paste the full log please?
    Kai
    @Kai44881308_twitter
    @stefanforsberg For sure :)
    Finding projects for pattern d:/Cloud\proj\src\Users.Tests/
    Found 1 matches for pattern in folder d:\Cloud\proj\src\Users.Tests
    Evaluating match d:/Cloud/proj/src/Users.Tests/
    Adding directory d:/Cloud/proj/src/Users.Tests/
    Executing dotnet test -t -v=q in d:/Cloud/proj/src/Users.Tests/
    Kai
    @Kai44881308_twitter
    finally, that's the Output of this dotnet command:

    Microsoft (R) Testausf├╝hrungs-Befehlszeilentool Version 16.0.1
    Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.

    Die folgenden Tests sind verf├╝gbar:
    ReturnEmptyListOnGet
    ReturnFiledListOnGet

    Stefan Forsberg
    @stefanforsberg
    Ah, I guess this is because we require to run the dotnet tooling in english. Have a look here: formulahendry/vscode-dotnet-test-explorer#77
    Kai
    @Kai44881308_twitter
    Thank you for that hint. Removing my localization Folder of the dotnet sdk helped.
    zaferduydu
    @zaferduydu
    Hi folks, I wrote a sample specflow test in VS CODE. But I don't view them in .NET TEST EXPLORER. Can you help me please ? I'm beginner in dotnet core.
    Stefan Forsberg
    @stefanforsberg
    @zaferduydu Hmm, I haven't run any specflow tests in a long time (like before .net core was a thing). I'm not sure I can help you I'm afraid.
    zaferduydu
    @zaferduydu
    @stefanforsberg Thanks for answer.
    I wrote Console.WriteLine("Hello"); in my unit test to .Net Core App. But I don't view log message, Why I didn't view log message ? Did you know ?
    Damir Bagapov
    @bonza
    Hi, did anyone manage to make it work in VS Code - Insiders?
    image.png
    image.png
    all good, sorry, it was simply hidden
    Stefan Forsberg
    @stefanforsberg
    👍
    Marcin
    @marcin-golebiowski
    Hi, I'm having problem with Test-Explorer. I run tests via Test-Exlorer and there are some problems. The icon of test status is spinning. There is no result of the test. However once it worked when I run one test
    I'm working
    on old, slow laptop
    Screenshot from 2019-08-04 14-17-47.png
    please help
    Gersch
    @thegerscheffect
    Can anyone help me understand hot to dispaly my test project inside the test explorer panel?
    how*
    Michael Bir
    @tekgiant
    I can't seem to get the extension to show up in the Activity Bar like Damir; but, for me, it's not a matter of being hidden. It's not even something I can unhide.
    Anyone have any experience with this issue?
    Janaka Abeywardhana
    @janaka
    @stefanforsberg Hey, looks like test explorer needs an update to be netcore 3.1 compatible. Did you have any plans to look into that? it's been a while, but if not I'll try take a stab.
    Stefan Forsberg
    @stefanforsberg
    @janaka Hey! So something seems to have happened with our approach that makes people not running on windows have issues with netcore 3.0. TBH I'm slightly burnt out trying to keep up with changes to causes our current approach to displaying test results utilizing generated trx files since it's a very brittle approach.
    So I think if I were to inject more energy into a test runner it would be to write a new one that only supports xunit since that would make tons of stuff much easier
    So TLDR: the current version is working well enough for me atm =)