Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Test-Driven Development with C++
  • Table Of Contents Toc
Test-Driven Development with C++

Test-Driven Development with C++

By : Abdul Wahid Tanner
4.5 (2)
close
close
Test-Driven Development with C++

Test-Driven Development with C++

4.5 (2)
By: Abdul Wahid Tanner

Overview of this book

Modern, standard C++ is all that is needed to create a small and practical testing framework that will improve the design of any project. This allows you to think about how the code will be used, which is the first step in designing intuitive interfaces. TDD is a modern balanced software development approach that helps to create maintainable applications, provide modularity in design, and write minimal code that drastically reduces defects. With the help of this book, you'll be able to continue adding value when designs need to change by ensuring that the changes don't break existing tests. In this book, you will use test-driven development (TDD) to gain practical skills by writing a simple testing framework and then using it to drive the design of a logging library. The book will help you enhance your software development skills with test cases. You'll understand how to design and implement test cases. The chapters will also show you how to utilize the TDD approach to be more productive in software development than attempting to code in large unstructured steps. By the end of this book, you'll have gained knowledge of TDD and testing and also built a working logging library with unique features not found in other libraries.
Table of Contents (21 chapters)
close
close
1
Part 1: Testing MVP
10
Part 2: Using TDD to Create a Logging Library
14
Part 3: Extending the TDD Library to Support the Growing Needs of the Logging Library

Test Setup and Teardown

Have you ever worked on a project where you needed to prepare your work area first? Once ready, you can finally do some work. Then, after a while, you need to clean up your area. Maybe you use the area for other things and can’t just leave your project sitting around or it would get in the way.

Sometimes, tests can be a lot like that. They might not take up table space, but sometimes they can require an environment setup or some other results to be ready before they can run. Maybe a test makes sure that some data can be deleted. It makes sense that the data should exist first. Should the test be responsible for creating the data that it is trying to delete? It would be better to wrap up the data creation inside its own function. But what if you need to test several different ways to delete the data? Should each test create the data? They could call the same setup function.

If multiple tests need to perform similar preparation and cleanup work, not...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Test-Driven Development with C++
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon