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
When we write tests, we don't usually check whether an instance of a class responds to a particular method. Instead, we check whether that method behaves correctly given various situations/scenarios. Your tests should ensure that in the event of code changes, the original functionality is still intact (these are what we call regression tests - just a fancy term).
Let's look at the tests written for the plugin handler and the resume maker. I can change the internal implementation of the methods and the tests wouldn't catch the changes.
Let me know if you need help understanding this more.
The text was updated successfully, but these errors were encountered:
Issue well understood. I shall write tests that tests the internal implementation of the given entity.
So instead of checking whether it responds to all those method calls, I have to see if they are performing the tasks(or making the internal changes they should make). Got it, thanks.
When we write tests, we don't usually check whether an instance of a class responds to a particular method. Instead, we check whether that method behaves correctly given various situations/scenarios. Your tests should ensure that in the event of code changes, the original functionality is still intact (these are what we call regression tests - just a fancy term).
Let's look at the tests written for the plugin handler and the resume maker. I can change the internal implementation of the methods and the tests wouldn't catch the changes.
Let me know if you need help understanding this more.
The text was updated successfully, but these errors were encountered: