Em 26-05-2011 09:14, Christian Johansen escreveu:
Actually this is just a matter of taste, like with RSpec. I prefer
to read specs as well as Capybara write syntax (visit url, etc).
The tests get much more readable for my taste. But I'll do it
using Rails integration tests if you prefer.
Ok. I was a bit worried that Capybara implied Cucumber, and I'm not
all that into that :)
Me too! Never bought the Cucumber idea! Cucumber == cumbersome ;)
So, if Capybara tests will still run fast, and stay readable (I think
the default runner is RackTest, so that should be in-memory and fast,
right?) you're welcome to give it a go with one test case, and we can
decide from that, ok?
Ok, when I write an example test, I'll let you know.
This worries me a bit, because I suspect we will take some heat
for security regressions, even if only temporary. Is there a
convenient way to monkey patch Device to add the secure option?
Just while we wait for Rails 3.
Yes, that is what I've said. Since you are open to change to
Devise before we finish the migration to Rails 3, then we *should*
use secure cookies. In that case we can either write another
strategy, or monkey patch the current strategy or send a pull
request to Devise 1.0 branch (prefered alternative for me) to make
it compatible with newest Devise.
Sure, we can send them a pull request, seems like the better option.
In the meanwhile, until it is merged, we can still poing to my fork of
Devise (man, I love Bundler! :D )
Of course it's possible! If it works, we'll use it :) What we
usually do with changes of this magnitude is to deploy changes to
an internal staging area for a week or so before launching it on
gitorious.org <http://gitorious.org>.
This remembers me another thing I would like to talk with you. Is
it possible for you to set some staging server that could be
tested by the public? I mean, backup data and repositories from
the official Gitorious and make them available in a staging
server. That way, before we migrate to Rails 3, people would be
able to try it and report any problems... Of course that changes
involving security like cookie or password stealing, etc, couldn't
be available with real data in this staging server, but I think
that for the other changes this could be a great idea...
I agree that having a public staging area would be cool. I'm not quite
sure how we should actually do this, but I'll think about it.
Thanks. Unfortunately, I wasn't able to work on Gitorious
yesterday night. I've spent all my little free time watching the
awesome Aaron Patterson (tenderlove) talk on RailsConf :)
Yeah, he is awesome :)
I was talking about the talk, but he is awesome too :)
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
