Purpose:

• Defines a set of tests to run sequentially:
  Each test is the combination of a test driver, that implements an ITest interface, and the production code it tests. We want to chain multiple tests to be executed in sequence. We expect to save that sequence and add additional tests later, as the development of the code continues.
• Provides exception-safe test execution:
  Each test is to be run inside a try-catch block, used to handle exceptions thrown by the test. A thrown exception does not stop testing of the sequence. Instead, it results in a fail result for the test that threw the exception. Also, we want to insert each test into a single try-catch block so we don't have to litter our test drivers with a lot of exception handling. We will discuss how to do that in class.
• Supports logging test results:
  The results of testing need to be reported to the person executing the tests. We will do that with a Logger class that supports concurrently writing results into one or more output streams, e.g., to the console and a file or database for storage.

Requirements:

1. Shall use Visual Studio 2017 and its C++ Windows Console Projects, as provided in the ECS computer labs.
2. Shall use the standard streams libraries for all I/O and operators new and delete for memory management.
3. (2) Shall provide an ITest interface that all tests must implement.
4. (4) Shall provide a container that provides references to a sequence of one or more test instances.
5. (2) Shall provide a function that extracts callable test objects from the container and executes them within a single try-catch block.
6. (1) Shall provide a logging facility that logs test success or failure, and test identification messages that provide information to the user during test execution.
7. (1) The logger shall provide for writing a test message on the console, and into a file for persistant storage, with a single write³ statement.
8. (1) Each message shall provide information about the test, author, and time-date of execution. This information should be as compact as practical while still providing useful information.
9. (4) Shall develop tests for each class in the CodeUtilities package, and execute them in your Single-User TestHarness.
10. (4) Shall include an automated unit test suite that demonstrates that you meet all the functional requirements above. Note that this is just a set of tests that is used to test the TestHarness packages.
11. (1) Each test shall provide comments in the test driver code that cite what each part of the test does, and the expected results.

1. In C++, a package consists of two source code files, a header (.h) and an implementation (.cpp), that contain:
   • prologue, providing a name, brief descriptive phrase, author information, and environment information
   • description of the package's responsiblities and required files
   • maintenance history
   • class declarations
   • class method definitions
   • a main function that implements construction tests for all the defined code
   The Blocking Queue CodeSnap is a good example.
2. A software baseline is the set of all code considered to be part of the current system, excluding experimental code that individual developers are working on.
3. You may name the writing method however you wish. The intent is that there is some way of registering streams for output so that a write goes to every registered stream.

What you need to know:

1. Basics of the C++ language: C++ Reference
2. How to implement a simple class hierarchy. This will be covered briefly in lecture #2 and in more detail later.
3. The standard Containers.
4. How to use Visual Studio. We will discuss this in one of the Help Sessions.