Book Image

Advanced C++

By : Gazihan Alankus, Olena Lizina, Rakesh Mane, Vivek Nagarajan, Brian Price
5 (1)
Book Image

Advanced C++

5 (1)
By: Gazihan Alankus, Olena Lizina, Rakesh Mane, Vivek Nagarajan, Brian Price

Overview of this book

C++ is one of the most widely used programming languages and is applied in a variety of domains, right from gaming to graphical user interface (GUI) programming and even operating systems. If you're looking to expand your career opportunities, mastering the advanced features of C++ is key. The book begins with advanced C++ concepts by helping you decipher the sophisticated C++ type system and understand how various stages of compilation convert source code to object code. You'll then learn how to recognize the tools that need to be used in order to control the flow of execution, capture data, and pass data around. By creating small models, you'll even discover how to use advanced lambdas and captures and express common API design patterns in C++. As you cover later chapters, you'll explore ways to optimize your code by learning about memory alignment, cache access, and the time a program takes to run. The concluding chapter will help you to maximize performance by understanding modern CPU branch prediction and how to make your code cache-friendly. By the end of this book, you'll have developed programming skills that will set you apart from other C++ programmers.
Table of Contents (11 chapters)
7
6. Streams and I/O

Unit Testing and Mock Testing

When a developer starts writing code, they need to ensure it is tested correctly at the unit level. It may happen that the boundary conditions are missed, and the code may break when it runs on the client's site. To avoid this situation, generally, it is a good idea to do unit testing for the code. Unit testing is testing that's performed at the unit level or the base level of the code where a developer can test their code in an isolated environment, assuming the required setup has been fulfilled to run a feature of the code. Generally, it is good practice to break down modules into small functions and test each function separately.

For example, suppose part of the functionality is to read the configuration file and get the environment set up with the parameters from the configuration file. We can create a dedicated function to write this functionality. So, to test this function, we can create a set of unit test cases that will check various combinations...