Bogus VS xUnit

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.

I was trying to think of an example of where C# attributes might be used in every day life and then it dawned on me: unit testing! If you have ever used a unit test framework such as MSTest, NUnit or xUnit, you will have used attributes in C# to define the classes and methods that you would like the test framework to execute. This is just one example of how you can use attributes to assign metadata to elements of your code.

Because I struggled with the initial tests written using MSTest, I converted all the tests to xUnit – some of this was out of sheer comfort with xUnit over MSTest, but also because its OSS product under the .NET Foundation – and I like supporting those.

I didn't want to create "yet another test runner," but I couldn't get any of the existing ones to do everything I needed. It's fairly well known that you can't run or debug xunit tests in a Godot game unless you're using Rider, and since I'm a die-hard VSCode user, I didn't want to make the switch. XUnit also runs tests in parallel by default, which isn't usually what I want in a game-like environment, so it just felt like a poor fit overall.

The setup here is really minimal, just create a new test project. I'll be using xUnit but NUnit should be fine too.

xUnit

If you're using xUnit for your tests, you can implement the IAsyncLifetime interface it helpfully provides for you.

The projects are all .NET 6 applications with nullable references types and implicit usings enabled. The unit testing projects use Xunit out of the box. There are also support files such as .gitignore, .editorconfig, etc.

The testing framework that I chose is XUnit. The first reason is that it is trendy compared to another test framework such as NUnits. I created test methods stub from the existing code by Create Unit Tests command. To use it with Xunit, I have to implement the XUnit.net.TestGenerator extension to my project.

Tests is a xunit project to unit test your domain logic.