If the end goal is to reduce test time how about setting up capybara and writing some tests checking for proper markup? Or use one of the many multi browser screens shot services out there so you only have to look over the screenshots to verify formatting. Don't forget that many browser vendors and versions have their own rendering quirks...
We also do something along the lines of what Diego was talking about. Using devise it was simple to create a second session controller that lets you assume the identity of another user and stores the original as another warden "user". In this scenario signing out of the assumed user session signs you back in as your original user. It's been a while since I set this up so the following simplified code may leave out some key bits but I'm 99% sure this is all you'd need:
# app/controllers/assume_user_sessions_controller.rb
class AssumeUserSessionsController < ApplicationController
authorize_resource :class => false # Make sure current_user is allowed to do this! Otherwise serious security implications.
def create
sign_in :user, User.find(params[:assume_user_id])
sign_in :original_user, current_user
redirect_to some_path
end
def destroy
sign_in :user, original_user
sign_out :original_user
redirect_to some_path
end
end
# app/controllers/application_controller.rb
def original_user
warden.user(:orginal_user)
end
# config/routes.rb
# change class_name as appropriate
devise_for :assume_user, :class_name => 'User', :only => []
resource :assume_user_session do
delete :destroy, :as => "destroy" # devise compatibility
end