Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Jake Ginnivan
    @JakeGinnivan
    its the only one which supports dotnet test
    command line also works if you run dotnet test in the test project folder
    or run build.ps1 to build and test everything
    Never though id be saying, am looking forward to them switching to msbuild
    Dylan Beattie
    @dylanbeattie
    ah. visual studio has a test runner. of course it does.
    Joseph Woodward
    @JosephWoodward
    JetBrains say it shouldn't be long until ReSharper's test runner supports .NET Core
    @dylanbeattie Did you get to the bottom of that issue you mentioned on Twitter yesterday?
    Dylan Beattie
    @dylanbeattie
    I'm looking into it now.
    OK, how do I add a project reference to Shouldly from a .NET 4.5.1 class library project?
    I want to be able to step into Shouldly's assertion code from the test that's failing to find out why, but I cannot seem to get them running happily in the same solution.
    Dylan Beattie
    @dylanbeattie
    ok, got it... for some reason VS won't add a project reference but by adding a DLL reference directly it's letting me step into Shouldly code.
    Dylan Beattie
    @dylanbeattie
    It's not a Shouldly issue. It's to do with Object.Equals(x,y) returning false if x and y are similar anonymous type instances that have come from different assemblies...
    Joseph Woodward
    @JosephWoodward
    That's interesting, didn't know that was the case.
    Shame you can't create a PR to the MSDN docs to stop others getting tripped up by this in the future.
    Tom Wright
    @tdwright
    Hi all. I'm hoping to try and get involved as a contributor. Thought I'd start with a couple of small issues. Problem is, I appear to have broken the build before going any further than a couple of markdown files. Any idea what's going on? shouldly/shouldly#406
    Appears to be a timeout scenario (FuncOfTaskOfTWithTimeoutScenario) timing out: https://ci.appveyor.com/project/shouldly/shouldly/build/2.8.3-PullRequest.406+7.build.289/tests
    João Barbosa
    @bmpj13
    Hello everyone. I'm also interested in helping as a contributor. @JosephWoodward , I sent you an email so I could get a bit more of information about the project (I didn't want to spam the chat).
    Hope everyone's doing fine :smile:
    Jake Ginnivan
    @JakeGinnivan
    Hey, will get back to you today with details and info
    AdityaTulasi
    @AdityaTulasi
    Hi. I'm too am interested in contributing. Please send that e-mail to me as well.. E-mail ID tulasiaditya1993@gmail.com
    @bmpj13 Can you please forward the e-mail of instructions you get for contributing?
    Jake Ginnivan
    @JakeGinnivan
    The best way is to pick up an up for grabs issue
    João Barbosa
    @bmpj13
    Hey guys, quick question. I just downloaded the most recent version of Shouldly, that has "build passing". For some reason, some unit tests fail when I try to run them. Did I miss something?
    Guilherme Lopes de Morais Filho
    @GuilhermeMorais
    Hi Everyone. I'm also interested in helping as a contributor. Any Read first file? Where you need help.
    SwapnaBru
    @SwapnaBru
    Hey There! I am interested in contributing .
    Joseph Woodward
    @JosephWoodward
    Hi, @bmpj13 Can you create an issue of the failing test you're seeing? I'd like to look into it.
    idormenco
    @idormenco
    Hello ,is there a tutorial how to build Shouldly in vs 2017 or how to set up working environment ? Regards
    Tom Liversidge
    @tomliversidge

    hi, liking shouldly so far, but my error messages do not look they do in the examples so i'm wondering if i'm doing something wrong. for example:

    var something = 10;
    something.ShouldBe(9);

    I was expecting an error message of "something should be 9 but was 10" but what i get is "9
    should be
    10
    but was not"

    i'm using 2.8.3, tried in Jetbrains Rider and terminal (on mac) just doing dotnet test
    David Dancy
    @programmation
    Hi all, I'm trying to use Shouldly on Visual Studio for Mac in a Xamarin project. When I create a test and run it (with NUnit if it makes a difference) I get an exception thrown by Shouldly itself: "The type initializer for 'Shouldly.ShouldlyConfiguration' threw an exception ----> System.TypeInitializationException : The type initializer for 'Shouldly.Configuration.KnownDiffTools' threw an exception. ----> System.EntryPointNotFoundException : CreateToolhelp32Snapshot"
    Any ideas?
    Joseph Woodward
    @JosephWoodward
    @programmation Hi David, yes this is a known issue. We've got a fix for this being released shortly. My best solution right now would be to roll back to 2.8.2 for the time being.
    Out of interest, what ShouldX extension method are you using that's causing this?
    David Dancy
    @programmation
    @JosephWoodward many thanks for that info. I just tried 2.8.2 and it worked. FWIW the error happened when I used a TimeSpan as my test value. Thanks again!
    Joseph Woodward
    @JosephWoodward
    @programmation No problem, the latest beta version has just been published which has the fix in it (https://www.nuget.org/packages/Shouldly/3.0.0-beta0003)
    Lashas83
    @Lashas83
    Hello,
    Is there some summary what's new in 3.0?
    Joseph Woodward
    @JosephWoodward
    Beta 2 saw a fix in a mono issue that I need to add to the release notes
    The main reason it's a version 3 release is because we've dropped support for NET 3.5
    Lashas83
    @Lashas83
    Thanks.
    One more thing - does shouldly have some way of exposing configured assertion as variable, so I can check multiple objects with it, and still have single output?
    Currently I do not find anything like that in API, but maybe that's only me?
    dyronald
    @dyronald
    Hi everyone.
    I forked and built the source code with VS2017. But when I ran the test, I'm getting 4 failed tests. All relating to incorrect exception messages when source code is enabled. I'm not quite sure if this some sort of build configuration mistake on my part or an actual issue. Should I raise it?
    Joseph Woodward
    @JosephWoodward
    Hi @dyronald, I've been looking into these as culprits, I'm not sure why they're failing yet. I've also been in the process of trying to port the tests to .NET Standard.
    krzysztofowsiany
    @krzysztofowsiany
    Hi, i em Krzysztof from poland. Time to time i use shouldly. Now i wone join to evolve library. Sorry for my english. I still learn.:)
    David Revoledo
    @davidrevoledo
    Hello everybody :)
    Andrius Bentkus
    @txdv
    hi guys
    do i need to use xunit with shouldly?
    is shouldly only an addition, which makes the reported strings/exceptions look super nicer?