"value":"\n <p>When fixing a bug or adding a new feature using test-driven development, it's important to see the test fail first.<\/p>\n\n<p>You should write your test so it doesn't pass by default or accidentally.<\/p>\n\n<p>When creating data, such as users or nodes within tests, do so in a way that will force the test to fail, such as explicitly setting the title or published date into a non-default order.<\/p>\n\n<p>When fixing a bug, write a test that represents the expected outcome when the bug is fixed. This confirms the bug exists and can be replicated.<\/p>\n\n<p>Then, once the tests pass, you know the feature or fix is working and that it's because of your changes and not for any other reason.<\/p>\n\n ",
"format":"full_html",
"processed":"\n <p>When fixing a bug or adding a new feature using test-driven development, it's important to see the test fail first.<\/p>\n\n<p>You should write your test so it doesn't pass by default or accidentally.<\/p>\n\n<p>When creating data, such as users or nodes within tests, do so in a way that will force the test to fail, such as explicitly setting the title or published date into a non-default order.<\/p>\n\n<p>When fixing a bug, write a test that represents the expected outcome when the bug is fixed. This confirms the bug exists and can be replicated.<\/p>\n\n<p>Then, once the tests pass, you know the feature or fix is working and that it's because of your changes and not for any other reason.<\/p>\n\n ",