Rails Best Practices
Use asset host for cookie-free domains for components, that make your components load faster.
Use YAML's anchor and reference syntax to DRY up your database.yml file.
Data setup is sometimes painful in features writing for cucumber. Use pickle & factory of ur choice to make it less painful.
Very often, we tend to repeat a number of common steps in all scenarios within a feature, to dry things up, as well as improve readability (helping reader to better focus the intent of each scenario), we can use 'Background'.
When a scenario has too many steps, it becomes hard to read & follow. Using nested step helps to clean up the scenario, & helps promote reusability of groups of steps, think of it as code refactoring.
When you generate a new migration, try it forwards and backwards to ensure it has no errors
Using declaratives (eg. acts_as_authentic) provided by external libs is unavoidable in building a rails application. But testing 3rd party libs is surely not part of our work, yet how do we rest assured that these declaratives are called ??