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
What to Know Before Getting Started
Files and Directories
Advanced C# and .NET Features

Moving forward 

Once the legacy system has been sufficiently refactored and a comprehensive suite of tests has been added, you may begin to think of the application as non-legacy, current, or a present-day system. It should now be trivial to add new features and squash any newly discovered defects. From this point forward, any new feature requested should be easily added with the confidence that other parts of the system will not be negatively affected.

The legacy application is no longer legacy. With a comprehensive suite of tests, you are now safe to proceed in Test-Driven Development fashion and write tests as every new feature is added. Remember to keep your tests as clean and well-refactored as any part of the production system.

Taking the GetPercent example above, how might you modify this in order to return two decimal places? Why, by writing new tests, of course! Start by creating a test to return two decimal places based on the input value.

Your test might look something like this...