Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Faker refactored. Cleaner. Faster.

This branch is 0 commits ahead and 0 commits behind master

Fetching latest commit…

Cannot retrieve the latest commit at this time

README.rdoc

ffaker

Fast Faker == Faker refactored. rubygems.org/gems/ffaker

Faker

A port of Perl's Data::Faker library that generates fake data. rubygems.org/gems/faker

Usage

require 'ffaker'
Faker::Name.name => "Christophe Bartell"
Faker::Internet.email => "kirsten.greenholt@corkeryfisher.info"

Ffaker / Faker

Faker and Ffaker APIs are mostly the same, although the API on ffaker keeps growing with its users additions. In general, the only difference is that you need to:

gem install ffaker

and then

require 'ffaker'

instead of “faker” with only one f.

Faster? does it really matter ?

Ffaker was initially written in an effort to speed up a slow spec suite. Bear in mind, if your spec suite is slow, chances are the generation of random data will not account for much of the run time.

Since then, the original faker gem has become faster (at the moment it did not seem it was mantained). Nevertheless, ffaker is still about 20x faster than faker.

$ cat scripts/benchmark.rb

# ...
N = 10_000

Benchmark.bm do |rep|
  rep.report("generating #{ N } names") do
    N.times do
      Faker::Name.name
    end
  end
end
  • ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2011.03

    generating 10000 names (faker 0.9.5)  1.500000   0.000000   1.500000 (  1.506865)
    generating 10000 names (ffaker 1.5.0)  0.070000   0.000000   0.070000 (  0.067526)
  • ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-linux]

    generating 10000 names (faker 0.9.5)  1.030000   0.020000   1.050000 (  1.046116)
    generating 10000 names (ffaker 1.7.0)  0.040000   0.000000   0.040000 (  0.045917)

Contributors

TODO

  • Even though the API is pretty simple, better rdoc documentation would not hurt.

Note on Patches/Pull Requests

  • Fork the project.

  • Make your feature addition or bug fix.

  • Add tests for it. This is important so I don't break it in a future version unintentionally.

  • Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)

  • Send me a pull request. Bonus points for topic branches.

Copyright

Copyright © 2010 Emmanuel Oga. See LICENSE for details. Copyright © 2007 Benjamin Curtis

Something went wrong with that request. Please try again.