aboutsummaryrefslogtreecommitdiffstats
path: root/actionpack/lib/action_dispatch.rb
diff options
context:
space:
mode:
authorSam Phippen <samphippen@googlemail.com>2017-06-24 15:47:59 -0400
committerSam Phippen <samphippen@googlemail.com>2017-06-24 15:47:59 -0400
commiteba361824d9eb242f186bb711ef82381ac50ef9e (patch)
tree3cfceae220ee6201dc009af02917571c1235e7f4 /actionpack/lib/action_dispatch.rb
parent8cad811b0559661df3c58528ac1e8d5a2e601d4d (diff)
downloadrails-eba361824d9eb242f186bb711ef82381ac50ef9e.tar.gz
rails-eba361824d9eb242f186bb711ef82381ac50ef9e.tar.bz2
rails-eba361824d9eb242f186bb711ef82381ac50ef9e.zip
Add an option to silence puma in system tests.
This is motivated by our usage of system test in RSpec. Puma lazily boots the first time a system test is used, but this causes some unfortunate output to appear in the middle of the user's green dots. An example of this can be seen in @derekprior's comment [here](https://github.com/rspec/rspec-rails/pull/1813#issuecomment-309252314). There are alternatives in RSpec where we attempt to intercept the puma boot and prevent the output from being made there, but that would involve some monkey patching. This seems like a cleaner solution.
Diffstat (limited to 'actionpack/lib/action_dispatch.rb')
0 files changed, 0 insertions, 0 deletions