Changesets can be listed by changeset number.
The Git repository is here.
- Revision:
- 98
- Log:
Initial import of Hub, an account management application.
- Author:
- adh
- Date:
- Thu Oct 19 15:18:43 +0100 2006
- Size:
- 1317 Bytes
1 | ENV["RAILS_ENV"] = "test" |
2 | require File.expand_path(File.dirname(__FILE__) + "/../config/environment") |
3 | require 'test_help' |
4 | |
5 | class Test::Unit::TestCase |
6 | # Transactional fixtures accelerate your tests by wrapping each test method |
7 | # in a transaction that's rolled back on completion. This ensures that the |
8 | # test database remains unchanged so your fixtures don't have to be reloaded |
9 | # between every test method. Fewer database queries means faster tests. |
10 | # |
11 | # Read Mike Clark's excellent walkthrough at |
12 | # http://clarkware.com/cgi/blosxom/2005/10/24#Rails10FastTesting |
13 | # |
14 | # Every Active Record database supports transactions except MyISAM tables |
15 | # in MySQL. Turn off transactional fixtures in this case; however, if you |
16 | # don't care one way or the other, switching from MyISAM to InnoDB tables |
17 | # is recommended. |
18 | self.use_transactional_fixtures = true |
19 | |
20 | # Instantiated fixtures are slow, but give you @david where otherwise you |
21 | # would need people(:david). If you don't want to migrate your existing |
22 | # test cases which use the @david style and don't mind the speed hit (each |
23 | # instantiated fixtures translates to a database query per test method), |
24 | # then set this back to true. |
25 | self.use_instantiated_fixtures = false |
26 | |
27 | # Add more helper methods to be used by all tests here... |
28 | end |