Should testing for .net - the way Asserting *Should* be!
I just came here from https://up-for-grabs.net to help out with some open source projects, and shoudly is one we also use in our company. When coming here there were several issues open and tagge as jump-in, but most issues were already solved. If you are searching for people to contribute, I would be grateful if you could do some house keeping and close already implemented issues which are marked as Jump-in. This would decrease the amount of overhead from people willing to contribute but unwilling to sift through every issue to check whether it has been implemented
Hi guys, someone has information about release date?
Hello, I've been using Shouldly for some time now, but lately with my (dotnet core) projects the failure messages are not as good as before. The name of the variable is not put anymore in the message. for example for employee.FirstName.ShouldBe("John"); // fails --> message: "Dale" should be "John" but was not My question: is that on purpose or did I miss something? This is not in line with the documentation I think.
(it kinda diminishes my point when I try to convince people to use it :-) )
osama arif lone
hey guys i am doing my masters in Pakistan does anybody know of a job or an internship that i can do remotly from Karachi ? Any help would be greatly appreciated.
Hi, I am a .NET developer, working mostly on commercial apps, and I would also like to contribute to open source. I think shouldly is very nice project, I like the assertion syntax you invented. Can you recommend any issue which I could help you with? It would be my first open source PR.
is anyone familiar with the subsection of the Shouldly src that has to do with formatting the exception string messages and embedding the appropriate values in a context-appropriate way? And particularly with grabbing stack trace manipulation
Someone here to answer a question about the project?
Hi. I have an enhancement for issue 482, but don't have permission to push to a feature branch. Could I please have access so I can issue a PR? Thanks. (shouldly/shouldly#482)
Nevermind. I forked and submitted a PR from there.
Hello Guys, am a software developer with NHS Wales Informatics and we doing lots of sturfs with unit testing. I am currently interested in contributing to this projects.
Hello, I am interested in learning more about this project.
The process is to wait until the sole maintainer has time to look at it.
This is an open source project and I know people contribute on their free time which is hard to get these days. I was wondering if the maintainer has considered pulling in long term contributors to help out with the PR merges. This would enable faster resolution of issues.
I don't know, but it's a question I asked in one of the issues. Maybe it's worth starting a discussion issue about it?
@JosephWoodward@JakeGinnivan seems shouldly supports some really old dotnet versions. eg 4.5.1 was released 10/2013 and support ended in 2016. just wondering is you have considered dropping some of those in v4?
hi all, anyone experience where Shouldly suddenly doesnt know how to find a diff tool. It's been working perfectly fine in visual studio, then suddenly stops working for no visible reason? the tests still work, as in they verify or fail, just doesnt launch the default visual studio diff tool anymore.
Hi all. I have a little fix for FindMethodUsingAttribute which allows it to correctly discover async test methods. How do I go about getting permission to push the branch and submit a PR?
Hello, So i'm looking at a test method called "ShouldBeSameAs" for comparing objects, however i can't find any documentation on this anywhere? anyone able to assist?
@benjaminroesdal ShouldBeSameAs compares whether two references point to the same object instance. It's a ReferenceEquals test.
Hi there, is the TypeInitializationException in v4 with ShouldMatchApproved a known issue? About to raise a GH issue for it :)
Hi - im using the lates version 4.0.3 i have IEquatable<class> implemented when i test i use expectedValue.ShouldBe(actualValue) i know that thay dont match becuse thay have diffrent values but shouldly wont output any of that information. Do anyone know way ?
or wont it list out the actual diffs of property values ? now it only shows the hashcode
seams to work better when u go directly on the properties, would be nice if it worked directly on the object tho but now i get more info at least