Question Authors' Forum

Unfortunately the condition 'compile error' is global to all tests, even if some of the tests would compile ok in isolation.

We generally try to avoid this sort of situation by setting a series of questions asking students to incrementally develop a class. Each new questions defines and tests a single new method. That provides a nice test-as-you-go development strategy for the students.

However, you could achieve what you wanted by turning off the "All-or-nothing" checkbox and using reflection in your test cases. For example if students are asked to write a class Bunkum with two method "hi" and "ho", you could test those methods with test-case code like

 

Bunkum bun = new Bunkum();
try {
    var hiMethod = Bunkum.class.getMethod("hi");
    hiMethod.invoke(bun); // Call bun.hi()
} catch (ReflectiveOperationException e) {
    System.out.println("Unimlemented 'hi'. Test aborted.");
}

and

 

Bunkum bun = new Bunkum();
try {
    var hoMethod = Bunkum.class.getMethod("ho");
    hoMethod.invoke(bun); // Call bun.ho
} catch (ReflectiveOperationException e) {
    System.out.println("Unimlemented 'ho'. Test aborted");
}