December 2014
Intermediate to advanced
350 pages
8h 43m
English
As the Rails community has matured, Rails developers have become much more likely to work with codebases and test suites that contain many years’ worth of work. As a result, there has been a lot of discussion about design strategies to manage complexity over time.
There hasn’t been nearly as much discussion about what practices make tests and test suites continue to be valuable over time. As applications grow, as suite runs get longer, as complexity increases, how can you write tests that will be useful in the future and not act as an impediment to future development?
Read now
Unlock full access