Great Habits

In this lesson, we introduced a few new habits. Check them out in the following list.

Considerations When Writing a New Test

• Tests should test one thing only
• Create more specific tests to drive a more generic solution (triangulate)
• Give your tests meaningful names (behavior/goal-oriented) that reflect your business domain
• See tests fail for the right reason
• Ensure you have meaningful feedback from failing tests
• Keep your tests and production code separate
• Organize your unit tests to reflect your production code (similar project structure)
• Organize your tests in arrange, act, and assert blocks
• Write the assertion first and work backward
• Write fast, isolated, repeatable, and self-validating tests

Considerations When Making a Failing Test Pass

• Write the simplest code to pass the test
• Write any code that makes you get to the refactor phase quicker
• Use Transformation Priority Premise
• Consider using object...