BigW Consortium Gitlab

  1. 15 Dec, 2015 2 commits
  2. 14 Dec, 2015 1 commit
  3. 08 Dec, 2015 2 commits
  4. 07 Dec, 2015 2 commits
  5. 04 Dec, 2015 1 commit
  6. 03 Dec, 2015 1 commit
  7. 01 Dec, 2015 2 commits
  8. 30 Nov, 2015 1 commit
  9. 03 Nov, 2015 1 commit
  10. 14 Oct, 2015 1 commit
  11. 13 Oct, 2015 1 commit
  12. 12 Oct, 2015 3 commits
  13. 07 Oct, 2015 2 commits
  14. 05 Oct, 2015 3 commits
  15. 02 Oct, 2015 2 commits
    • Basic setup for an RSpec based benchmark suite · 19893a1c
      Yorick Peterse authored
      This benchmark suite uses benchmark-ips
      (https://github.com/evanphx/benchmark-ips) behind the scenes. Specs can
      be turned into benchmark specs by setting "benchmark" to "true" in the
      top-level describe block like so:
      
          describe SomeClass, benchmark: true do
      
          end
      
      Writing benchmarks can be done using custom RSpec matchers, for example:
      
          describe MaruTheCat, benchmark: true do
            describe '#jump_in_box' do
              it 'should run 1000 iterations per second' do
                maru = described_class.new
      
                expect { maru.jump_in_box }.to iterate_per_second(1000)
              end
            end
          end
      
      By default the "iterate_per_second" expectation requires a standard
      deviation under 30% (this is just an arbitrary default for now). You can
      change this by chaining "with_maximum_stddev" on the expectation:
      
          expect { maru.jump_in_box }.to iterate_per_second(1000)
            .with_maximum_stddev(10)
      
      This will change the expectation to require a maximum deviation of 10%.
      
      Alternatively you can use the it block style to write specs:
      
          describe MaruTheCat, benchmark: true do
            describe '#jump_in_box' do
              subject { -> { described_class.new } }
      
              it { is_expected.to iterate_per_second(1000) }
            end
          end
      
      Because "iterate_per_second" operates on a block, opposed to a static
      value, the "subject" method must return a Proc. This looks a bit goofy
      but I have been unable to find a nice way around this.
    • Don't use "rm" for cleaning tmp/builds · dbc05d4a
      Yorick Peterse authored
      If this directory were to be empty this would result in warnings being
      printed to STDERR, cluttering spec output. Doing this in Ruby fixes this
      problem (and also removes the need for shell alltogether).
  16. 21 Sep, 2015 1 commit
  17. 15 Sep, 2015 4 commits
  18. 14 Sep, 2015 2 commits
  19. 10 Sep, 2015 3 commits
  20. 09 Sep, 2015 1 commit
  21. 06 Sep, 2015 1 commit
  22. 02 Sep, 2015 1 commit
  23. 01 Sep, 2015 2 commits