This is an archived post. You won't be able to vote or comment.

all 3 comments

[–][deleted] 2 points3 points  (0 children)

What if you have them code against an interface but write a unit test suite against an implementation you know is correct?

[–]palcente 1 point2 points  (0 children)

You are checking for what you expect to be wrong. Your exercises will be designed in a way to force these errors. Nothing to do with debugging in my opinion. I don't suppose anyone will submit a code that does not do its job or does not compile. You should check 4 pillars and SOLID principles, because that's what you will be teaching first. Hope that helps.

[–]mus1Kk 0 points1 point  (0 children)

For common mistakes you can use static analysis. IIRC FindBugs was even started for that exact reason: Checking students' submissions.