#275
How I Test
Jul 18, 2011 |
15 minutes |
Testing, Refactoring
Here I show how I would add tests to the password reset feature created in the previous episode. I use RSpec, Capybara, Factory Girl, and Guard to make request, model, and mailer specs.
How Can We Develop For Tomorrow's Needs? - 2 views
OXID eShop, la solution e-commerce open source allemande arrive (enfin) en France : BLO... - 5 views
Ruminations From a Tortured Mind - 0 views
#275 How I Test - RailsCasts - 0 views
37signals Product Blog: We're retiring the Product Blog. Please follow us on Twitter fo... - 1 views
Androidpatterns.com comment designer des applis Android - 0 views
Yoshinori Matsunobu's blog: Announcing MySQL-MHA: "MySQL Master High Availability manag... - 2 views
-
A primary objective of MHA is automating master failover and slave promotion within short (usually 10-30 seconds) downtime, without suffering from replication consistency problems, without spending money for lots of new servers, without performance penalty, without complexity (easy-to-install), and without changing existing deployments. MHA also provides a way for scheduled online master switch: changing currently running master to a new master safely, within a few seconds (normally 0.5-2 seconds) of downtime (blocking writes only).
Daniel Fischer's Blog - Upgrading from Snow Leopard to Lion - 2 views
Open World Forum 2011 - Home - 1 views
« First
‹ Previous
41 - 60 of 86
Next ›
Last »
Showing 20▼ items per page