Hey guys,
I'm trying to get rSpec (rev 2996) working with Rails 2 (rev 8214).
Running the tests from the command line works, no problem.
I installed the RSpec.tmbundle (also rev 2996), and would like to see
the HTML test results in TextMate. When I run the "Run examples in
selected files/directo
Just seven upped the latest rspec update, and suddenly all my
be_matchers don't work anymore (they worked just before I updated):
User.find_by_email(email).should_not be_confirmed
User.find_by_email(email).confirmation_code.should_not be_nil
>>
FAILURES:
1) confirmation (
For the default setup of RSpec is there a way to set the fail_on_error
instance variable to false from outside of spectask.rb? I am not familiar
enough with either ruby or rails to figure this out from the information
provided. I realize that there is a fail_on_error= method but I do not
know what
On 11/26/07, Daniel Tenner <[EMAIL PROTECTED]> wrote:
> Just seven upped the latest rspec update, and suddenly all my
> be_matchers don't work anymore (they worked just before I updated):
> Anyone else getting that?
All of my controller specs are passing, but my stories are failing
with the sam
On Nov 26, 2007 11:57 AM, Josh Knowles <[EMAIL PROTECTED]> wrote:
> On 11/26/07, Daniel Tenner <[EMAIL PROTECTED]> wrote:
> > Just seven upped the latest rspec update, and suddenly all my
> > be_matchers don't work anymore (they worked just before I updated):
>
>
>
> > Anyone else getting that?
>
First time I have a look inside the RSpec codebase (let alone the
Story Runner), and not much luck this time. But, counter-intuitively
enough, I think it's probably nothing to do with RailsStory itself
since that didn't change in the last update. Trying to add an include
Spec::Matchers in t
These are the files that got modified in between. Revision 2994 has
the matchers working.
Reversing to 2994 highlighted these files:
[EMAIL PROTECTED]:~/Sites/xxx.local/xxx/rails/trunk/vendor/plugins/
rspec$ svn up -r 2995
Dstories/example_groups/nested_groups
Dstories/resources/spec/n
On Nov 26, 2007 1:09 PM, Daniel Tenner <[EMAIL PROTECTED]> wrote:
> First time I have a look inside the RSpec codebase (let alone the
> Story Runner), and not much luck this time. But, counter-intuitively
> enough, I think it's probably nothing to do with RailsStory itself
> since that didn't chang
On 11/26/07, David Chelimsky <[EMAIL PROTECTED]> wrote:
> Again - I'll look at this tonight and get it working.
http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/147-patch-allow-stories-to-use-spec-matchers
--
Josh Knowles
phone: 509-979-1593
email: [EMAIL PROTECTED]
web:http://jos
On Nov 26, 2007 2:02 PM, Josh Knowles <[EMAIL PROTECTED]> wrote:
> On 11/26/07, David Chelimsky <[EMAIL PROTECTED]> wrote:
> > Again - I'll look at this tonight and get it working.
>
> http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/147-patch-allow-stories-to-use-spec-matchers
Applied -
I wrote some quick notes up on a custom matcher I wrote around a
pattern that I am using constantly.
http://smartic.us/2007/11/26/rspec-matcher-for-active-record-associations
You could use it as a custom matcher tutorial for the uninitiated or
as a possible solution for validations specs for
11 matches
Mail list logo
