Gearing Up for Testing
A big difference between this assignment and previous assignments is that you will be writing your own tests!
So you need to understand what good tests are, and what is and is not allowed when you are doing testing.
Our Guidance on Writing Tests
Get started by reading our help page about testing:
The information in this page applies to both this assignment and to all subsequent CS 70 assignments. It has important rules and guidance on how to construct your tests. Read it now. (We'll also ask you questions about it on the written homework.)
Document the Interface
As you can see, to write good tests, it will be really important that you have a clear understanding about what each function you will implement promises and what it doesn't promise. One effective way to develop such an understanding is to do the work of writing documentation for each function. Such documentation typically takes the form of interface comments: specially-formatted comments, found alongside each function declaration, which describe what that function does. In the past, we have provided these interface comments for you. But this time around, we've provided code in intlist.hpp that lacks documentation, and it will be your job to add interface comments to all of the member functions of the IntList class in intlist.hpp.
Before you begin, you should take a moment to familiarize yourself with the expected format of interface comments by reading the "Interface Comments" section in our commenting help page (if you have not done so already):
As you write your interface comments, you should be referring to the IntList specifications to double check that the descriptions you are writing are complete and accurate:
Although you should try to be brief in your descriptions, you should include any usage rules that apply in \warning specifications for the functions.
Hint: Focus On intlist.hpp
In this part, you're focused on intlist.hpp. There are various other files you'll need to work on, but you can ignore them for now.
(When logged in, completion status appears here.)