- 28 Apr, 2017 1 commit
-
-
Dosuken shinya authored
-
- 14 Apr, 2017 1 commit
-
-
Rémy Coutable authored
This new class uses a Redis Hash instead of a Sorted Set. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 04 Apr, 2017 2 commits
-
-
Alejandro Rodríguez authored
-
mhasbini authored
-
- 17 Mar, 2017 1 commit
-
-
Rémy Coutable authored
This solves transient failures when a text contains HTML-escapable characters such as `'`. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 06 Mar, 2017 2 commits
-
-
Eric Eastwood authored
-
Eric Eastwood authored
- gl_emoji for falling back to image/css-sprite when the browser doesn't support an emoji - Markdown rendering (Banzai filter) - Autocomplete - Award emoji menu - Perceived perf - Immediate response because we now build client-side - Update `digests.json` generation in gemojione rake task to be more useful and include `unicodeVersion` MR: !9437 See issues - #26371 - #27250 - #22474
-
- 01 Mar, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 23 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 16 Feb, 2017 1 commit
-
-
Robert Schilling authored
-
- 10 Feb, 2017 1 commit
-
-
Robert Speicher authored
-
- 05 Feb, 2017 1 commit
-
-
Robert Schilling authored
-
- 05 Jan, 2017 1 commit
-
-
Robert Speicher authored
-
- 06 Dec, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 01 Dec, 2016 1 commit
-
-
Sean McGivern authored
-
- 30 Nov, 2016 3 commits
-
-
Mike Greiling authored
-
Mike Greiling authored
-
Robert Speicher authored
This is the Group equivalent of 13ad9a74
-
- 28 Nov, 2016 1 commit
-
-
Robert Speicher authored
Prior, every single test was creating four `ProjectMember` objects, each of which created one `User` record, even though each test only used _one_ of those Users, if any. Now each test only creates the single user record it needs, if it needs one. This shaves minutes off of each spec file changed here.
-
- 16 Nov, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 17 Oct, 2016 1 commit
-
-
Nick Thomas authored
The amount of precision times have in databases is variable, so we need tolerances when comparing in specs. It's better to have the tolerance defined in one place than several.
-
- 30 Sep, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 20 Jul, 2016 1 commit
-
-
Rémy Coutable authored
Handle videos in: - MD preview in notes: commit, issue/MR, MR diff - New notes in: commit, issue/MR, MR diff - Persisted notes in: commit, issue/MR, MR diff Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 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
-