You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A good unit test has only one assert statement. However, in practice we sometimes use more than one assert statement or the code before the assert fails for whatever reason (e.g. NPE in student code). In these cases, we'd like to give point percentages.
So the whole test is worth 10 (relative) points in total. If you reach the Checkpoint, you will get proportionate values of that, even if the test method fails later on.
One might even allow variables in the checkpoint annotation (instead of constants only).
The text was updated successfully, but these errors were encountered:
A good unit test has only one assert statement. However, in practice we sometimes use more than one assert statement or the code before the assert fails for whatever reason (e.g. NPE in student code). In these cases, we'd like to give point percentages.
A possible annotation might be:
So the whole test is worth 10 (relative) points in total. If you reach the Checkpoint, you will get proportionate values of that, even if the test method fails later on.
One might even allow variables in the checkpoint annotation (instead of constants only).
The text was updated successfully, but these errors were encountered: