Well in general, you'd want to figure out what kind of things you'd want to test for. I think these were all listed in the textbook somewhere, but off the top of my head, you test for things like:
Functionality - do the required features of the solution function correctly
Appearance - is it neat, logically ordered, aesthetically pleasing etc.
Usability - is the solution easy to use
Accuracy/Reliability - do you get the correct results out all the time
There were a few other types of things you test for, but I can't really remember at the moment.
You can go back to the work you did in design and take a look at what you stated about what the website should be like at that stage and then compare it to how it actually turned out.
For specific examples, it's probably best to keep those above things in mind and then take a look at the prototype website that you've put together. The columns of the testing table are something like: Test Description, Test Data, Expected Result, Actual Results, Corrections (if needed), so once you decide on the first column entries, the rest of it is simple.