Comments on Lab 8 Test Plan Document
1	You need to be systematic about the order of your tests in your test plan (i.e. you can’t test getUserName until you have created a user.
2	You need to be very specific in each test: - showing the sample input and indicating the expected output for that specific input as “expected output is …”
3	You need to do your tests one at a time (for example: you shouldn’t create and test in a single “test” – That should be indicated as 2 separate correctly ordered tests.
4	You should use the correct method names in your test plan
5	Test plans need to be VERY precise – yours isn’t
6	“Implement” is not a verb that belongs in a test plan. A test plan indicates the tests that will be performed on implemented methods and classes.
7	You need to indicate what method you are invoking with what values and the number of values has to correspond to the number of parameter in that method
8	You need to indicate what specific method you are invoking that will cause each of the outputs you indicate
9	When writing a test plan you don’t need to involve the user … You can hard code.