- 02 4月, 2014 1 次提交
-
-
由 Matthew Draper 提交于
Restore the 4.0 behaviour for 'sqlite3:///', but deprecate it. We'll change to the absolute-path interpretation in 4.2. The current "correct" spellings for in-memory, relative, and absolute URLs, respectively, are: sqlite3::memory: sqlite3:relative/path sqlite3:/full/path Substantially reverses/defers fbb79b51. Uncovered by @guilleiguaran while investigating #14495, though that sounds like a different issue.
-
- 16 3月, 2014 1 次提交
-
-
由 Eric Steele 提交于
Allows fixtures to use their $LABEL as part of a string instead of limiting use to the entire value. mark: first_name: $LABEL username: $LABEL1973 email: $LABEL@$LABELmail.com users(:mark).first_name # => mark users(:mark).username # => mark1973 users(:mark).email # => mark@markmail.com
-
- 09 2月, 2014 1 次提交
-
-
由 Mikko Johansson 提交于
-
- 08 1月, 2014 1 次提交
-
-
由 Roderick van Domburg 提交于
Fixes: #11524
-
- 16 11月, 2013 1 次提交
-
-
由 Ryan Davis 提交于
Fix bad test order dependency between LoadAllFixturesTest#test_all_there and FoxyFixturesTest#test_ignores_belongs_to_symbols_if_association_and_foreign_key_are_named_the_same
-
- 07 10月, 2013 1 次提交
-
-
由 Federico Ravasio 提交于
Stubbing ENV[] is not safe outside MRI. At some point after the stubbing has occurred a backtrace is printed to the ActiveSupport warning log: there Rubinius accesses ENV['RBX_NOCOLOR'] to determine if it should print the backtrace with colors or not, causing the stub to fail. Other implementations might access ENV in a different way too, we just can't predict it. The only thing we can do here is to actually set the ENV with what we want and restore it afterwards.
-
- 10 9月, 2013 2 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 08 9月, 2013 1 次提交
-
-
由 Jeremy Kemper 提交于
-
- 07 9月, 2013 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 27 8月, 2013 1 次提交
-
-
由 wangjohn 提交于
Allows you to change your configuration for calls to `table_name_prefix`, `table_name_suffix`, and `pluralize_table_names`. The default configuration is still ActiveRecord::Base, but you are now able to change the configuration easily.
-
- 25 8月, 2013 1 次提交
-
-
由 wangjohn 提交于
Also, constantizing the default_fixture_model_name when it gets loaded in from the file. Later, when the class_name is passed to a new FixtureSet, a deprecation warning will occur if the class_name is a string.
-
- 06 8月, 2013 1 次提交
-
-
由 Kassio Borges 提交于
-
- 02 7月, 2013 1 次提交
-
-
由 Yves Senn 提交于
-
- 15 6月, 2013 1 次提交
-
-
由 Yves Senn 提交于
As you can also configure your database connection using `ENV["DATABASE_URL"]`, the fixture setup can't reply on the `.configurations` Hash. As the fixtures are only loaded when ActiveRecord is actually used (`rails/test_help.rb`) it should be safe to drop the check for an existing configuration.
-
- 22 3月, 2013 1 次提交
-
-
- 10 3月, 2013 1 次提交
-
-
由 Ben Moss 提交于
This allows end-users to have a `connection` method on their models without clashing with ActiveRecord internals.
-
- 18 1月, 2013 2 次提交
-
-
由 Guillermo Iguaran 提交于
This reverts commit 637a7d9d, reversing changes made to 5937bd02.
-
由 robertomiranda 提交于
-
- 08 10月, 2012 1 次提交
-
-
由 Alexey Muranov 提交于
Rename `ActiveRecord::Fixtures` class to `ActiveRecord::FixtureSet`. Instances of this class normally hold a collection of fixtures (records) loaded either from a single YAML file, or from a file and a folder with the same name. This change make the class name singular and makes the class easier to distinguish from the modules like `ActiveRecord::TestFixtures`, which operates on multiple fixture sets, or `DelegatingFixtures`, `::Fixtures`, etc., and from the class `ActiveRecord::Fixture`, which corresponds to a single fixture.
-
- 27 4月, 2012 1 次提交
-
-
由 Jon Leighton 提交于
-
- 23 3月, 2012 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 12 2月, 2012 1 次提交
-
-
由 Vishnu Atrai 提交于
This reverts commit 7381596e.
-
- 11 2月, 2012 1 次提交
-
-
由 Karunakar (Ruby) 提交于
-
- 26 1月, 2012 1 次提交
-
-
由 Sergey Nartimov 提交于
-
- 04 1月, 2012 2 次提交
-
-
由 Jeremy Kemper 提交于
create_fixtures should accept symbol keys for custom table -> class mappings. Fixes an unintended regression.
-
由 Jeremy Kemper 提交于
setup_fixture_accessors should accept symbols for table names. Fixes an unintended (and untested) regression.
-
- 30 12月, 2011 2 次提交
-
-
由 Alexey Muranov 提交于
-
由 Alexey Muranov 提交于
Test using fixtures with random names and model names, that is not following naming conventions but using set_fixture_class instead. It is expected that the table name be defined in the model, but this is not explicitly tested here. This will need to be fixed.
-
- 27 12月, 2011 1 次提交
-
-
由 Alexey Muranov 提交于
Make sure the table name of a model is reset in a test case after assigning ActiveRecord::Base.table_name_prefix and ActiveRecord::Base.table_name_suffix.
-
- 25 12月, 2011 1 次提交
-
-
由 Sergey Nartimov 提交于
-
- 23 12月, 2011 1 次提交
-
-
由 Jon Leighton 提交于
This reverts commit f8e484d0, reversing changes made to fa5adfb1. Reason: broke the postgres tests.
-
- 22 12月, 2011 1 次提交
-
-
由 Alexey Muranov 提交于
Make sure the table name of a model is reset in a test case after assigning ActiveRecord::Base.table_name_prefix and ActiveRecord::Base.table_name_suffix. This was somebody else's test case, so an independent opinion on the change can be helpful.
-
- 11 12月, 2011 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 10 10月, 2011 1 次提交
-
-
由 Jon Leighton 提交于
Use broken YAML that will fail with Syck as well as Psych. Fixes test_broken_yaml_exception in fixtures_test.rb on Ruby 1.8.7. Cherry-pick from 3-1-stable: b8d46924
-
- 06 10月, 2011 1 次提交
-
-
由 Jeremy Kemper 提交于
You can use multiple databases in your tests without disabling transactional fixtures.
-
- 02 9月, 2011 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 14 8月, 2011 1 次提交
-
-
由 Jon Leighton 提交于
Quote these dates to prevent intermittent test failure. Suppose local time is 00:50 GMT+1. Without the quoting, the YAML parser would parse this as 00:50 UTC, into the local time of 01:50 GMT+1. Then, it would get written into the database in local time as 01:50. When it came back out the UTC date from the database and the UTC date of two weeks ago would be compared. The former would be 23:50, and the latter would be 00:50, so the two dates would differ, causing the assertion to fail. Quoting it prevents the YAML parser from getting involved.
-
- 04 8月, 2011 1 次提交
-
-
由 Jon Leighton 提交于
Quote these dates to prevent intermittent test failure. Suppose local time is 00:50 GMT+1. Without the quoting, the YAML parser would parse this as 00:50 UTC, into the local time of 01:50 GMT+1. Then, it would get written into the database in local time as 01:50. When it came back out the UTC date from the database and the UTC date of two weeks ago would be compared. The former would be 23:50, and the latter would be 00:50, so the two dates would differ, causing the assertion to fail. Quoting it prevents the YAML parser from getting involved.
-
- 08 7月, 2011 1 次提交
-
-
由 Akira Matsuda 提交于
-