David,
Here is an extract from my source code
it should allow authenticated user to access '#{action}' do
@user = mock_user_authentication(:id = 1, :identity_url =
http://openid.server/yrashk;, :queues = [])
get action, params
assigns[:current_user].should ==
David,
Depending on action, it is either successful response or response
that redirects somewhere (but not to login, since user is
proven to
be authenticated). In this example, I really don't want to care,
whether it was successful response or redirection to somewhere,
until
it is not
Hi Paul,
On 27/07/2007, at 1:13 AM, Paul Brackenridge wrote:
When I run script/generate I get the following:
Installed Generators
Plugins: authenticated, rspec, rspec_controller, rspec_model,
rspec_scaffold
Builtin: controller, integration_test, mailer, migration, model,
observer,
There might be a better way to do it, but I basically ripped off
the builtin spec:doc Rake task almost verbatim and made a custom task
in my Rails app for generating the HTML report. This isn't anything
magical, but you should be able to drop a file called
whatever_you_want.rake in your
Recently as a result of using Git I've noticed a number of
inconsistencies in the RSpec codebase with respect to whitespace
(mixed line endings, mixed use of spaces and tabs for indentation,
and trailing whitespace at the end of lines). I never would have
noticed, but Git produces nice
