rspec-long_time_specs_profiler
Advanced tools
A RSpec 2.x formatter which shows longest time spec files.
This formatter works in only RSpec 2.x. RSpec 3.x is not supported.
Add this lines to your application's Gemfile:
group :test do
gem 'rspec-long_time_specs_profiler'
end
And then execute:
$ bundle
Or install it yourself as:
$ gem install rspec-long_time_specs_profiler
Execute rspec command with -f RSpec::LongTimeSpecsProfiler option.
$ bundle exec rspec -f RSpec::LongTimeSpecsProfiler
After tests, 10 longest time spec files are shown in your console.
If you want to show progress, please specify -f progress option as follows.
$ bundle exec rspec -f progress -f RSpec::LongTimeSpecsProfiler
You can use --profile option which specifies how many files are shown in longest time spec files.
$ bundle exec rspec -f RSpec::LongTimeSpecsProfiler --profile 20
Bug reports and pull requests are welcome on GitHub at https://github.com/ryu39/rspec-long_time_specs_profiler. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
The gem is available as open source under the terms of the MIT License.
FAQs
Unknown package
We found that rspec-long_time_specs_profiler demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.