Group items tagged

priamo od tvorcu Rails "... I rarely unit test in the traditional sense of the word, where all dependencies are mocked out..."

Cognitive dissonance is the most often cited reason for claims for independent testing teams. IF the tester is part of the development team that created the product, then he will be biased to confirm the product is working.

Testing distributed systems under hard failures like network partitions and instance termination is critical, but it's also important we test them under less catastrophic conditions because this is what they most often experience. Comcast is a tool designed to simulate common network problems like latency, bandwidth restrictions, and dropped/reordered/corrupted packets. It works by wrapping up some system tools in a portable(ish) way. On BSD-derived systems such as OSX, we use tools like ipfw and pfctl to inject failure. On Linux, we use iptables and tc. Comcast is merely a thin wrapper around these controls.

The customer-service obsessed company calls its executives "monkeys," has staffers ring cowbells to greet guests, and offers new employees cash to quit as a way to test their loyalty. The Las Vegas-based retailer is now going even more radical, introducing a new approach to organizing the company. It will eliminate traditional managers, do away with the typical corporate hierarchy and get rid of job titles, at least internally.

It speeds up development by keeping your application running in the background so you don't need to boot it every time you run a test, rake task or migration.

has_many is an anti-pattern which leads straight to monolithic applications. However, a simple inversion can free us from its grasp. What is the first model you added to your application? Probably User, right? So, once you wrote user.rb and its corresponding tests, and committed it - why did you ever open that file up again to tell it about something that it did not need to know existed? Rails keeps you from reopening user.rb if you add a column to the User table, and this is good, right? So why, when you added a Posts table far away, did you open up User again to make it aware of Posts? Did the definition of being a user change? Did you did not realize you were violating the Open-Closed Principle, one of the 5 principles of SOLID design? Somewhere inside I bet you knew it felt dirty to keep opening up User and making it aware of things that it had been blissfully unaware of.