Error'd: Yes We Have No Banana... Note

Error'd: Yes We Have No Bananas

There is a collection of incidents where companies are testing in production, which is a vital part of the development process. Testing in production allows companies to identify issues before their customers do, but it should be done in a way that doesn't affect customers. When testing in production goes wrong, it can be embarrassing for the company and frustrating for the customers. A series of examples are provided, including incidents from Firestone Auto Care, Crunchyroll, and Engadget, where testing in production was done poorly. In each of these cases, the testing was visible to customers, which is not ideal. Other examples include a test item on a live webstore, a default test message, and a leaky production test by Amazon Prime video. These incidents highlight the importance of testing in production, but also the need to do it carefully and discreetly. The examples provided are from various companies and industries, showing that testing in production is a common practice. The article concludes with an advertisement for ProGet, a tool that provides security and access controls on NuGet feeds. Overall, the article emphasizes the importance of testing in production, while also showcasing examples of when it goes wrong.
CdXz5zHNQW_0GoSFKOcEN.jpeg