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
We could write new methods (Ex: assertEqualHint) that takes function, args (as a tuple), and expected as parameters, generates the msg automatically, calls the function with the given arguments, and then does the assertion. That would also make giving consistent and correct feedback easier. Sometimes instructors accidentally do (expected, actual) based on JUnit, which is confusing, because students think the expected value is what their function returned.
The text was updated successfully, but these errors were encountered:
Another idea from today's meeting. We have a lot of test code like this:
We could write new methods (Ex:
assertEqualHint
) that takesfunction
,args
(as a tuple), andexpected
as parameters, generates themsg
automatically, calls the function with the given arguments, and then does the assertion. That would also make giving consistent and correct feedback easier. Sometimes instructors accidentally do (expected, actual) based on JUnit, which is confusing, because students think the expected value is what their function returned.The text was updated successfully, but these errors were encountered: