Continue reading »]]> Speeding up you tests with Spork is very common when developping Rails applications.

What Spork do is preloading your application in a server and copies a fork of that server whenever you run tests.

It avoids reloading all the rails stack !! That is great !!!

But the problem I ran into is that I wanted to be able to

• reload my application files
• and keep cache_classes = true

That is why I like ruby and rails (and great coders there ! ). What I simply did :

1. Reading and understanding the rails initialize process  (especially these lines engine.rb and finisher.rb )
2. Adding these small pieces of code in my prefork block with Spork trap method 
3. trap eager loading in my prefork block like below

  require 'rails/application'
 
  # Use of https://github.com/sporkrb/spork/wiki/Spork.trap_method-Jujutsu
  Spork.trap_method(Rails::Application, :reload_routes!)
  Spork.trap_method(Rails::Application::RoutesReloader, :reload!)
 
  require 'rails/mongoid'
  Spork.trap_class_method(Rails::Mongoid, :load_models)
 
  # Prevent main application to eager_load in the prefork block (do not load files in autoload_paths)
  Spork.trap_method(Rails::Application, :eager_load!)
 
  # Below this line it is too late...
  require File.expand_path("../../config/environment", __FILE__)
  # Load all railties files
  Rails.application.railties.all { |r| r.eager_load! }

My own benefits : specs runs faster than setting cache_classes = false

You need small explanation of what I’ve done !

  Spork.trap_method(Rails::Application, :eager_load!)
  require File.expand_path("../../config/environment", __FILE__)
  Rails.application.railties.all { |r| r.eager_load! }

First, we prevent Rails::Application to loads files in the application autoload_paths such as app/models, app/controllers etc …

  Spork.trap_method(Rails::Application, :eager_load!)

Second, we load the rails stack :

  require File.expand_path("../../config/environment", __FILE__)

Last, we eager load all the engines :

  Rails.application.railties.all { |r| r.eager_load! }

Doing that we can make change in our models and avoid restarting spork.

Why don’t I just set cache_classes to false ?

Because the ActiveSupport::Dependencies.mechanism is set to :require and not :load

All application files are required and not just loaded (spork required them just after forking, not before).
This trick could resolve some inconsistencies in your application (such as already defined constant and else …)

Continue reading »]]> Hello,

It’s been a while when I last updated this blog. It seems that Rspec 2 can not use fixtures from Activerecord 2.3.x !

Impossible ? Not really, and thanks to ruby it was possible for me.

Let’s describe the background :

First of all, I had a gem built on jeweler that uses ActiveSupport::TestCase and ActiveRecord::Fixtures exactly implemented like in Rails
But one day, I decided to switch to RSpec (jeweler (1.5.2) uses as of my writing rspec ~> 2.3.0)

The conversion of test_* to “it” syntax was very quick and easy but loading fixtures was not !!!
So here is my implementation if you want to know how can this be possible :

# spec/spec_helper.rb
# .... some stuff ...
 require 'activerecord'
module  MyExtensions
  def self.extended(base)
    class << base # Beginning of Proxy
      def subclass_with_fixtures(*args,&block)
        child = subclass_without_fixtures(*args,&block)
        child.module_eval do
          include ActiveSupport::Callbacks
          define_callbacks :setup, :teardown
          include ActiveRecord::TestFixtures
 
          self.fixture_path = File.expand_path("../db/fixtures",__FILE__)
          self.use_instantiated_fixtures = false
          self.use_transactional_fixtures = true
          self.set_fixture_class :categories => 'Categorie'
 
          def run_in_transaction?
            true
          end
        end
        child
      end # End of method chain subclass_with_fixtures
      alias_method_chain :subclass, :fixtures
    end # End of Proxy
  end # End of extended
end # End of MyExtensions
 
RSpec::Core::ExampleGroup.extend(MyExtensions)
RSpec.configure do |config|
 
  config.after(:each) do
    run_callbacks :teardown, :enumerator => :reverse_each
  end
 
  config.before(:each) do
    run_callbacks :setup
  end
 
end

In my fixtures :

  # spec/db/fixtures/posts.yml
  a_post:
    title: "My first post"

Now when I want to load fixtures :

# spec/post_spec.rb
describe "Post" do
  before(:all) do
   self.class.fixtures :posts
  end
 
  it "should not save without a title" do
     post = posts(:a_post)
    post.title = nil
    post.save.should_not be_true
  end
end

Maybe, a better way can be found … if so please inform me !!!

Continue reading »]]> If you as us in my company use self signed certificate and ran into an OpenSSL::SSL::SSLError when using httpclient gem.

Here is how to bypass ssl certificate verification :

The issue :

require 'rubygems'
require 'httpclient'
 
client = HTTPClient.new
url = "https://www.server1.com"
client.get(url)
at depth 1 - 19: self signed certificate in certificate chain
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient/session.rb:247:in `connect'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient/session.rb:247:in `ssl_connect'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient/session.rb:639:in `connect'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient/timeout.rb:128:in `timeout'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient/session.rb:631:in `connect'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient/session.rb:522:in `query'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient/session.rb:147:in `query'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient.rb:953:in `do_get_block'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient.rb:765:in `do_request'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient.rb:848:in `protect_keep_alive_disconnected'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient.rb:764:in `do_request'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient.rb:666:in `request'
	from /home/hery/.gem/ruby/1.8/gems/httpclient-2.1.5.2/lib/httpclient.rb:591:in `get'
	from (irb):5

Solution :

client.ssl_config.verify_mode = OpenSSL::SSL::VERIFY_NONE
client.get(url)

Continue reading »]]> I am proud to have published my first useful ruby gem.
It is called gettext_column_mapping, you can check out the code in my github repository.
I already released it as a gem through gemcutter/rubygems

It is based upon Masao Mutoh (gettext and gettext_active_record) and Michael Grosser (fast_gettext and gettext_i18n_rails) works.

Thanks to them

History

In my company we need a mean to translate bad written fields/table name in our database. Why ? because our applications are internationalized and we need to have cleaner name than “libelle” (the french word standing for label) to send to translators.

We also have some “constants” name saved in our tables so we need to translate them.

Then started this library a year ago.

Formerly, it was a library that depends on Rails … But I decided that it ccould be nice if it reaches these requirements :

• Use of Rubygem to spread it more easily
• Must be Rails agnostic
• Can use either mutoh’s gettext or grosser/fast_gettext
• Can be implemented easily on rails 2.3.x and 3.0 or other ruby web framework
• Can have some built-in configurable rake tasks

All is done!

But now I would like to improve this gems (API, tests, documentation, implementation) , so if someone who reads this post can help … I must remind you that this project is open source. Partly, it has been developped at work but I burnt most many hours of my sparetime than at work

TODO ?

• other database implementation (only mysql for now)
• ORM agnosticism ?
• More testing
• More documentation
• Rails < 2.3 compatibility backward
• … and so many

Try it and give me feedback

Continue reading »]]> Hi all,
A simple trick I want to share with you if you are using Bundler (or rails 3)
It matters if you want to install wirble gem in your workstation but not in your server

Sometimes, you want to include some gem that are not mandatory for your application to run but you want to use in your workstation. E.g wirble, awesome_print etc … or other debugging tools

Just write something like this in your Gemfile

# Gemfile
if File.exist?(file = File.expand_path('../myGemfile',__FILE__))
  instance_eval(File.read(file))
end

Now in your myGemfile

# myGemfile
gem 'wirble'
gem 'awesome_print'

That’s all! You can now require ‘wirble’ or ‘awesome_print’ in your rails console