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

End-to-end integration tests


The last subject we will discuss in this chapter is end-to-end integration tests. These tests involve actually calling the server and checking the real responses.

Benefits

So, what are the benefits of testing the actual client-server connection? The most valuable benefit is that you know your application will work in the deployed environment. Sometimes an application will get deployed and not work because a network or database connection was incorrectly configured and that will wreak havoc on a deployment.

Additionally, this will help to verify the system is working properly. A series of smoke tests could be employed after a deployment to ensure the deployment was successful.

Detriments

E2E tests are usually skipped for one of two reasons. The first reason is that they are difficult to write. You have a lot of extra setup to get these tests to run, including a completely different test runner than what you normally use for unit testing. If not a different runner,...