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
Currently all unit test messages (the ones in "assert…") describe the case when the test/assert passes/is satisfied. However, as they are only printed when the assert actually fails, they should better describe the opposite case: What actually fails.
This is an easy wording task. Just turn around the meaning of all these messages. (Remember to use present tense.)
Example: "Should print 1234."
Change to: "Does not print 1234."
The text was updated successfully, but these errors were encountered:
Currently all unit test messages (the ones in "assert…") describe the case when the test/assert passes/is satisfied. However, as they are only printed when the assert actually fails, they should better describe the opposite case: What actually fails.
This is an easy wording task. Just turn around the meaning of all these messages. (Remember to use present tense.)
Example: "Should print 1234."
Change to: "Does not print 1234."
The text was updated successfully, but these errors were encountered: