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

Configuring the API project


With the React project now configured to hit the real API, it's time to turn our attention to the .NET solution. In order to verify that everything is wired up correctly, you'll want to write a series of integration tests to ensure that the whole system is working properly.

Integration test project

Create a new xUnit Project called SpeakerMeet.Api.IntegrationTest within the existing solution. This will be where the .NET integration tests will be created. You may want to explore separating these out according to your preferences and/or team coding standards, but that can wait. For now, a single integration test project will do.

For our purposes, we'll be testing whether the system functions from API entry all the way to the database, and back. However, it's best to start small test individual integration points and grow from there.

Where to begin?

You could certainly start by creating a test that will call an API endpoint. In order to achieve this, an HTTP Request will...