Part 1					Part 2
ID-4	1.1	1.2	1.3	1.4	Part 1 Comments	2.1	2.2	2.3	2.4	2.5	Part 2 Comments
1026	4	16	4	6		5	5	20	10	15	Only 10 test cases. No strategy in report.
1161	4	6	4	6	1.2 -10 since no log was created and shown in the screen	5	0	30	6	10	No JUnit tests for TestStub. Only 2 corrections. Report consists primarily of a screen shot.
1370	4	16	4	6		1	5	30	10	20	Could not determine if CVS was used.
1385	4	16	4	6		5	5	30	10	20	TestStub tests can't "fail" by throwing an exception.
1461	4	0	4	6	1.2 -16 missing	5	5	30	10	20	Very thorough!
1489	4	6	4	6	1.2 -10 since no log was created and shown in the screen	5	0	28	10	18	No JUnit tests for TestStub. Only 14 test cases. No TestCaseIDs.
1504	4	11	4	6	1.2 -5 no screen shot	5	5	30	0	20	Made no corrections.  Otherwise, it was good.
1520	4	16	4	6		5	5	30	3	20	1 correction was made.
1691	4	16	4	6		5	0	30	0	20	No Junit tests for TestStub. No Corrections.
1701	4	16	4	6		5	5	30	10	20	Extremely thorough.  However, the student should have made it simple…
1862	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times.	1	3	12	0	0	No indication of using CVS. No JUnit tests for TestStub. Most test methods are empty. No Corrections. Missing write up.
1997	4	5	4	6	12 -5 since no screen shot						Missing part 2.
2039											No submission
2047	4	16	4	6		5	5	30	6	20	Only 2 corrections.
2118	4	0	4	6	1.2 -16 missing	5	5	30	0	20	Difficult to determine if corrections were made, as the source files were not included.
2145											No submission
2168	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times.	5	5	28	3	20	TestStub tests can't "fail" by throwing an exception. Only 14 test cases. Only 1 correction.
2171	4	16	4	6		5	3	22	3	20	TestStub tests are not in test methods, can't "fail" by throwing an exception. Only 11 tests. Only 1 correction.
2210	4	0	4	0	1.2 -16 missing 1.4 -6 missing	1	5	30	0	10	Could not determine if CVS was used.  Made no corrections.  The test report was incomplete, as it did not explicitly list testcases.
2340	4	13	4	6	1.2 -3 no logging report	5	5	30	6	20	2 corrections made.  Otherwise, it was very thorough.
2446	4	6	4	6	1.2 -10 since no log was created and shown in the screen	5	5	12	10	20	Only 6 test cases.
2540	4	13	4	6	12 -3 since only the screen shot is shown	5	0	30	0	20	No JUnit tests for TestStub. No corrections.
2574	4	11	4	6	1.2 -5 no screen shot	5	0	18	10	20	TestStub was not re-implemented.  11 Test Cases (No test cases were actually implemented for Scheduler).
2595	4	13	4	6	1.2 -3 no logging report	5	3	30	10	20	TestStub was not re-implemented properly.  Tests were thorough.
2613	4	13	4	6	1.2 -3 no logging report	5	0	30	3	20	Did not re-implement TestStub.  Made 1 correction.
2614	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times.	5	5	24	0	10	Only 12 test cases. No corrections. Report consists primarily of a screen shot.
2712	4	0	4	6	1.2 -16 missing	1	3	0	0	10	No indication of CVS being used.  Improper TestStub re-implementation.  All of the tests are blank.  Made no corrections.  The Test Report was on the right track, but was incomplete.
2829	4	13	2	6	12 -3 no logging report 1.3 -2 error calculation is wrong	5	0	30	3	20	TestStub was not re-implemented.  Only 1 correction was made.
2873	4	16	4	6		5	5	30	10	20
2899	4	8	4	6	1.2 -8 summary only	5	0	30	10	20	No JUnit tests for TestStub.
3045	4	16	4	6		5	5	30	0	20	No corrections.
3049	4	0	4	6	1.2 -16 missing	5	0	28	10	18	No JUnit tests for TestStub. Not all test cases can "fail" by throwing an exception. setUp() should be used for initialization, not constructors. No TestCaseIDs.
3079	4	16	4	6		5	5	30	10	20
3082	4	16	4	6		5	5	30	0	20	TestStub re-implementation was too elaborate.  Did not make any corrections.
3131	4	16	4	6		5	5	26	6	20	13 Test Cases.  Made 2 correctoins.
3133	4	0	4	6	1.2 -16 missing	5	4	28	0	20	TestStub tests don't test for both Frank and Julie. Only 14 tests. No Corrections.
3184	4	16	2	0	1.3 -2 since error&summary are insufficient 1.4 -6 missing	5	5	30	10	20	Good.
3196	4	8	4	6	1.2: no detailed log	5	2	30	10	20	2.2: not fully converted.
3266	4	0	4	6	1.2 -16 missing (late -4)	1	3	30	9	20	No indication of using CVS. TestStub tests are not in test methods, can't "fail" by throwing an exception. Only 3 corrections.
3318	4	13	4	6	1.2 -3 no logging report	5	5	30	10	20	Good.
3409	4	16	4	6		5	0	26	0	20	Did not re-implement TestStub.  13 Test Cases.  Did not make any corrections.
3452											Missing assignment
3466	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times.	5	3	24	6	20	TestStub tests don't do anything. Only 12 tests. Only 2 corrections.
3579	2	11	2	6	1.1 -2 insufficient 1.2 -5 no screen shot 1.3 -3 summary insufficient	1	5	30	3	20	Did not use CVS.  1 correction made.
3679	4	11	4	6	12 -5 since no screen shot	1	0	0	0	0	No indication of using CVS. No JUnit tests for TestStub. All JUnit test cases are empty. No corrections. Report consists primarily of a screen shot.
3789	4	16	4	6		5	5	30	3	20	1 correction was made.  Otherwise, the rest was good.
3829	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times.	5	4	30	0	18	Made no corrections.  Otherwise, it was good.  The Test Report spacing was off.
3845											No submission
3850	4	13	4	6	1.2 -3 since only the screen shot is shown	5	5	30	0	20	No corrections.
3885	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times.	5	5	28	10	20	Only 14 test cases
3935	4	0	4	6	1.2 -16 missing	5	0	30	10	10	TestStub was not re-implemented.  The Test Report is not informative.  It was difficult to find changes made in the code, although they do exist.
3993	1	11	1	0	1.1 -3 insufficient estimation 1.2 -5 since no screen shot 1.3 -3 insufficient summary 1.4 -6 missing	5	3	20	3	20	TestStub doesn't use setUp() and tearDown() methods appropriately. Only 10 tests. Only 1 correction.
4013	4	11	4	6	12 -5 since no screen shot	1	3	24	0	20	No indication of using CVS. TestStub tests are not in test methods, can't "fail" by throwing an exception. Only 12 test cases. No Corrections.
4026											Missing assignment.
4035	4	16	4	6		1	5	30	10	20	CVS was not used.
4184	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times.	5	5	30	3	10	Made on correction.  Test Report was misleading, as it was not complete.
4197	4	16	4	6		5	5	30	6	10	Made 2 corrections.  Test report was incomplete.
4241	4	11	4	6	1.2 -5 since no screen shot	5	5	24	6	20	Only 12 test cases. Only 2 corrections.
4294	4	16	4	6		5	5	30	10	20	Great.
4378	4	16	4	6		1	5	30	10	20	It was unclear whether CVS was used.  Great test report!
4439	4	11	4	6	1.2 -5 no screen shot	1	5	30	10	20	Could not determine if CVS was used.  The Test Report was insanely thorough!
4465	4	16	4	6		5	5	30	10	20	Very thorough tests.  Test Report was clear.
4518	4	16	4	6	(late, -8)	5	0	30	6	20	No JUnit tests for TestStub. Only 2 corrections.
4582	4	16	4	6		5	4	20	10	20	TestStub tests can't "fail" by throwing an exception. Only 10 test cases.
4656	4	16	4	6		5	3	30	10	20	TestStub was not re-implemented correctly.  The Test Report was hard to follow, although it was thorough.
4725	4	16	4	6		5	5	30	10	20
4744	4	13	4	6	12 -5 since no screen shot; explanation given	3	4	30	0	20	TestStub tests can't "fail" by throwing an exception. No corrections.
4895	4	11	4	6	1.2 -5 no screen shot	1	1	24	0	20	12 Test Cases.  Could not determine if CVS was used.  Incorrect conversion of TestStub.  No corrections.
4909	4	16	4	6	(late, -10)	5	0	16	3	18	Did not re-implement TestStub.  Test Report was misleading… only 8 test cases were made.  Made one correction.  TestCaseID ommitted.
5163	4	13	4	6	1.2 -3 no logging report	5	3	28	9	20	Incomplete conversion of TestStub.  Only made 3 corrections.  Very well organized document.
5185	4	6	4	4	No log; -2 for 1.4, too short and cryptic.	1	5	24	10	15	12 test cases; no CVS; report has no strategy.
5235											Missing assignment.
5279	4	16	4	6		5	5	30	3	20	Only 1 correction.
5315	4	16	4	6		5	5	30	10	20
5426	4	16	4	6							Missing assignment.
5476	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times. (late -6)	5	3	8	0	20	TestStub tests are not in test methods, can't "fail" by throwing an exception. Only 4 test cases. No corrections.
5512	4	6	4	6	1.2 -10 since no log was created and shown in the screen						Missing assignment part 2.
5680	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times.	5	1	30	10	20	Created a TestStub but did not actually implement it.
5717	4	11	4	6	1.2 -5 since no screen shot	1	5	24	0	20	No indication of using CVS. Only 12 test cases. No Corrections.
5724											Missing assignment
5792	4	16	4	6		5	5	30	10	20	Awesome.
5812	4	0	4	0	1.2 -16 missing 1.4 -6 missing	3	0	26	10	10	Did not use CVS because of errors.  Did not re-implement TestStub.  Did not have tests for one class.  The Test Report was not a good indicator of the work that was done, as it was incomplete.
5832	4	16	4	6		5	3	30	0	10	TestStub tests are not in test methods, can't "fail" by throwing an exception. No corrections. Report only lists tests, incomplete.
6031	4	16	4	6		5	0	26	6	18	No JUnit tests for TestStub. Only 13 test cases. Only 2 corrections. Unique names for tests are not actually unique.
6033	4	16	4	6		5	4	24	0	20	Confusing TestStub conversion.  No corrections made.
6209	4	16	4	6		5	5	30	10	20
6327	4	13	4	6	1.2 -3 since only the screen shot is shown	5	3	30	10	20	No JUnit tests for TestStub.
6398	4	13	4	6	1.2 -3 no logging report	1	0	30	0	20	No CVS, no TestStub, no corrections.
6432	4	16	4	6		5	0	24	0	0	No JUnit tests for TestStub. Only 12 test cases. No Corrections. Report consists only of a screen shot.
6455	4	16	4	6		5	5	6	0	20	Only 3 test cases. No corrections.
6491											No submission
6608	4	16	4	6		5	0	30	0	20	Did not re-implement TestStub.  Made no corrections.  Test report was clear.
6745	4	16	4	6		5	0	30	3	20	Did not convert TestStub.java.  Only 1 correction.
6849	4	16	4	6		5	5	24	6	20	Only 12 test cases. Only 2 corrections.
6923	4	16	4	6		5	0	30	3	20	No JUnit tests for TestStub. Difficult to tell what was corrected (files are not java file, but CVS records?)
7092	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times.	1	0	18	0	10	No indication of using CVS. No JUnit tests for TestStub. Only 9 test cases. No corrections. Report has only findings, no information on test cases.
7202	4	16	4	6		5	5	30	6	20	Made 2 corrections.  Well organized test report.
7272	4	11	4	6	1.2 -5 since no screen shot	5	0	30	0	0	No JUnit tests for TestStub. No Corrections. Report consists primarily of a screen shot.
7293	4	0	4	6	1.2 -16 missing	5	5	30	9	20	Corrected 3 errors.
7400	4	16	4	6		5	0	26	10	19	Did not re-implement TestStub.  13 Test Cases.  The Test Report formatting made it hard to read.
7409	4	16	4	6		1	0	30	6	20	CVS was not used.  Did not re-implement TestStub.  Made 2 corrections.
7520	4	16	4	6		5	5	30	2	20	Great Test Report!  It is not clear whether any changes were made, as the source code was not provided, however changes were suggested in the report.
7692	4	16	4	6		5	5	30	0	20	No corrections.
7785	4	13	4	6	1.2 -3 no logging report	5	4	30	10	20	Converted most of TestStub.
7857	4	16	4	6	(late, -3)	5	5	30	10	20	No JUnit tests for TestStub.
7862	4	16	4	6		5	0	30	10	20	TestStub was not re-implemented.
7913	4	16	4	6		5	5	30	10	20	Good.
8087	4	16	4	6	(late, -10)	5	4	30	10	20	TestStub should have been created differently, but this is mostly fine.
8154	4	16	4	6		5	3	30	10	18	TestStub tests can't "fail" by throwing an exception. Probably corrections should prevent setting bad values in the first place, rather than prevent getting bad values. No TestCaseIDs.
8274	4	16	4	6		5	5	30	10	20
8292	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times.	5	1	24	9	20	A TestStub was available, but was empty.  12 Test Cases.  3 corrections made.
8300	4	0	4	0	1.2 -16 missing 1.4 -6 missing (late, -10)	1	0	26	0	20	Could not determine if CVS was used.  TestStub was not re-implemented.  13 test Cases.  No corrections made.
8335	4	11	4	6	1.2 -5 no screen shot	1	4	28	0	20	Unable to determine if CVS was used.  TestStub not fully re-implemented.  Scheduler was not tested, but test cased existed.  Unable to determine if corrections were made.
8341	4	16	4	6		5	0	24	3	20	Did not re-implement TestStub.  12 Test Cases.  1 Correction.
8455	4	16	4	6		5	0	26	0	20	No JUnit tests for TestStub. Only 13 test cases. No Corrections.
8457	4	16	4	6		5	5	30	0	20	No corrections.
8462	4	16	4	6		5	3	10	0	20	JUnit tests don't use "test" methods. No corrections.
8510	4	11	4	6	1.2 -5 no screen shot	5	0	26	10	20	TestStub re-implementation was empty.  No test cases available for seminar.
8531	4	13	2	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times. 1.3 -2 since no error calculation	5	5	28	10	20	JUnit tests don't always use setUp() and tearDown() methods appropriately. Report probably should use bulleted text, it's hard to read as purely prose.
8554	4	11	4	6	1.2 -5 since no screen shot	5	4	30	10	20	TestStub has only one test method.
8599	4	10	4	6	1.2 -6 since CVS shows that the log was checked in and out fewer than three times and no logging report	5	5	30	9	20	Made 3 corrections.  Test report was mostly in prose, which made it more difficult to follow.
8668	4	16	4	6	(late, -10)	5	0	30	3	18	No JUnit tests for TestStub. Only 1 correction. No TestCaseIDs.
8725	4	11	4	6	12 -5 since no screen shot	5	0	30	10	20	No JUnit tests for TestStub. Corrections should not include renaming the classes.
8779	4	16	4	6		5	5	22	10	20	Only 11 test cases.
8782	4	0	4	6	1.2 -16 missing	5	5	30	0	18	No corrections were made.  The Test Report should have been labeled well.
8989	4	16	4	6		5	4	28	10	20	TestStub tests can't "fail" by throwing an exception. JUnit tests must thrown the exception to indicate that they failed.
9074	0	0	0	6	1.1 -4 missing 1.2 -16 missing 1.3 -4 missing	1	0	6	0	10	No indication of using CVS. No JUnit tests for TestStub. Only 3 test cases. No Corrections. Report incomplete.
9190	4	16	4	6		5	0	30	3	20	No JUnit tests for TestStub. Preventing an exception from being thrown isn't really a "correction". Handling the case where the exception would be thrown in a different way, would be okay.
9199	4	0	4	6	1.2 -16 missing	3	0	10	0	0	Did not convert TestStub.java.  Did not complete test cases.  Did not create report.
9239	4	16	4	6		5	5	24	0	16	Made no corrections.  Missing Scheduler Tests.  Only 12 test cases were created.Test report should be more detailed.
9390	4	16	4	6		5	5	30	6	20	Made 2 corrections.  Good.
9486	4	16	4	6		5	5	30	10	20	Some of the aggregated tests could/should be split up into multiple test cases.
9491	4	16	4	6		5	5	30	10	20
9498	4	16	4	6		5	5	28	10	20	JUnit tests don't always use setUp() and tearDown() methods appropriately. Nice corrections!
9503	4	16	4	6		5	5	28	10	20	Test cases can't fail by throwing an exception.
9530	4	13	4	6	1.2 -3 no logging report	5	4	30	10	20	TestStub re-implementation should separate concerns.
9671	4	13	4	6	1.2 -3 since CVS shows that the log was checked in and out fewer than three times.	5	3	30	0	20	TestStub has only one test method. No corrections.
9691	4	0	4	6	1.2 -16 missing	1	0	30	0	20	No indication of using CVS. No JUnit tests for TestStub. No Corrections.
9729	4	6	4	6	1.2 -10 since no log was created and shown in the screen	5	5	30	10	20
9823	4	11	4	6	1.2 -5 no screen shot	5	4	24	0	12	Confusing TestStub conversion.  Had 14 test cases, but no test cases existed for Scheduler.  Difficult to determine if defects were fixed.  The Test Report was written in prose, which made it difficult to follow.  It did not describe in detail, what was being tested.
9918	4	14	4	6	1.2 -2 revision control insufficient	1	5	30	10	20	CVS was not used.  Very thorough Test Report.
9934	4	16	4	6		5	5	25	10	15	2.3, -5: unorthodox Junit Test Case Structure (all test cases were in one file).  2.5: -5: report not in reqested format
9980											Missing assignment
4841L	4	16	2	6	1.3 -2 insufficient summary	5	3	24	0	20	Did not make any corrections.  TestStub formatting was odd.
4841V	4	0	4	6	1.2 -16 missing	1	5	18	0	20	No indication of using CVS. Only 9 test cases. No Corrections.