Contract testing checks whether different components honor the same behavioral promise. To test the Liskov Substitution Principle, run the parent class’s unit tests against each subclass; a failure reveals behavior that callers cannot safely depend on. section 3.4.3
Test the player contract
If Player tests require a player to move away from the net, run those tests against Goalie and Midfielder too. A Goalie that fails has broken the parent class’s contract. section 3.4.3






