Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    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?
    Jake Ginnivan
    @JakeGinnivan
    It is just an assertion library, so it works with any test framework
    Andrius Bentkus
    @txdv
    feels like information that should be provided in the readme
    @JakeGinnivan with any test framework you mean xunit, nunit and that microsoft visual studio thing?
    Jake Ginnivan
    @JakeGinnivan
    Sure do!
    Would even work in a console application 😋
    Andrius Bentkus
    @txdv
    how would it work with a console application?
    literally just a console application and that is it?
    Jake Ginnivan
    @JakeGinnivan
    If you can make it clearer, feel free to submit a pull request
    Yeah, shouldly does magic with stack traces to find the first method not inside shouldly and then reads the code before the extension method to make the error message
    Andrius Bentkus
    @txdv
    that sounds slow
    so it distinguishes between xunit, nunit, visual studio testing and when none of them is present?
    basically moves methods up until it finds the a method with a Test/Fact/whatever attribute from the specific unit testing framework?
    Jake Ginnivan
    @JakeGinnivan
    Relatively speaking, yes, but the magic probably means an extra 10-20ms. And most only happens when there is a failure
    We just throw an exception, so no direct integration needed
    Andrius Bentkus
    @txdv
    that is true
    Jake Ginnivan
    @JakeGinnivan
    Basically, it's the same as doing this `if(actual != expected) throw new Exception (actual + " does not equal " + expected);
    But awesome error messages
    Sasank
    @sasanknvs
    Hello all, I am facing an error while opening the solution "one or more projects in the solution were not loaded properly". I am using VS2015 community edition. are there any prerequisites to open the solution. Can someone throw some light on the issue i am facing ?
    Paulo Morgado
    @paulomorgado
    Hi! Any chance of addressing #471 ?
    whortleberrybearer
    @whortleberrybearer
    Is anyone else getting loads of tests failing with the latest master? I had a little look and it seems to be due to .netcore not fully defining the stack trace.
    whortleberrybearer
    @whortleberrybearer
    After a bit of a play, it looks like most of them will work if then run on .net45 (by removing the reference to .netcore), or including DiaSymReader files in the bin folder (as detailed here dotnet/corefx#21079). Is anyone looking at fixing this?
    Alex Allen
    @lxalln

    Hey guys, I'm a little stuck in figuring out how to get a more helpful message than "False should be True but was not".

    Running xUnit, in a netcoreapp2.0 app, executing the tests in Rider 2017.3. Shouldly 3.0.0

    I believe the PDB settings are correct and are being generated. I don't know how to proceed.