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

The plan

Now that our testing config has been updated and is working correctly, we can begin thinking about test-driving our first feature.

In earlier chapters, we discussed where to start testing and decided that if possible an inside-out approach is preferred. To keep with that approach, we want to determine the different parts of our React app so that we can target the purest business logic we can.

Right off the bat, regardless of any other architectural choices, we can identify the React component and a service representing communication with our data source. We are planning to use Redux in this app so that makes up the missing piece and connects our component with our data.

Which one of these is the business logic though? Out of those base options, what would we even test? Let's examine each one a little more closely and see what we could test that would be considered a unit test.

Considering the React component

Generally, we want to avoid unit-testing third-party libraries. So, let's separate...