Because sometimes one test is all you can handle.

No reason to duplicate them, the gemspec would have priority anyway since
it appears later in the file

If it doesn't then Sinatra::Base never initializes the template_cache,
causing undefined variable exceptions later in it's life-cycle

It's part of the Ruby stdlib in 1.9

Otherwise calling delete on it will perform a delete in the database.
Under ActiveRecord 2.3, records returned from a scope where array-like and a delete just removed
them from the in-memory representation, not the DB.  Under newer
ActiveRecord, it's an association so delete also performs a DB delete.

If actions are not an absolute path then they need to be loaded from the
current directory.

An alternate method would be to convert relative action paths to absolute.

This way the actions can be required by using their basename