Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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.
    3 replies
    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 =)
    Marek Linka
    @mareklinka
    Hey everyone. Not sure how alive this channel still is, but here goes. I found an interesting problem with the extension - when opening a project folder with a solution file containing several test project AND not using the dotnet-test-explorer.testProjectPath, the extension generally fails to work when trying to execute a subset of all tests. After looking at the code, this is caused by the way dotnet test is executed. Without the testProjectPath override, the tests are executed against the solution file (which is valid for dotnet test). This causes all the test projects to be executed, but of course only one of them contains tests matching the test filter. Others produce a TRX file with "No test matches the given testcase filter". Unfortunately, the extension sees this first TRX file, finds to test results, but still updates the UI and thinks the test run is complete. A related problem: the test process is still running at this point and might be for some time, depending on the test complexity. The extension does not wait for the test process to finish.
    After poking at the code, I think I found a relatively small fix for both of these problems - would there be interest for a PR? Is someone still accepting them?
    Janaka Abeywardhana
    @janaka
    @mareklinka sorry, we are a bit quiet in here. Did you submit a PR? I've been away from this project for a while. Did a quick search and didn't spot anything. If you are still interested please do submit a PR.
    Janaka Abeywardhana
    @janaka

    @stefanforsberg @formulahendry I just came across a folk of our extension being published. See here. Were you aware? I DM's the person on Twitter to find out the reasons. It seems like they are doing it to learn and have given full credits etc. So not pretending to pass on this work as theirs. I'm concerned that it's confusing to users. It certainly confused me.

    I've invited him to contribute to this project. Also, come here and chat if he wishes to get involved in a deeper way.

    image.png
    This is what the results look like when you search for the extension
    Stefan Forsberg
    @stefanforsberg
    Hmm, nothing against forking but using the same name and the same logo is very confusing as you say.
    thanks for understanding :)
    @janaka
    Janaka Abeywardhana
    @janaka
    Thanks @hjdarnel
    Stefan Forsberg
    @stefanforsberg
    💖
    💖
    💖
    Mark McGookin
    @markmcgookin

    Hi folks, hoping someone can help me out here... I have a UnitTest project at the path
    <ProjectRoot>Tests/UnitTests/my-unit-tests.csproj

    it's not being picked up, so I am adding the setting:
    "dotnet-test-explorer.testProjectPath": "Tests/UnitTests/*tests.@(csproj|vbproj|fsproj)"

    and it is still not picking up any tests... am I doing something wrong here or is it too 'deep' for it to be picked up? It doesn't work if I just paste in a relative path either.

    Mark McGookin
    @markmcgookin
    Ah looks like its an issue with the Regex because I am using Net5.0. Looks like they/you are working on it. formulahendry/vscode-dotnet-test-explorer#288
    Stefan Forsberg
    @stefanforsberg
    👍
    andrewVolodko
    @andrewVolodko
    Have the same issue, but I'm not using regex. Tests are not found on Mac OS. Maybe there is any solution?
    Stefan Forsberg
    @stefanforsberg
    If it's related to netcore 5 the solution is awaiting @formulahendry to release it
    Janaka Abeywardhana
    @janaka
    @stefanforsberg looks like the latest version isn't released yet. I also emailed @formulahendry.
    Janaka Abeywardhana
    @janaka
    v0.7.5 has been released.
    Ahmet Burhan Simsek
    @simsekahmett
    hey hey
    Ahmet Burhan Simsek
    @simsekahmett
    i see some new PR's merged, any release date for pending fixes ?
    Janaka Abeywardhana
    @janaka
    Hi @simsekahmett, I don't think we have anything else planned for release at the moment. Was there particular fix you are after?
    Ahmet Burhan Simsek
    @simsekahmett
    well, i am waiting for auto-attaching to process fix
    Ahmet Burhan Simsek
    @simsekahmett
    also i wonder why "Could not find test (no symbols found)" for the discovered tests ?
    Stefan Forsberg
    @stefanforsberg
    @formulahendry Hey Jun, just wanted to let you know that I won't be able to look at and/or merge things in the test explorer for a foreseeable future.
    Jeremy
    @jmoglesby
    Would anyone here be able to help me figure out why my test are not being found (initial setup)?