I found this online about MiniTest: http://www.mikeperham.com/2012/09/25/minitest-ruby-1-9s-test-framework/ Turns out, you are right. It is about randomizing the execution order of tests. You can explicitly use them like this: rake TESTOPTS=”–seed=1261″ (according to the above link).
The answer is simple: from the database. By the way – when you take a look into the source code of db:* tasks you can see that migration tasks calls schema:dump after the run desc “Migrate the database (options: VERSION=x, VERBOSE=false).” task :migrate => :environment do ActiveRecord::Migration.verbose = ENV[“VERBOSE”] ? ENV[“VERBOSE”] == “true” : true … Read more
The difference between them is that script/runner boots Rails whereas a Rake task doesn’t unless you tell it to by making the task depend on :environment, like this: task :some_useful_task => :environment do # do some useful task end Since booting Rails is expensive, it might be worth skipping if you can avoid it. Other … Read more
Tasks that don’t have a description will not show up. EDIT: Looks like DHH removed the description from Rails 3 for a few tasks to ‘cut down on noise’. rake db:setup has a note about db:reset though. http://github.com/rails/rails/commit/983815632cc1d316c7c803a47be28f1abe6698fb
If by described you mean defined, rake -W is your friend. Example: $ rake -W db:create => rake db:create /path/to/ruby/gems/1.9.1/gems/activerecord-3.1.11/lib/active_record/railties/databases.rake:39:in `block in <top (required)>’ Just found this out today 🙂
Change the file extension from .rb to .rake.
Start by creating a separate directory to hold your custom seeds – this example uses db/seeds. Then, create a custom task by adding a rakefile to your lib/tasks directory: # lib/tasks/custom_seed.rake namespace :db do namespace :seed do Dir[Rails.root.join(‘db’, ‘seeds’, ‘*.rb’)].each do |filename| task_name = File.basename(filename, ‘.rb’) desc “Seed ” + task_name + “, based on … Read more
If you define a rake task that already exists, its execution gets appended to the original task’s execution; both tasks will be executed. If you want to redefine a task you need to clear the original task first: Rake::Task[“db:test:prepare”].clear It’s also useful to note that once a task has been executed in rake, it won’t … Read more
You could do this fairly simply with refspecs. git pull origin git diff @{1}.. That will give you a diff of the current branch as it existed before and after the pull. Note that if the pull doesn’t actually update the current branch, the diff will give you the wrong results. Another option is to … Read more
These answers assume you know what a DSL is, or are familiar with Make or Ant. If that’s not the case, here’s a (perhaps grossly oversimplified answer): Rake is a tool you can use with Ruby projects. It allows you to use ruby code to define “tasks” that can be run in the command line. … Read more