diff options
| author | Xavier Noria <fxn@hashref.com> | 2011-06-23 18:08:11 +0200 |
|---|---|---|
| committer | Xavier Noria <fxn@hashref.com> | 2011-06-23 18:08:11 +0200 |
| commit | 1f505a8ef21a300c22e4c6a3cc4d3bf4cf1853de (patch) | |
| tree | e6d3457116b06dac44554b4100ff2ddfd13a64ee /railties/guides/source/performance_testing.textile | |
| parent | d49622a1f211a036283dcd094c9da0da3bb39fa8 (diff) | |
| parent | 06fe01a337ccf7f44bbaf272eddac284f80dcadb (diff) | |
| download | rails-1f505a8ef21a300c22e4c6a3cc4d3bf4cf1853de.tar.gz rails-1f505a8ef21a300c22e4c6a3cc4d3bf4cf1853de.tar.bz2 rails-1f505a8ef21a300c22e4c6a3cc4d3bf4cf1853de.zip | |
Merge branch 'master' of git://github.com/lifo/docrails
Diffstat (limited to 'railties/guides/source/performance_testing.textile')
| -rw-r--r-- | railties/guides/source/performance_testing.textile | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/railties/guides/source/performance_testing.textile b/railties/guides/source/performance_testing.textile index a4187a3135..dbe6f97f5c 100644 --- a/railties/guides/source/performance_testing.textile +++ b/railties/guides/source/performance_testing.textile @@ -151,7 +151,7 @@ Performance tests can be run in two modes: Benchmarking and Profiling. h5. Benchmarking -Benchmarking makes it easy to quickly gather a few metrics about each test tun. By default, each test case is run +4 times+ in benchmarking mode. +Benchmarking makes it easy to quickly gather a few metrics about each test tun. By default, each test case is run *4 times* in benchmarking mode. To run performance tests in benchmarking mode: @@ -161,7 +161,7 @@ $ rake test:benchmark h5. Profiling -Profiling allows you to make an in-depth analysis of each of your tests by using an external profiler. Depending on your Ruby interpreter, this profiler can be native (Rubinius, JRuby) or not (MRI, which uses RubyProf). By default, each test case is run +1 time+ in profiling mode. +Profiling allows you to make an in-depth analysis of each of your tests by using an external profiler. Depending on your Ruby interpreter, this profiler can be native (Rubinius, JRuby) or not (MRI, which uses RubyProf). By default, each test case is run *once* in profiling mode. To run performance tests in profiling mode: |