search for: nulldb

...''s Objects on Rails for having a better rails app and not forcing to some conventions and practices which are REALLY common in rails development and will lead to bad OO design and poor dependency management and maintainability of the application. But I have some problems setting up the nulldb in my tests for having fast specs without depending on ActiveRecord so tightly. I posted my question in StackOverflow few days ago and I didn''t receive any response yet. I really appreciate your help and guidance on this issue. you can find the question here --> http://stackoverflow...

...dows 8 Metro and RIA services or eclipse and EJB 2.0 for masochistic fun) ERROR: Could not find a valid gem ''activerecord-sqlite3-adapter'' (>= 0) in any repository ERROR: Possible alternatives: activerecord-jdbcsqlite3-adapter, activerecord-sqlserver-adapter, activerecord-nulldb-adapter, activerecord-simpledb-adapter, activerecord-dbslayer-adapter and as I''m hoping to get to a point where I can see a continuation of the tutorial with a toy app, I''m about ready to throw up my hands in despair thinking this is just a sign of more to come here.: =>...

Hi all, I am using story runner with webrat, but I am not sure how to incorporate stub_model into my tests. The webrat steps only care about the user interface and have nothing to say about interaction with the database. Following Ben Mabey, I have a line in my story like: "When clicks the Create button" And a step like: When "clicks the $button button" do |button|

It took a while, but now I an totally convinced that controller specs should not access the database and stub as much as possible. I''m committed to that style of writing, yet from time to time I incidentally allow it to happen. Is there a way to err on the safe side and have RSpec throw an error every time a controller spec attempts to access the database? And does it sound like a good