- 19 Aug, 2016 1 commit
-
- 09 Aug, 2016 1 commit
-
-
Stan Hu authored
This is in preparation to address the DB load caused by the counting in gitlab-com/infrastructure#303.
-
- 21 Jul, 2016 5 commits
-
-
Grzegorz Bizon authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 12 Jul, 2016 2 commits
-
-
Lin Jen-Shin authored
It turns out they are different: builds.success.latest.first and builds.latest.success.first If we put success first, that latest would also filter via success, and which is what we want here.
-
Lin Jen-Shin authored
-
- 07 Jul, 2016 2 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
-
- 04 Jul, 2016 1 commit
-
-
Patricio Cano authored
-
- 30 Jun, 2016 1 commit
-
-
Z.J. van de Weg authored
-
- 08 Jun, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 07 Jun, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 03 Jun, 2016 3 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 16 May, 2016 1 commit
-
-
James Lopez authored
-
- 05 May, 2016 1 commit
-
-
James Lopez authored
-
- 04 May, 2016 1 commit
-
-
James Lopez authored
refactored some namespace stuff and fixed project tree restorer spec. also removing controller so that it belongs to the UI MR
-
- 01 May, 2016 1 commit
-
-
Connor Shea authored
This allows the removal of the monkey patch from this commit: 47ff1c56 It'll also make it slightly easier to upgrade to 3.5.0 later. Changelog: https://github.com/rspec/rspec-rails/blob/master/Changelog.md#340--2015-11-11
-
- 30 Mar, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 29 Mar, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 15 Mar, 2016 1 commit
-
-
Timothy Andrew authored
1. Allow subscribing (the current user) to a label - Refactor the `Subscription` coffeescript class - The main change is that it accepts a container, and conducts all DOM queries within its scope. We need this because the labels page has multiple instances of `Subscription` on the same page. 2. Creating an issue or MR with labels notifies users subscribed to those labels - Label `has_many` subscribers through subscriptions. 3. Adding a label to an issue or MR notifies users subscribed to those labels - This only applies to subscribers of the label that has just been added, not all labels for the issue.
-
- 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
-
- 09 Mar, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 25 Jan, 2016 1 commit
-
-
Robert Speicher authored
-
- 30 Nov, 2015 1 commit
-
-
Valery Sizov authored
-
- 05 Oct, 2015 1 commit
-
-
Kamil Trzcinski authored
-
- 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.
-
- 09 Sep, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 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
-
- 14 Jul, 2015 1 commit
-
-
Robert Speicher authored
These tools must be loaded before our regular Rails environment.
-
- 30 Jun, 2015 2 commits
-
-
Robert Speicher authored
There were several specs that were failing when run by themselves. - Use the `helper` object, as per RSpec 3 standards - Use `assign` to assign instance variables that helpers expect - Add `StubConfiguration` support module
-
Robert Speicher authored
Just for consistency with our Capybara, DatabaseCleaner, WebMock, etc. setups.
-
- 22 Jun, 2015 1 commit
-
-
Robert Speicher authored
This fixes spec/mailers/notify_spec Also only require email_spec in the one place it's used
-
- 10 Jun, 2015 2 commits
-
-
Robert Speicher authored
-
Robert Speicher authored
-
- 26 Apr, 2015 1 commit
-
-
Robert Speicher authored
-