February 2007 Archives by author

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...

Starting: Thu Feb 1 08:33:25 EST 2007
Ending: Wed Feb 28 14:30:30 EST 2007
Messages: 140

• [rspec-devel] Coming Soon...   David Chelimsky
• [rspec-devel] Will it be "response.should_have" or "response.body.should_have"?   David Chelimsky
• [rspec-devel] Will it be "response.should_have" or "response.body.should_have"?   David Chelimsky
• [rspec-devel] Will it be "response.should_have" or "response.body.should_have"?   David Chelimsky
• [rspec-devel] Will it be "response.should_have" or "response.body.should_have"?   David Chelimsky
• [rspec-devel] Meta specifications or spec. helpers available?   David Chelimsky
• [rspec-devel] Meta specifications or spec. helpers available?   David Chelimsky
• [rspec-devel] [ANN] RSpec 0.8.0-RC1   David Chelimsky
• [rspec-devel] Meta specifications or spec. helpers available?   David Chelimsky
• [rspec-devel] Meta specifications or spec. helpers available?   David Chelimsky
• [rspec-devel] [ANN] RSpec-0.8.0   David Chelimsky
• [rspec-devel] Meta specifications or spec. helpers available?   Evgeny
• [rspec-devel] Meta specifications or spec. helpers available?   Evgeny
• [rspec-devel] Meta specifications or spec. helpers available?   Evgeny
• [rspec-devel] Meta specifications or spec. helpers available?   Evgeny
• [rspec-devel] Will it be "response.should_have" or "response.body.should_have"?   James Hughes
• [rspec-devel] Will it be "response.should_have" or "response.body.should_have"?..never mind   James Hughes
• [rspec-devel] Will it be "response.should_have" or "response.body.should_have"?   James Hughes
• [rspec-devel] Will it be "response.should_have" or "response.body.should_have"?   James Hughes
• [rspec-devel] Will it be "response.should_have" or "response.body.should_have"?   James Hughes
• [rspec-devel] [rspec-users] Coming Soon...   Brandon Keepers
• [rspec-devel] [ANN] rspec-ext 0.0.1   Yurii Rashkovskii
• [rspec-devel] [ rspec-Bugs-8917 ] Cannot checkout repository   Scott Taylor
• [rspec-devel] [ rspec-Bugs-8917 ] Cannot checkout repository   Scott Taylor
• [rspec-devel] [ rspec-Bugs-8917 ] Cannot checkout repository   aslak hellesoy
• [rspec-devel] [ rspec-Patches-7461 ] [PATCH] Contexts don't call Module::included when they include a module   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8366 ] Structure for library specs in rspec_on_rails   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8366 ] Structure for library specs in rspec_on_rails   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8371 ] Mocking complaining about wrong number of arguments (odd)   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8371 ] Mocking complaining about wrong number of arguments (odd)   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8241 ] "no id given" if controller method does not exist   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8241 ] "no id given" if controller method does not exist   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8240 ] Cryptic error message when no controller_name   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8027 ] should_change works but should_not_change appears not to.   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8392 ] should_have_tag :content => true fails to match correctly   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8392 ] should_have_tag :content => true fails to match correctly   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-6896 ] should_render fails with respond_to   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-7805 ] Stubs aren't being removed from modules   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8218 ] heckle_runner.rb doesn't work with heckle >= 1.2.0   noreply at rubyforge.org
• [rspec-devel] [ rspec-Patches-6720 ] [PATCH] ActiveRecord has_many :through and has_and_belongs_to_many break 'should'   noreply at rubyforge.org
• [rspec-devel] [ rspec-Patches-8332 ] [PATCH] Update views documentation   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8393 ] [PATCH?] Could an unhelpful error message be improved?   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8393 ] [PATCH?] Could an unhelpful error message be improved?   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8393 ] [PATCH?] Could an unhelpful error message be improved?   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8149 ] specify_negatively   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8414 ] Place for Rails specs for library code, not M/V/C component.   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8414 ] Place for Rails specs for library code, not M/V/C component.   noreply at rubyforge.org
• [rspec-devel] [ rspec-Documentation-6897 ] better explanation about should_render   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8424 ] more integrated email spec'ing support   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8126 ] Nested specify blocks   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8126 ] Nested specify blocks   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8126 ] Nested specify blocks   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8126 ] Nested specify blocks   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-7344 ] Failing spec in HTML formatter   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-7344 ] Failing spec in HTML formatter   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8484 ] should_receive with blocks and cardinality   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8484 ] should_receive with blocks and cardinality   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8484 ] should_receive with blocks and cardinality   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-7613 ] context#include should add constants into the context   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-7613 ] context#include should add constants into the context   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-7613 ] context#include should add constants into the context   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-7613 ] context#include should add constants into the context   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-7613 ] context#include should add constants into the context   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-7613 ] context#include should add constants into the context   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8507 ] change #include to some other name   noreply at rubyforge.org
• [rspec-devel] [ rspec-Patches-8509 ] Enhance controller docs   noreply at rubyforge.org
• [rspec-devel] [ rspec-Patches-8509 ] Enhance controller docs   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-5485 ] proc#should_raise and proc#should_not_raise output   noreply at rubyforge.org
• [rspec-devel] [ rspec-Patches-8509 ] Enhance controller docs   noreply at rubyforge.org
• [rspec-devel] [ rspec-Patches-8509 ] Enhance controller docs   noreply at rubyforge.org
• [rspec-devel] [ rspec-Documentation-8509 ] Enhance controller docs   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8371 ] Mocking complaining about wrong number of arguments (odd)   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-7636 ] drbspec not managing db connections appropriately   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-7344 ] Failing spec in HTML formatter   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8371 ] Mocking complaining about wrong number of arguments (odd)   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8371 ] Mocking complaining about wrong number of arguments (odd)   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8507 ] change #include to some other name   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8507 ] change #include to some other name   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8509 ] Enhance controller docs   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-6178 ] should_return   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-5485 ] proc#should_raise and proc#should_not_raise output   noreply at rubyforge.org
• [rspec-devel] [ rspec-Documentation-8572 ] Old Google result   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8646 ] Context Runner does not report on Non standard exceptions and return a 0 return code   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8646 ] Context Runner does not report on Non standard exceptions and return a 0 return code   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8646 ] Context Runner does not report on Non standard exceptions and return a 0 return code   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8646 ] Context Runner does not report on Non standard exceptions and return a 0 return code   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8654 ] Aspects   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8654 ] Aspects   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8696 ] --order option   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8654 ] Aspects   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8698 ] --snippet option   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8654 ] Aspects   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8126 ] Nested specify blocks   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8126 ] Nested specify blocks   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8750 ] should[_not]_include backwards compatibility between 0.8.0-RC1 and 0.7.5.1 broken   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8750 ] should[_not]_include backwards compatibility between 0.8.0-RC1 and 0.7.5.1 broken   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8771 ] Spec::Mocks::BaseExpectation#with converts hash params to array of arrays with #collect   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8771 ] Spec::Mocks::BaseExpectation#with converts hash params to array of arrays with #collect   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8783 ] auto generate spec names from last expectation   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8786 ] 0.8.0-RC1 rake tasks seems to behave unobvious if test database does not exist   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8783 ] auto generate spec names from last expectation   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8789 ] --line and --spec not working when the context has parenhesis in the name   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8783 ] auto generate spec names from last expectation   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8815 ] should_receive(:method).with('val') should report the arg it actually received instead of saying it received it 0 times.   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8815 ] should_receive(:method).with('val') should report the arg it actually received instead of saying it received it 0 times.   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8786 ] 0.8.0-RC1 rake tasks seems to behave unobvious if test database does not exist   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8843 ] Broken link to rails svn repository, on website   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8843 ] Broken link to rails svn repository, on website   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8139 ] & quot; not implemented& quot; message for specs yet to be implemented   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8139 ] & amp; quot; not implemented& amp; quot; message for specs yet to be implemented   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8139 ] & amp; amp; quot; not implemented& amp; amp; quot; message for specs yet to be implemented   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8139 ] & amp; amp; quot; not implemented& amp; amp; quot; message for specs yet to be implemented   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8887 ] Should have RJS matches DOM IDs as substrings   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8887 ] Should have RJS matches DOM IDs as substrings   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8897 ] Error when mixing controller spec with/without integrated views and using template system other than rhtml   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8789 ] --line and --spec not working when the context has parenhesis in the name   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8789 ] --line and --spec not working when the context has parenthesis in the name   noreply at rubyforge.org
• [rspec-devel] [ rspec-Patches-8132 ] [PATCH] RSpec breaks "rake db:sessions:create" in a rails project that has the rspec_on_rails plugin   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8905 ] Bug w/ spec --drb in RC1 0.8.0   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8914 ] [Controller] stubbed render_file on @template causes problems with rails -r6253   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8914 ] [Controller] stubbed render_file on @template causes problems with rails -r6253   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8914 ] [Controller] stubbed render_file on @template causes problems with rails -r6253   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8914 ] [Controller] stubbed render_file on @template causes problems with rails -r6253   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8917 ] Cannot checkout repository   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8905 ] Bug w/ spec --drb in RC1 0.8.0   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8905 ] Bug w/ spec --drb in RC1 0.8.0   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8917 ] Cannot checkout repository   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8905 ] Bug w/ spec --drb in RC1 0.8.0   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8786 ] 0.8.0-RC1 rake tasks seems to behave unobvious if test database does not exist   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8917 ] Cannot checkout repository   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8786 ] 0.8.0-RC1 rake tasks seems to behave unobvious if test database does not exist   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8925 ] Documentation bug in 0.8.0RC1 rspec website   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8928 ] rspec_on_rails 0.8.0-RC1 controller tests make double call to setup_with_fixtures   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8928 ] rspec_on_rails 0.8.0-RC1 controller tests make double call to setup_with_fixtures   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8925 ] Documentation bug in 0.8.0RC1 rspec website   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8925 ] Documentation bug in 0.8.0RC1 rspec website   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8925 ] Documentation bug in 0.8.0RC1 rspec website   noreply at rubyforge.org
• [rspec-devel] [ rspec-Bugs-8928 ] rspec_on_rails 0.8.0-RC1 controller tests make double call to setup_with_fixtures   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-8509 ] Enhance controller docs   noreply at rubyforge.org
• [rspec-devel] [ rspec-Feature Requests-6508 ] Proper stacktrace for mocks   noreply at rubyforge.org

Last message date: Wed Feb 28 14:30:30 EST 2007
Archived on: Wed Feb 28 14:30:36 EST 2007

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...