aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/application
Commit message (Collapse)AuthorAgeFilesLines
...
* Immediately run queued jobs in tests. Otherwise you have to explicitly drain ↵Jeremy Kemper2012-10-121-3/+3
| | | | the queue to actually deliver your emails.
* Update test locationsMike Moore2012-10-091-6/+6
| | | | | | | | | | | | | | Change the default test locations to avoid confusion around the common testing terms "unit" and "functional". Add new rake tasks for the new locations, while maintaining backwards compatibility with the old rake tasks. New testing locations are as follows: app/models -> test/models (was test/units) app/helpers -> test/helpers (was test/units/helpers) app/controllers -> test/controllers (was test/functional) app/mailers -> test/mailers (was test/functional)
* Remove duplicated testGuillermo Iguaran2012-10-091-15/+0
|
* Minor test refactoring: Use add_to_env instead of an initializerGuillermo Iguaran2012-10-091-1/+1
|
* Fix middleware cache tests enabling rack_cacheGuillermo Iguaran2012-10-051-0/+2
|
* config.action_dispatch.rack_cache should set explicitly to enable Rack::CacheGuillermo Iguaran2012-10-041-1/+10
|
* Use String#exclude? to make sure that Active Support is not loaded whenRafael Mendonça França2012-10-041-1/+1
| | | | | | | bare is true. We need to change this since coffee-rails loads ActionView that loads core_ext/array/access.
* Remove action cache related testsRafael Mendonça França2012-10-041-42/+0
|
* Make Rails.public_path return a PathnamePrem Sichanugrist2012-10-021-1/+9
|
* Provide access to the application's KeyGeneratorMichael Koziarski2012-10-011-0/+1
| | | | Available both as an env entry for rack and an instance method on Rails::Application for other uses
* Assets cache shouldn't be shared between different environmentsGuillermo Iguaran2012-09-281-1/+2
|
* Tune up Rails::Rack::Logger. Only put space between requests in development ↵Jeremy Kemper2012-09-261-7/+7
| | | | logs.
* Update asset test to match one in sprockets-railsGuillermo Iguaran2012-09-211-2/+5
|
* Use last version of sprockets-rails and syncing tests for assets.Dmitry Vorotilin2012-09-191-32/+35
|
* In development and test we drain the jobs in the same thread.Rafael Mendonça França2012-09-181-4/+4
|
* Merge pull request #7251 from rails/integrate-strong_parametersDavid Heinemeier Hansson2012-09-182-14/+22
|\ | | | | Integrate strong_parameters in Rails 4
| * Add config.action_controller.permit_all_attributes to bypass ↵Guillermo Iguaran2012-09-161-0/+22
| | | | | | | | StrongParameters protection
| * Remove configuration test for config.activerecord.whitelist_attributesGuillermo Iguaran2012-09-161-13/+0
| |
| * Remove all references to attr_accessible/protected and old ↵Guillermo Iguaran2012-09-161-1/+0
| | | | | | | | mass_assignment_sanitizers
* | Date.beginning_of_week thread local and beginning_of_week application config ↵gregolsen2012-09-181-0/+22
|/ | | | option added (default is Monday)
* Fix syntax error in assert_matchRafael Mendonça França2012-09-151-6/+6
|
* Few more warnings removed.Arun Agrawal2012-09-151-3/+3
| | | | | | | I found them when I was running warning mode on with railties See https://github.com/rails/rails/pull/3782
* Move queue classes to ActiveSupportSantiago Pastorino2012-09-142-11/+11
|
* Merge pull request #7616 from lest/null-session-forgery-protectionMichael Koziarski2012-09-131-0/+82
|\ | | | | Implement :null_session CSRF protection method
| * Implement :null_session CSRF protection methodSergey Nartimov2012-09-131-0/+82
| | | | | | | | | | | | | | | | It's further work on CSRF after 245941101b1ea00a9b1af613c20b0ee994a43946. The :null_session CSRF protection method provide an empty session during request processing but doesn't reset it completely (as :reset_session does).
* | Allow users to configure the queue for the mailersRafael Mendonça França2012-09-121-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | This allow the users to do: config.action_mailer.queue = MyQueue.new and class UsersMailer < ActionMailer::Base self.queue = MyQueue.new end
* | Use the SynchronousQueue as default in production and development.Rafael Mendonça França2012-09-121-5/+6
| | | | | | | | | | We should not let the users use the ThreadedConsumer without know about the risks
* | fixed support for DATABASE_URL for rake db tasksGrace Liu2012-09-112-0/+213
|/ | | | | | | | | | | | - added tests to confirm establish_connection uses DATABASE_URL and Rails.env correctly even when no arguments are passed in. - updated rake db tasks to support DATABASE_URL, and added tests to confirm correct behavior for these rake tasks. (Removed establish_connection call from some tasks since in those cases the :environment task already made sure the function would be called) - updated Resolver so that when it resolves the database url, it removes hash values with empty strings from the config spec (e.g. to support connection to postgresql when no username is specified).
* Rake assets:precompile shouldn't fail quietly.Dmitry Vorotilin2012-09-111-7/+4
| | | | We should show to user original issue if rake task will be aborted.
* &#39 dates back to SGML when &#x27 was introduced in HTML 4.0Kalys Osmonov2012-09-091-2/+2
|
* Remove unused require.kennyj2012-08-292-3/+0
|
* Fixes wrong test class names.kennyj2012-08-294-4/+4
|
* Raise more helpful error message on missing gemPrem Sichanugrist2012-08-241-0/+19
| | | | | | Tell people to install `activerecord-session_store` gem when it's not installed instead ofraising `NameError` on missing `ActionDispatch::Session::ActiveRecordStore`.
* Extract ActiveRecord::SessionStore from RailsPrem Sichanugrist2012-08-241-20/+0
| | | | | This functionality will be available from gem `active_record-session_store` instead.
* Fix failure on middleware/exceptions_testJosé Valim2012-08-231-10/+4
| | | | | | | The reason the test was failing was because when the test invokes `app.config`, the app is loaded and, as `eager_load` is set to true, it disables the dependency loading mechanism, so controllers that are later defined are not loaded.
* before_eager_load only runs when eager_load is trueRafael Mendonça França2012-08-221-4/+4
|
* Remove app building setup/teardown for remote ip railtie testsCarlos Antonio da Silva2012-08-211-14/+0
| | | | | These tests rely on "make_basic_app", which is a faster version that does not need to create the whole app directory structure.
* Deprecate config.threadsafe!José Valim2012-08-211-12/+9
|
* Get rid of config.preload_frameworks in favor of config.eager_load_namespacesJosé Valim2012-08-212-17/+0
| | | | | | | The new option allows any Ruby namespace to be registered and set up for eager load. We are effectively exposing the structure existing in Rails since v3.0 for all developers in order to make their applications thread-safe and CoW friendly.
* Remove allow_concurrency as a flagJosé Valim2012-08-212-3/+4
| | | | | | | | | | | | | | | | The flag was mainly used to add a Rack::Lock middleware to the stack, but the only scenario the lock is desired is in development. If you are deploying on a not-threaded server, the Rack::Lock does not provide any benefit since you don't have concurrent accesses. On the other hand, if you are on a threaded server, you don't want the lock, since it defeats the purpose of using a threaded server. If there is someone out there, running on a thread server and does want a lock, it can be added to your environment as easy as: `use Rack::Lock`
* Allow users to choose when to eager_load the application or not.José Valim2012-08-211-0/+24
| | | | | | | | | | | | | | | | | Previously, the eager load behavior was mostly coupled to config.cache_classes, however this was suboptimal since in some environments a developer may want to cache classes but not necessarily load them all on boot (for example, test env). This pull request also promotes the use of config.eager_load set to true by default in production. In the majority of the cases, this is the behavior you want since it will copy most of your app into memory on boot (which was also the previous behavior). Finally, this fix a long standing Rails bug where it was impossible to access a model in a rake task when Rails was set as thread safe.
* make assertions easier to track downAaron Patterson2012-08-071-9/+17
|
* Fix tests.Rafael Mendonça França2012-08-021-2/+2
| | | | | Since b6ab4417720e03f1551abda2f1e4bd0a392dd04e the single quotes are being escaped in the templates.
* Remove ActionDispatch::Head middleware in favor of Rack::HeadSantiago Pastorino2012-07-232-2/+8
| | | | Closes #7110 there's more work to do on rack-cache issue 69
* adding Rails::Queueing::ContainerAaron Patterson2012-07-191-5/+5
| | | | | | | | | | | | | | | This allows us to do: In your configuration: Rails.queue[:image_queue] = SomeQueue.new Rails.queue[:mail_queue] = SomeQueue.new In your app code: Rails.queue[:mail_queue].push MailJob.new Both jobs pushed to the same default queue Rails.queue.push DefaultJob.new Rails.queue[:default].push DefaultJob.new
* Remove RoutesInspector from railties, since it was moved to APCarlos Antonio da Silva2012-07-081-168/+0
| | | | | Changes introduced in 7404cda9f61e41d52ce244d60abbf598684a96c4. Fix railties build.
* Ensure jobs do not refer to the queuePaul Battley2012-07-031-0/+15
| | | | | | | | Jobs pushed to the queue should not contain a reference to it. As the queue itself cannot be marshalled, and as a consequence of checking the marshallability of all jobs in the test environment, we can now guarantee this to be the case in the test environment when using the default TestQueue implementation.
* Ensure test jobs are marshallablePaul Battley2012-07-031-8/+28
| | | | | | | | | | By marshalling and unmarshalling jobs when adding them to the test queue, we can ensure that jobs created during test runs are valid candidates for marshalling, and, thus, that they can be used with queueing backends other than the default simple in-process implementation. This will also be used in a subsequent commit to ensure that jobs pushed to the queue do not contain a reference to the queue itself.
* Track queue threading with named classesPaul Battley2012-07-031-14/+24
| | | | | | | Using an anonymous class prevented marshalling: we're not doing that yet, but the next commit will introduce this. This also provided an opportunity to improve the expressivity of the tests and to make the assertion failure messages clearer.
* Made file name and class name consistantRahul P. Chaudhari2012-07-021-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-06 00:20:55 +0000