similar to: self.use_instantiated_fixtures

When I install a plugin, does Rails record the version installed anywhere? Maybe I''m not doing it the "right" way, but I''ve excluded vendors from my source repository. I''d like some ''record'' of what plugins are used that is under source control. David

I''m trying to get a simple authentication system going for a small rails app. After much research, it looks like LoginEngine should do exactly what I want. Now, the documentation is somewhat confusing to me when looked at in the light of reality. There are some places that say you have to install the "engines" plugin. But, I cannot find such a beast. So, I installed the

Is there any "standard" way if I wish to use a layout with an otherwise static page? Do I have to create a controller "and everything" for this to work? Thanks David

It appears that you cannot use migrations (out of the box) with mysql 4.0.16, because when creating a table, the statement says "ENGINE=InnoDb", instead of "TYPE=InnoDB". Looking at the source code for the adapter, this appears to be hard coded. Is there any supported way to make this work with older versions of MySQL? David

Hi, The LoginEngine has been updated to 1.0.1. Notable changes: * User model now does very basic email validation * All tests now pass on both Rails 1.0 and 1.1 * Many bugs fixed! Please refer to the Engines documentation for how to update. http://www.rails-engines.org/download The subversion URL for the tag is: http://svn.rails-engines.org/login_engine/tags/rel_1.0.1 = v1.0.1 * Added

I am trying to create unit tests for my users model but when I add a test that destroys a user, that user is not available in any of the other test. If I remove the test that destroys the user all my other tests work again. All the fixtures are suppose be reloaded between tests right? Here is my testcase : require File.dirname(__FILE__) + ''/../test_helper'' class UserTest

Hi all, I get an error when testing the "store_controller_test.rb" The troublesome line is in the test below: def test_add_to_cart get :add_to_cart, :id => @version_control_book.id <<< cart = session[:cart] assert_equal @version_control_book.price, cart.total_price assert_redirected_to :action => ''display_cart'' follow_redirect

One problem I sort of always had with the ActiveRecord''s tight coupling to the SQL backend is how slow it makes the unit tests. OK, there are some ways to make it faster at a price of extra complexity (reusing the fixtures, doing a rollback in the end of the test, etc), but still - it is much slower than what I would like a unit test to be. Today I had a very simple idea (why, oh why

I am running Rails 1.1.2 with Ruby 1.82-15. My database is Postgresql. I haven''t had any problems generating models, migrations, using scaffolds, and generally building and using my application, but I haven''t been able to get testing to work. I initially just ignored the problem and kept developing, but would like to add proper testing from here on out. Currently when I type

Hi all, I''m having a bit of a problem with unit testing. I''ve simplified my models to try and get my head round it but I''m still struggling. I''m using STI and trying to write tests for the extended models (code below). I''ve written test cases for the extended models which themselves extend the test case for the parent model, so BarTest extends

Here is my products.yml version_control_book: id: 1 title: Pragmatic Version Control description: How to use version control image_url: /images/sk_svn_small.jpg price: 29.95 date_available: 2005-01-26 00:00:00 automation_book: id: 2 title: Pragmatic Project Automation description: How to automate your project

Im having trouble with Testing models. im following the tutorials in the book Agile Web Development with Rails. if i execute the code product_test.rb, i get this error: ============================================================ 1) Failure: test_update2(ProductTest) [test/unit/product_test.rb:30]: <29.95> expected but was <99.95>. 3 tests, 11 assertions, 1 failures, 0 errors

I''m trying to write a test like the one at the bottom of page 148 in Agile Rails. I''m using rails 1.0 I''ve created the fixture correctly I''m pretty sure because the test database table is being populated per the fixture. I have what I think is a simple unit test: ========= require File.dirname(__FILE__) + ''/../test_helper'' class CaseTest

I have a problem with test fixtures. The data from the fixtures is loaded into the db (MySQL) but the variables in the test cases are not present. The logfiles contain nothing looking like an error. Any hints what I could have done wrong? Or how to debug this situation? thanks Frank

FYI On the ISN vulnerability I found a really good article on Initial Sequence Numbers (ISN) vulnerability and according to this article all Linux Kernels after 1996 are not affected by this vulnerability. http://www.linuxsecurity.com/articles/security_sources_article-2968.html I found another article that stated : Operating systems that have been reported to be safe from practical attacks

I have a class Player, and a class Game. Game has two HABTM relationships to the Player table through seperate relationship tables. class Game < ActiveRecord::Base has_and_belongs_to_many :players, :uniq => true has_and_belongs_to_many :victors, :class_name => ''Player'', :uniq => true end When I add Player A to players, and Player B to victors, and save the

Hey all, I''m following along with AWDWR, specifically the unit testing. On page 148, it shows you how Test::Unit::TestCase will automatically define instance variables based on your fixtures. It doesn''t seem to actually work, though. It seems that both @artists ["beatles"]["name"] and @beatles.name are nil objects in my test, where as

Hi, It states on page 140 of Agile Web Development with Rails: Here?s the bottom line: even if a test method updates the test database, the database is put back to its default state before the next test method is run. This is important because we don?t want tests to become dependent on the results of previous tests. Well, I''ve been running into a brick wall with some functional tests

hi all, my first attempt at tests and i''m having trouble accessing the fixture values, if anyone can make it suggestions. i have news_release_test.rb, using new_releases.yml as the fixture file according to the agile book, i should be able to access the fixture properties within my test as such: assert_equal @first_test.id , @news_release.id unfortunately, i try that and get:

Hi all I want users to register on my page. To register, they only have to deliver an email and a password. Then a link with an activation token will be sent to them, and after clicking the link the user sees a page where he should fill in further details, means: a username. My model looks like this: class Member < ActiveRecord::Base validates_presence_of :username, :if =>