Creating Your Own Fakes Instead of Using Mocking Libraries

[giscus[bot]]

Creating Your Own Fakes Instead of Using Mocking Libraries

With respect to the current topic around Moq, I want to showcase how you can easily roll out your own fakes so that you are not depending on a third party library.¨

https://steven-giesel.com/blogPost/2ad414c8-273f-4976-a9de-c95f0e791d51

[vertonghenb]

Nice article about Faking data, I've dedicated some slides to it in our C# course, "Fake it 'till you make it" using bogus.
https://hogent-web.github.io/csharp/chapters/06/slides/index.html#73

[toupswork]

There's something I've been wanting to try. Rather than implementing them with a class, I want to try creating an interface that inherits from the real interface and implements the methods now that interfaces allow this, then pass that into the class you're testing

[toupswork]

Yeah, but you can now set an upper limit and control how aggressive it is at collecting. I haven't read up on the details of the configuration options, but I know that you can tell it not to grow beyond a certain size and that it allows you to make it behave the way it does on a workstation. I was helping out another team a few months back and they were doing AWS stuff.. I even learned PostgreSQL and I think it's awesome, after being a MS fan boy my whole life and using mostly SQL. Now I am back on my team and we're building a React App with a .NET 8 API running in on-prem kubernetes. I liked working in the cloud and hope we get a project later on so I can go back to it because I learned so much. I was going to mention GoLang. It looks neat. I know that a lot of .NET shops moved to it because of the cold-start issue. It's a compiled language, which is cool, and it's one higher abstraction order above Rust. But when it comes to a general purpose language, .NET in my opinion is the best. I'm also a huge TypeScript fan. Hard to say which language I like more: TS or C#.

[linkdotnet]

I love the structural typing of TypeScript - and to that extent of Golang as well.
I wish I could use that (more often) in .NET.

A lot of things are somewhat duck typed in C# like foreach, await and using where you don’t necessarily need the interface - it just makes it painfully obvious what your intend is.

Postgresql is a beast. In the projects I work you mainly see MSSQL Server. While rock solid you can see how it tried to onboard features that Postgres has since ages.

[toupswork]

Agreed. There's something about TypeScript that makes me love it. Maybe cause the advanced stuff looks so cryptic, and I wanted a challenge. I don't know, but I love building components with TypeScript where as you start adding properties, the type inference flows out and you get all this cool auto completion support, and I can make it really hard to pass the wrong data into it. I hate the any keyword, though. So many people don't try to learn TS and as soon as they get stuck, they put in any.

[toupswork]

Yes, agreed on the duck typing. They need to stop that. Do you remember Global.aspx duck typing? yuck. And yea, PostgreSQL is a beast. It's so freaking powerful and eloquent.

[linkdotnet]

Oh the good old Global.asax
Yes it was weird. Weird conventions that didn’t really fit into .net at all.

I do agree - using any everywhere gives you the overhead of typescript but your still using JavaScript.
Sometimes big 3rd component libraries (in the angular space) don’t really type their API so it is really hard that it doesn’t bleed into your own code.
And sometimes even worse: they use the wrong type:)