Bogus
Moq
Our great sponsors
Bogus | Moq | |
---|---|---|
27 | 26 | |
8,261 | 5,215 | |
- | - | |
8.3 | 6.6 | |
7 days ago | 10 months ago | |
C# | C# | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
Bogus
-
Bogus custom Dataset
Bogus NuGet package is fake data generator which can be helpful for populating tables in a database and testing purposes. If a database is not used and Bogus populates list of data each time an application runs, the data is random, never the same. Also, the random data generated by Bogus may not meet a developer’s requirements.
-
C# User-defined explicit and implicit conversion operators
A list is populated with NuGet package Bogus.
-
Windows form move items up/down in ListView and more
Other project either mocked data using NuGet package Bogus or a json file.
-
Should I give a copy of the database to the developer
That reminds me of Bogus which also generates dummy data that I've been using for sometime now.
-
Best practices for organising Mock Data & Repositories in Testing
To do all this you need test though...and that's where ]Bogus](https://github.com/bchavez/Bogus) and Auto Bogus come in handy. They both generate semi random test data that you can use to populate whatever method you've decided to use. You can setup rules so for specific fields, they have built in generators for common things like names and addresses. Auto Bogus can be used to populate large/complicated objects with data automatically (it can be slow if you don't use .WithRecursiveDepth() or.WithTreeDepth() )
-
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
-
WinForms communicate between forms
To keep things interesting Bogus library is used to create a Person instance.
- bchavez/Bogus: fake data generator for C#
-
The art of Deconstructing
Usage with mocked data using Bogus NuGet package.
-
Nuget Packages in Class Libraries
I would say the issue is either a general issue with how Revit loads the addin, or maybe an issue with conflicts in your transitive dependencies. You can do some tests to try to figure out which. Try making a barebones Revit addin that uses a library that has no dependencies and isn't likely to be used in Revit. I'd suggest Bogus, you can use it generate a few pieces of test data and log them/display in the UI/whatever. If that works, then it would appear that Revit is fine with your addin having dependencies (which I would expect).
Moq
-
Setting up a simple testing project with C#
In terms of mocking there are several frameworks you can use, but I've mainly relied on Moq and NSubstitute. Within this demo, I'm going to use NSubstitute as I've found it a little easier to use.
-
What if writing tests was a joyful experience
Or you just run into bullshit like https://github.com/Moq/moq4/issues/173
- Moq.NET Mocking framework [C#]
-
Dependency injection
Now to the real benefit of DI: If you are testing a method in your application that calls the ReservationRepository.GetReservation() method, you can use a library like Moq to simply "mock" a class that uses the IReservationRepository interface and define the return result of the GetReservation() method. Pass the mocked class into the constructor of the class you are testing.
-
Usefully links for DotNet Backend Developers
MOQ https://github.com/moq/moq4
-
I need a C# crash course for experienced developers
Moq
-
A Tale of 2 Codebases (Part 2 of 4): Testability
Both projects use similar testing infrastructure. I write unit tests in C# using XUnit.net. I frequently use mock objects in testing, and MOQ is my tool of choice. I utilize continuous testing and coverage analysis through Rider. I do not have specific objectives for code coverage. When writing complicated algorithms, I frequently shoot for 100% coverage of the algorithm. I test simple properties inconsistently, and frequently do not test guard clauses.
-
Moq vs NSubstitute: syntax cheat sheet
🔗 Moq documentation | GitHub
-
What's your go-to unit testing tool?
But the reality is that I don't really write my tests with it. Toss on the MSTest attributes as needed of course. But all the testing code itself is FluentAssertions with a bit of Moq. (Though I find rarely need to use Moq/mocking anymore -- scandalous, I know.)
-
How YOU can Learn Mock testing in .NET Core and C# with Moq
Moq tutorial
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.
FakeItEasy - The easy mocking library for .NET
faker-cs - C# port of the Ruby Faker gem (http://faker.rubyforge.org/)
NSubstitute - A friendly substitute for .NET mocking libraries.
NBuilder - Rapid generation of test objects in .NET
AutoMoq - Auto mocking provider for Moq.
GenFu - GenFu is a library you can use to generate realistic test data. It is composed of several property fillers that can populate commonly named properties through reflection using an internal database of values or randomly created data. You can override any of the fillers, give GenFu hints on how to fill them.
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.
xUnit - xUnit.net is a free, open source, community-focused unit testing tool for .NET.