June 2014 Summaries

The text discusses common anti-patterns in Test-Driven Development (TDD) by highlighting specific issues with writing test cases, using examples from Ruby code. It critiques the practice of adding multiple assertions to a single test case, which can lead to vague descriptions and obscure the root cause of test failures, thus defeating the purpose of a short feedback loop. The text illustrates this with a "feedback form" test case for events, showing how it can be improved by separating different expectations into distinct test contexts. It also addresses the problem of using different test values in a single test case, suggesting that separating test scenarios makes the output clearer and the feedback more informative. The discussion includes examples of testing city name slugs to demonstrate how tests can be more explicit and readable, enhancing their effectiveness.

Continuous delivery is becoming increasingly popular within the PHP community due to its benefits in reducing development risk and accelerating the deployment process. By automatically testing new code through continuous integration and deploying working versions via continuous deployment, developers can focus more on coding and delivering products safely. With PHP support now available on platforms like Semaphore and Heroku, setting up a continuous delivery pipeline for a Laravel web application is straightforward. The process involves creating a Heroku application, possibly using a custom build pack via the command line for necessary dependencies, and then setting up continuous integration from GitHub to Semaphore. Once set up, Semaphore can automatically test and deploy the application to Heroku whenever new code is pushed to GitHub, provided all tests pass. This automation streamlines the deployment process and can be manually triggered if needed, allowing developers to efficiently manage and deliver their applications.