Book Image

Clean Code in C#

By : Jason Alls
Book Image

Clean Code in C#

By: Jason Alls

Overview of this book

Traditionally associated with developing Windows desktop applications and games, C# is now used in a wide variety of domains, such as web and cloud apps, and has become increasingly popular for mobile development. Despite its extensive coding features, professionals experience problems related to efficiency, scalability, and maintainability because of bad code. Clean Code in C# will help you identify these problems and solve them using coding best practices. The book starts with a comparison of good and bad code, helping you understand the importance of coding standards, principles, and methodologies. You’ll then get to grips with code reviews and their role in improving your code while ensuring that you adhere to industry-recognized coding standards. This C# book covers unit testing, delves into test-driven development, and addresses cross-cutting concerns. You’ll explore good programming practices for objects, data structures, exception handling, and other aspects of writing C# computer programs. Once you’ve studied API design and discovered tools for improving code quality, you’ll look at examples of bad code and understand which coding practices you should avoid. By the end of this clean code book, you’ll have the developed skills you need in order to apply industry-approved coding practices to write clean, readable, extendable, and maintainable C# code.
Table of Contents (17 chapters)
Unit Testing

Previously, we looked at exception handling, how to implement it properly, and how this can be useful to the customer and the programmer when issues occur. In this chapter, we will look at how programmers can implement their own quality assurance (QA) to provide quality code that is robust and less likely to generate exceptions in production.

We start by looking at why we should test our own code, and what makes a good test. We then look at several testing tools that are available to C# programmers. Then, we move on to the three pillars of unit testing that are Fail, Pass, and Refactor. Finally, we look at redundant unit tests and why they should be removed.

In this chapter, we will cover the following topics:

  • Understanding the reasons for a good test
  • Understanding the testing tools
  • TDD methodology practice – fail, pass, and refactor
  • Removing...