Book Image

Improving your C# Skills

By : Ovais Mehboob Ahmed Khan, John Callaway, Clayton Hunt, Rod Stephens
Book Image

Improving your C# Skills

By: Ovais Mehboob Ahmed Khan, John Callaway, Clayton Hunt, Rod Stephens

Overview of this book

This Learning Path shows you how to create high performing applications and solve programming challenges using a wide range of C# features. You’ll begin by learning how to identify the bottlenecks in writing programs, highlight common performance pitfalls, and apply strategies to detect and resolve these issues early. You'll also study the importance of micro-services architecture for building fast applications and implementing resiliency and security in .NET Core. Then, you'll study the importance of defining and testing boundaries, abstracting away third-party code, and working with different types of test double, such as spies, mocks, and fakes. In addition to describing programming trade-offs, this Learning Path will also help you build a useful toolkit of techniques, including value caching, statistical analysis, and geometric algorithms. This Learning Path includes content from the following Packt products: • C# 7 and .NET Core 2.0 High Performance by Ovais Mehboob Ahmed Khan • Practical Test-Driven Development using C# 7 by John Callaway, Clayton Hunt • The Modern C# Challenge by Rod Stephens
Table of Contents (26 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
8
What to Know Before Getting Started
17
Files and Directories
18
Advanced C# and .NET Features
Index

Issues that prevent adding tests 


Deadlines are tight. The scope is ever changing. We just don't have time to write tests. It's more important to get functionality out the door. We've all been there. Whatever the case may be, sometimes you will find yourself working on a project that was not written with testing in mind.

Note

There never seems to be enough time to do it right, but there's always time to do it over.

So, what are the issues you might face that would prevent you from adding tests to a legacy application?

When a system wasn't written with testing in mind, it can be quite difficult to go back and add tests at a later date. Classes with concrete dependencies and tight coupling make software applications difficult to test. Things such as large classes and functions, Law of Demeter violations, global state, and static methods can also make for a system that can be very difficult to test.

Much like building a house by starting with a shaky foundation, untestable code begets untestable...