- 18 May, 2016 1 commit
-
-
Adam Butler authored
-
- 21 Apr, 2016 2 commits
-
-
Alejandro Rodríguez authored
-
Alejandro Rodríguez authored
Using the syntax proposed in #13829 [project_reference]%(milestone_id | milestone_name) to get a link to the referred milestone.
-
- 06 Apr, 2016 1 commit
-
-
Gabriel Mazetto authored
-
- 20 Mar, 2016 1 commit
-
-
Douwe Maan authored
-
- 13 Mar, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
The user has the rights of a public user execpt it can never create a project, group, or team. Also it cant view internal projects.
-
- 10 Mar, 2016 1 commit
-
-
Yorick Peterse authored
The rationale for this can be found in https://gitlab.com/gitlab-org/gitlab-ce/issues/13718 but in short the benchmark suite no longer serves a good purpose now that we have proper production monitoring in place. Fixes gitlab-org/gitlab-ce#13718
-
- 14 Jan, 2016 2 commits
-
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
- 24 Dec, 2015 1 commit
-
-
Douwe Maan authored
-
- 01 Dec, 2015 1 commit
-
-
Douwe Maan authored
-
- 05 Oct, 2015 2 commits
-
-
Yorick Peterse authored
This ensures that blocks defines using "benchmark_subject" have access to methods defined using let/subject & friends.
-
Yorick Peterse authored
This class method can be used in "describe" blocks to specify the subject of a benchmark. This lets you write: benchmark_subject { Foo } instead of: benchmark_subject { -> { Foo } }
-
- 02 Oct, 2015 1 commit
-
-
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.
-
- 06 Sep, 2015 1 commit
-
-
Stan Hu authored
Also adds the ability to run rspecs with relative_url_defined on the enviornment. For example: RELATIVE_URL_ROOT=/gitlab rspec Closes #1728
-
- 28 Jul, 2015 1 commit
-
-
Robert Speicher authored
-
- 22 Jul, 2015 2 commits
-
-
Robert Speicher authored
-
Robert Speicher authored
-