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

Speaker detail

Now that we have our speakers listing nicely, it would be nice to be able to view a bit more information about a specific speaker. Let's look at the tests involved in retrieving and viewing a speakers-detailed information.

Adding to the mock API Service

In the mock API, we need to add a call to get the details for a specific speaker. We can assume that the speaker has an ID field that we can use to gather that information. As usual, let's start our tests with a simple exists check. We will need to add a new describe inside the After Initialization describe for getting a speaker by ID.

describe('Get Speaker By Id', () => {
   it('exists', () => {
     // assert

To make this test pass, we need to add a method to the mock API.

getById() {

Now, we can write a test to verify the functionality we expect when a matching speaker cannot be found. The functionality we want in this case is for a SPEAKER_NOT_FOUND message to be shown...