Testing the List class and Beyond

Please note, until further notice pass instances of the ListT class by reference

Please note, until further notice do not copy from one ListT class to another.

What are some things we should test

Does the constructor work?
- How will we do this?

Does the destructor work?

This is harder.
At one point you had to read the code and assure that it worked.
- Or run it for a long time and see the program grow without bound.
valgrind is a useful linux tool for this.
valgrind progname

Should report

==8958== HEAP SUMMARY:
==8958==     in use at exit: 0 bytes in 0 blocks
==8958==   total heap usage: 108 allocs, 108 frees, 75,424 bytes allocated
==8958==
==8958== All heap blocks were freed -- no leaks are possible
==8958==
==8958== For lists of detected and suppressed errors, rerun with: -s
==8958== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Insert/Delete
- Make sure insert inserts in order.
- I built a function to test this.
- Do a number of special cases
  - Insert at the beginning of an empty list and a list with items in it.
  - Insert at the end of a list with items in it
  - Insert into the middle of a list with more than 1 item.
- Delete: do the same.
I have automated this somewhat.
- Look at listTest.cpp