fefrei / prog2tests

Automatically exported from code.google.com/p/prog2tests

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

idea test extensions

GoogleCodeExporter opened this issue · comments

Could you slightly change the loop including tests timeout?
I had in mind that you could check if break, continue, while and do while are 
implemented yet.
Problem here:
maybe the users would have to 
>>return null
in their unimplemented methods? The test could print a brief reminder (console)
this would prevent the tests to melt your board ;)


Original issue reported on code.google.com by TheEquiv...@googlemail.com on 23 Jul 2012 at 9:33

If the user returns null, then the tests fail in some way or the other.
I'd suggests that you use
throw new UnsupportedOperationException("Not yet implemented");
as dummy implementation, but not "return null;"

Detecting that there's a null somewhere in the tree is pretty hard and, in my 
eyes, not necessary.
Remember that we can't use visitors -- at least we can't implement our own 
Visitor.

"Melt your board"? I don't know what you mean here.
Most of our tests (at least mine) have a timeout. So, if your implementation is 
caught in a loop, or tries to take more than a few seconds for computation, an 
exception is risen that tells you "TimeoutException". So, no board-melting here.

Original comment by Nichmen...@gmail.com on 24 Jul 2012 at 6:51

No response, plus there's no "open question" or something here.

Original comment by Nichmen...@gmail.com on 27 Jul 2012 at 12:42

  • Changed state: Expired