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
    then it is just an assertion within your test method
    Phil Scott
    @enkafan
    @matkoch are you asking how shouldly itself knows how to generate the text?
    Matthias Koch
    @matkoch
    I was asking for the specific technique, how you generate a text that equals to the actual statement.
    Jake Ginnivan
    @JakeGinnivan
    Ahh, sorry. I thought it was about usage of the library
    We use the stack trace to get the line number of the caller
    Matthias Koch
    @matkoch
    When I spoke about rewriting, I was relating to IL rewriting, which seemed like the most reliable way.
    Yes I got it already =)
    Jake Ginnivan
    @JakeGinnivan
    Ok cool
    Matthias Koch
    @matkoch
    well, performance is not so important for test projects
    but you know .... :)
    Jake Ginnivan
    @JakeGinnivan
    Yeah, shouldly has the opinion better error messages are more useful than saving a few hundred ms total
    We use another technique internally which would be quicker
    for Should.Throw() - we support expressions, then we format the expression tree
    Matthias Koch
    @matkoch
    I guess you guys are interested in testing, so I would like to tell you about my test framework, if you don't mind :) It's orthogonal to yours indeed. Could be combined.
    Jake Ginnivan
    @JakeGinnivan
    Sure
    Matthias Koch
    @matkoch
    Jake Ginnivan
    @JakeGinnivan
    Have not seen it
    nice
    Matthias Koch
    @matkoch
    I'm not putting so much effort into promotion unfortunately...
    But I'm actively developing it for 2 years now
    almost three :))
    Jake Ginnivan
    @JakeGinnivan
    Nice, I know how that feels. I have been building GitVersion for about that same time too
    Have you seen BDDfy? Also another project based on it https://github.com/mwhelan/Specify - Looks like we share similar concepts, except yours is also a test running whereas BDDfy/specify fit within existing test libraries
    https://github.com/JakeGinnivan/ExpressionToString - is the expression tree formatter i talked about
    Matthias Koch
    @matkoch
    ahh... i don't like this language noise :DD
    no test discovery in visual studio or resharper?
    Jake Ginnivan
    @JakeGinnivan
    These are just libraries which sit inside other testing frameworks
    you can use with fixie, nunit, xunit or any others
    Matthias Koch
    @matkoch
    yes, but will never be usable in a big solution
    Jake Ginnivan
    @JakeGinnivan
    how so?
    Matthias Koch
    @matkoch
    or maybe i don't understand..... how are tests displayed in the runners?
    Jake Ginnivan
    @JakeGinnivan
    we output to console/trace/whatever the test framework will pickup and display
    Matthias Koch
    @matkoch
    that's something that should be added to the readme.md :)
    Jake Ginnivan
    @JakeGinnivan
    Possible :)
    Matthias Koch
    @matkoch
    if you don't have any means to browse through test structure, THEN it's not suitable for big solutions
    btw, do you know pendulum? :)
    Jake Ginnivan
    @JakeGinnivan
    Test structure you use same techniques as xunit/nunit/whatever. organise by class or folders/namespaces etc
    nope?
    Matthias Koch
    @matkoch
    noticed you're from Perth... they're also... pretty famous =D
    Jake Ginnivan
    @JakeGinnivan
    oh, band
    haha
    Matthias Koch
    @matkoch
    i will leave it here once again =) https://github.com/matkoch/TestFx hope to get some people to test it
    Reuven Y.
    @robi-y
    This message was deleted
    John-Philip Johansson
    @seriema
    I like the shouldly syntax a lot, but I'm wondering if there's a way to make them stand out a bit. When quickly scanning through test code it's hard to see what is the "assert" compared to "act". In JS and mocha the BDD syntax is: expect(myvar).to.be.null;
    The dot syntax isn't interesting, but the "expect()" is very helpful even if it can seem like unnecessary code.
    I guess one way would be a generic Expect() method that just returns the param. Has anyone experimented with or seen what I'm looking for?
    Jake Ginnivan
    @JakeGinnivan
    @seriema not sure there is much in that space. Assert. style libraries like xUnit assertions probably match what you want better.
    TBH I just sometimes use // Assert in my tests to separate it
    Peter
    @AnderssonPeter
    I have been looking at shouldy and it seems nice i just have one question, does this replace other unit test frameworks like mstest and xunit or does it just enhance them?
    Reuven Y.
    @robi-y
    @AnderssonPeter b)
    Jake Ginnivan
    @JakeGinnivan
    @AnderssonPeter it is an assertion library, it can be used with any unit test framework