FsCheck
Stryker.NET
Our great sponsors
FsCheck | Stryker.NET | |
---|---|---|
11 | 14 | |
1,132 | 1,707 | |
0.9% | 1.5% | |
8.1 | 9.4 | |
7 days ago | 2 days ago | |
F# | C# | |
BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
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/
Stryker.NET
-
Stryker.NET alternatives - Testura.Mutation, visualmutator, fettle, and Faultify
5 projects | 9 Jun 2023
-
Do you guys mock everything in your Unit Tests?
Bogus - For creating fake data Verify - Snapshot testing for .NET MELT - For testing ILogger usage Stryker - Mutation Testing for .NET TestContainers - run docker programmatically in integration tests
-
Scope of unit testing (karma/Jas) Boss wants unreasonable testing?
This is called mutation testing btw.
-
Don't target 100% coverage
Let's try it on our small example using Stryker.
- PhD'ers, what are you working on? What CS topics excite you?
-
Killing mutants to improve your tests
There are tools that do this automatically, stryker[2] is one of them. When you run stryker, it will create many mutant versions of your production code, and run your tests for each mutant (that's how mutations are called in stryker's' documentation) version of the code. If your tests fail then the mutant is killed. If your tests passed, the mutant survived. Let's have a look at the the result of runnning stryker against reffects-store's code:
-
Not sure if popular opinion: Greenfield projects should have 100% test coverage.
Mutation testing is pretty solid. Better than code coverage for sure. Using Stryker personally.
-
Seriously what are they and why does everyone hate them?
A mutation testing tool (like Stryker) runs your unit tests to verify they all pass then makes a small change (mutation) to your code and reruns the tests. At least one test should fail because the modified code should behave differently.
-
Relesed v1.0.0 of my pet javasscript project yesterday after hitting 100% coverage- a gesture detection library
I haven't tried it yet, but last time I researched it, this is the library that looked most promising: https://stryker-mutator.io/
-
Mutation Testing in NodeJS
Website: https://stryker-mutator.io/
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.
xUnit - xUnit.net is a free, open source, community-focused unit testing tool for .NET.
Bogus - :card_index: A simple fake data generator for C#, F#, and VB.NET. Based on and ported from the famed faker.js.
sharpfuzz - AFL-based fuzz testing for .NET
Expecto - A smooth testing lib for F#. APIs made for humans! Strong testing methodologies for everyone!
Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]
MSTest - MSTest framework and adapter
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.
hedgehog - Release with confidence, state-of-the-art property testing for Haskell.
should - Should Assertion Library