Bogus VS Moq

Going forward, the secret to knowing were to find data is to read Bogus information in the readme file which goes into depth were to find paths to generate data. This is very important as you can clash with their classes e.g. you create a Person class and guess what, Bogus has a Person class. This is were knowing how to work with using statements and using statements with aliasing.

Code samples for Json.net which as of version 13.0.2 now supports DateOnly and TimeOnly. Three code samples are used to show interactions with Bogus and Microsoft.Data.SqlClient which is most likely used to work with json data.

In terms of generating test cases, I've come across this before: https://github.com/bchavez/Bogus

I used a .Net library a few years ago to create random text for a bunch of fake email bodies. It wasn't "lorem ipsum" type text, but full sentences and paragraphs. It would produce text that sounded like it came from a bullshit consulting handbook, or an intentionally obtuse technical description....things like, "Though vague in purpose the participant reality substituted reactional nature while in strongest thought vertices coincided with ...." and so on. I think it was somehow tied to Bogus but I can't seem to find it anywhere. Anyone able to help me out here?

Bogus Github Nuget: Install-Package Bogus -Version 33.1.1

Seems like a fun package but I prefer Bogus

I inserted 10M rows of fake data generated by Bogus into the table. You can download the dump here.

What is Bogus and Faker? They are libraries randomly to create a variety of dummy data such as human name, address, date and product/company name etc. = reduce our boring time of generating dummy records and have testing cases with multiple dummy values instead of our static ones.

MOQ https://github.com/moq/moq4

Moq

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 documentation | GitHub

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.)

This looks like the kind of thing Moq could handle with LINQ to Mocks.

Full code can be found here. More on Moq can be found here.

Moq

> edit: one more qualm, the Mockito equivalent for C#, NSubstitute, cannot mock a concrete class, only an interface.

I've never heard of NSubstitute (that doesn't mean it's bad), but most places I've worked at typically use Moq (https://github.com/moq/moq4) which does support interfaces and classes.

Have you tried Moq?