2 Matching Annotations
  1. May 2022
  2. github.com github.com
    Add config.around(:all) // current behaviour is confusing, and the same as around(:each) · Issue #1031 · rspec/rspec-core
    2
    1. TylerRick 27 May 2022
      1/ It fits into existing spec based testing infrastructure nicely, including running on travis, code coverage using SimpleCov, switching between generating a profile (RubyProf), a benchmark (Benchmark::IPS) or normal test run. 2/ Some of my benchmarks do have expect clauses to validate that things are working before invoking the benchmark.

      Answering the question:

      I don't understand the point of putting it in a spec. What does that gain you over using benchmark-ips the normal way?

      good point legitimate/valid use case
    2. TylerRick 27 May 2022
      I just wanted to mention there was, IMHO, a valid use case for this. It helps add to the validity of the ticket and the design of the feature.
      legitimate/valid use case
    Visit annotations in context

    Tags

    Annotators

    URL

    github.com/rspec/rspec-core/issues/1031