Blazor Unit Testing Tutorial – How to Master with Practical Examples in C#
Unit test your Blazor project! Improve code quality and catch bugs early with improved test coverage. Check out this Blazor unit testing tutorial now!
Unit test your Blazor project! Improve code quality and catch bugs early with improved test coverage. Check out this Blazor unit testing tutorial now!
In this article, you'll explore the importance of Blazor unit testing and learn about Blazor unit testing best practices. Get started with Blazor today!
Interested in unit testing in C#? Let's look at xUnit and Moq for unit testing! We'll explore mocking external dependencies and the role of these in unit tests.
Unit tests or functional tests? What's the difference and which ones should you be using? Find out in this super quick compare-and-contrast!
xUnit tests not running with .NET standard project settings? Here's a super quick solution to get you back up and running so you can test away!
ProjectXyz Alright, I'll admit it... Even for a placeholder name on a side project it's pretty terrible, right? Well, my apologies. So, if you made it to this post you might be wondering what ProjectXyz is and why I started it up. From a high level, I started working on ProjectXyz so that I could have a hobby programming project to tinker with and I figured I'd blog about my adventures in bringing it all together. I plan on making this a mini-series documenting some of the things I'm learning or experimenting with, so this will serve as the intro to the series. Before we get too far, here's the link to the GitHub site: https://github.com/ncosentino/ProjectXyz Why Have a Side Project? Here's the main thing I want to talk about in part 1 of this series: Why should you have a…
Refactoring: Some Background If you're a seasoned programmer you know all about refactoring. If you're relatively new to programming, you probably have heard of refactoring but don't have that much experience actually doing it. After all, it's easier to just rewrite things from scratch instead of trying to make a huge design change part way through, right? In any mature software project, it's often the case where you'll get to a point where your code base in its current state cannot properly sustain large changes going forward. It's not really anyone's fault--it's totally natural. It's impossible to plan absolutely everything that comes up, so it's probable that at some point at least part of your software project will face refactoring. In my real life example, I was tasked with refactoring a software project that has a single owner. I'm close…