Our great sponsors
FsCheck | NUnit | |
---|---|---|
11 | 26 | |
1,135 | 2,460 | |
1.1% | 2.8% | |
8.0 | 9.1 | |
18 days ago | 6 days ago | |
F# | C# | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
FsCheck
-
Property-based tests and clean architecture are perfect fit
As you can see from the imports statement we're relying on FsCheck to generate some random values for us.
-
When writing unit tests, what exactly am I looking for?
C# - FsCheck
-
Is there a tool that could be used to generate fake unit test cases automatically for code coverage? (read description before downvoting)
https://fscheck.github.io/FsCheck/ can hopefully generate random inputs automatically or with low effort for many methods to get your code coverage up. You don’t even need to write real tests right now, just call the methods with the random inputs and check they don’t fail.
-
Does anyone know of a good place to learn and practice some F# preferably F# 6 to be able to use Task.
Try using F# for tests. It has some great libraries like FsCheck (https://fscheck.github.io/FsCheck/).
-
Typesafe F# configuration binding
At Symbolica we're building a symbolic execution service that explores every reachable state of a user's program and verifies assertions at each of these states to check that the program is correct. By default it will check for common undefined behaviours, such as out-of-bounds memory reads or divide by zero, but it can also be used with custom, application specific, assertions too just like the kind you'd write in a unit test. Seen from this perspective it's kind of like FsCheck (or Haskell's QuickCheck or Python's Hypothesis), but much more exhaustive and without the randomness.
-
Does anybody know a simple algorithm for generating unit tests given a function's code?
Maybe something like QuickCheck, a quick search gave me this library for .NET https://github.com/fscheck/FsCheck
-
When do you consider your unit tests be "enough"?
Because of the above I've generally been using tools like Stryker.NET and FsCheck to augment my testing suite. I'm still doing unit testing to find the more obvious "I haven't had my coffee, let's make sure I'm doing what I think I'm doing" bugs. I'm just using things like mutation testing, property testing, fuzzing, etc. to find the deeper issues in my code. There's a ton of libraries out there, including one that I've built for myself to help with testing but FsCheck and Stryker are just beautiful. And if you're interested in fuzzing, SharpFuzz is a great option. But that one isn't quite as easy of an on ramp compared to the other two that I mentioned.
-
What are you working on? (2021-06)
Looks cool. Is there a reason why you didn't use FsCheck or Hedgehog? They're built to generate random data for testing, and can return the seed if a test fails so you can rerun the test with the exact same data once you figure out what the problem is - which is useful if the failure condition is rare.
-
Mutation Testing
Haskell has QuickCheck and Hedgehog, and dotnet has both as well. F# is favored, but there's C# interop.
-
How Good Are Your .NET Tests? Test Your Tests With Stryker Mutator
Side note, if you are thinking about testing in general, might be interested in property based testing. See for example https://fscheck.github.io/FsCheck/
NUnit
-
CI/CD Pipeline Using GitHub Actions: Automate Software Delivery
.NET / xUnit / NUnit / MSTest
-
Fluent Assertions: Fluently Assert the Result of .NET Tests
This library extends the traditional assertions provided by frameworks like MSTest, NUnit, or XUnit by offering a more extensive set of extension methods. Fluent Assertions supports a wide range of types like collections, strings, and objects and even allows for more advanced assertions like throwing exceptions.
-
TDD vs BDD - A Detailed Guide
Next, you need to install a testing framework that will be used for performing unit testing in your project. Several testing frameworks are available depending on the programming language used to create an application. For example, JUnit is commonly used for Java apps, pytest for Python apps, NUnit for .NET apps, Jest for JavaScript apps, and so on. We’ll use the Jest framework for this tutorial since we are using JavaScript.
-
Setting up a simple testing project with C#
At this point you're going to see a familiar screen asking you to select a project. Here we're looking for a test project. By default, Visual Studio gives you access to 3 different testing frameworks based on your choice of project. These are MSTest, XUnit and NUnit. Ultimately, all 3 of these testing accomplish the same thing, and I've worked with all of them at various points in my career. The difference is mainly in exact syntax and documentation. Although, it's generally considered that MSTest is a little "older" than NUnit or XUnit, so I tend to see it less now. For the purposes of this demo, I'm going to go with NUnit:
-
Test-Driven Development
Use a testing framework: Utilize a testing framework like NUnit, xUnit, or MSTest to create, organize, and run your tests. These frameworks provide a consistent way to write tests, generate test reports, and integrate with continuous integration tools.
-
Debugging extension for test library
So I wrote extension attribute for Nunit, the opposite of how the retry attribute works.
- 2023 Development Tool Map
-
Unlock the Power of Unit Testing: A Beginner’s Guide to Quality Software Development
This is a basic example of how to create an NUnit unit test for a simple API in a controller with C#. You can find more information and resources on the NUnit website and in the NUnit documentation.
-
Commemorating Charlie Poole's Contributions to the NUnit Project
Has #NUnit helped you, your career, or your organization? We'd love for you to tell that story here, to celebrate Charlie: https://github.com/nunit/nunit/discussions/4283
After over TWENTY years leading the NUnit project, Charlie is stepping back.
Has NUnit helped you, your career, or your organization? We'd love to hear about it at https://github.com/nunit/nunit/discussions/4283.
> To attempt to quantify Charlie’s contributions to NUnit is a daunting task. He was the lead of NUnit across at least 207 releases in 37 different repositories, authoring 4,898 commits across them. He participated in 2,990 issues, 1,305 PRs, and impacted 6,992,983 lines of code. And those are only the ones we can easily find; our numbers are sourced from after NUnit moved the project to GitHub in 2011, which means there are at least 9 additional years of work not quantified above.
I think of Charlie as one of the ".NET OSS OGs". I'd love to see him celebrated.
What are some alternatives?
AutoFixture - AutoFixture is an open source library for .NET designed to minimize the 'Arrange' phase of your unit tests in order to maximize maintainability. Its primary goal is to allow developers to focus on what is being tested rather than how to setup the test scenario, by making it easier to create object graphs containing test data.
Fluent Assertions - A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit tests. Targets .NET Framework 4.7, as well as .NET Core 2.1, .NET Core 3.0, .NET 6, .NET Standard 2.0 and 2.1. Supports the unit test frameworks MSTest2, NUnit3, XUnit2, MSpec, and NSpec3.
Bogus - :card_index: A simple fake data generator for C#, F#, and VB.NET. Based on and ported from the famed faker.js.
NSubstitute - A friendly substitute for .NET mocking libraries.
Expecto - A smooth testing lib for F#. APIs made for humans! Strong testing methodologies for everyone!
xUnit - xUnit.net is a free, open source, community-focused unit testing tool for .NET.
sharpfuzz - AFL-based fuzz testing for .NET
Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]
Shouldly - Should testing for .NET—the way assertions should be!
hedgehog - Release with confidence, state-of-the-art property testing for Haskell.
coverlet - Cross platform code coverage for .NET [Moved to: https://github.com/coverlet-coverage/coverlet]