Click here to Skip to main content
14,640,725 members
Articles » General Reading » CodeProject FAQs » General » Revisions



Have Less Production Issues with the Help of xUnit

Rate this:
4.53 (4 votes)
Please Sign up or sign in to vote.
4.53 (4 votes)
24 May 2020CPOL
By using xUnit the right way, your logging can be improved and production problems can be solved easily or even prevented
Considering the way many tests with xUnit are written, two things need to be improved: the tests need to be more realistic and should prevent having limited logging. Making tests more realistic will make production problems less likely, Moreover, testing what has been logged prevents the problem of having to limited logging details to solve a production issue once it occurs. This article explains how to prevent such problems in your xUnit tests.



Compare Revision Minor Date Status Editor


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Daan Acohen
Software Developer (Senior)
Netherlands Netherlands
I am a self-employed software engineer working on .NET Core. I love TDD.

Comments and Discussions