Verifiable View

Keep your database view definitions in sync with your named scopes and associations' definitions.

gem install verifiable_view

class RegularProduct
  extend VerifiableView

  definition do
    Product.
      not_deprecated.
      where(Product.arel_table[:price].gt(150)).
      select(:id, :name, :price)
  end
end

Then in your tests you'll have a

test "regular_products view is up-to-date" do
  RegularProduct.verify
end

That will check that you have a regular_products view defined in your database and that the query matches with your definition (Products that are not deprecated, with prices superior to 150, etc)

Named scopes and named associations are easy to write with Arel and easy to maintain. Every time you write a view by crafting your SQL by hand you risk forgetting a condition. If you already have already defined associations or named scopes why to violate DRYness and duplicate their definitions?

Also when updating the definition of a named scope, you will notice immediately that your view got out of your sync.

gem install dep dep install cutest test/*.rb