Great Habits

In this lesson, we introduced a new habit. Check it out in the following lists.

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 that the test fails 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 to the project structure).
• Organize your test into arrange, act, and assert blocks.
• Write the assertion first and work backward.
• Write fast, isolated, repeatable, and self-validating tests.
• Consider using object calisthenics to drive design decisions.
• Consider adding tests to legacy code.

Considerations When Making a Failing Test Pass

• Write the simplest code to pass the test...