Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Clean Code with C#
  • Table Of Contents Toc
  • Feedback & Rating feedback
Clean Code with C#

Clean Code with C#

By : Jason Alls
4.5 (2)
close
close
Clean Code with C#

Clean Code with C#

4.5 (2)
By: Jason Alls

Overview of this book

Traditionally associated with Windows desktop applications and game development, C# has expanded into web, cloud, and mobile development. However, despite its extensive coding features, professionals often encounter issues with efficiency, scalability, and maintainability due to poor code. Clean Code in C# guides you in identifying and resolving these problems using coding best practices. This book starts by comparing good and bad code to emphasize the importance of coding standards, principles, and methodologies. It then covers code reviews, unit testing, and test-driven development, and addresses cross-cutting concerns. As you advance through the chapters, you’ll discover programming best practices for objects, data structures, exception handling, and other aspects of writing C# computer programs. You’ll also explore API design and code quality enhancement tools, while studying examples of poor coding practices to understand what to avoid. By the end of this clean code book, you’ll have the developed the skills needed to apply industry-approved coding practices to write clean, readable, extendable, and maintainable C# code.
Table of Contents (18 chapters)
close
close

Chapter 6

  1. Testing frameworks for C#:
    • NUnit: Widely used, supports parameterized tests, lacks some advanced features.
    • xUnit: Similar to NUnit but newer, promotes more modern testing practices, extensible.
    • MSTest: Integrated with Visual Studio, easy setup, but historically considered less flexible.
  2. Best practices for unit tests in C#:
    • Isolation: Tests should be independent, not relying on the OOE.
    • Readability: Clearly express the intent of the test and use meaningful names.
    • Speed: Tests should run quickly, enabling frequent execution.
    • Maintainability: Regularly update tests to reflect changes in the code base.
  3. Mocking data in unit tests:
    • Use mocking frameworks such as Moq or NSubstitute to create fake objects.
    • Mock external dependencies by providing controlled responses to method calls.
    • Focus on testing specific code units in isolation without invoking actual external services.
  4. Code coverage analysis in Visual Studio 2022:
    • Code coverage: Measures the percentage of code lines executed...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY