08 Jun, 2016
6 commits
-
This reverts commit 4211de4d7a8af53111995500e4d7c225023e143c. The right way to set the subdirectory is by setting the Rack mount on config.ru or on the webserver like apache or nginx.
-
They are not even supposed to have one!
-
…of Rack, Warden and omniauth-remote-user
-
Signed off by: Daniel Miranda <danielkza2@gmail.com>
-
Signed-off-by: Heitor Reis Ribeiro <marcheing@gmail.com>
28 May, 2016
1 commit
-
The previous syntax was over complicated. This one gets the job done the same way. Signed-off-by: Rafael Reggiani Manzo <rr.manzo@gmail.com>
04 May, 2016
1 commit
-
Apparently, the ruby 2.0.0-p598 (CentOS 7 default) breaks with the code we were using. This commit replace it with a different syntax that should be reverted when CentOS 7 updates its ruby.
20 Apr, 2016
2 commits
-
It was still relying on repositories with no attributes while Repository#latest now relies on attributes to list just the public ones.
-
Unit tests cannot expects that models will always be fetched. But to make sure things are still well tested, verify the existence of a configuration, project and repository in the homepage feature.
18 Apr, 2016
3 commits
-
Signed-off-by: Heitor Reis <marcheing@gmail.com>
-
Instead of including it manually on every step that needs it. Signed-off-by: Heitor Reis <marcheing@gmail.com>
16 Apr, 2016
2 commits
-
It makes it harder for an user to mistakenly add a metric to their script that will never work. Signed-off-by: Eduardo Araújo <duduktamg@hotmail.com>
-
It will be used to verify the correctness of the Compound Metric Configuration creation metrics list. Signed-off-by: Eduardo Araújo <duduktamg@hotmail.com>
15 Apr, 2016
2 commits
-
This makes the names more intuitive for the user. Signed-off-by: Diego Araújo <diegoamc@protonmail.ch>
-
As we are using multiple cache fragments for one action, we need to specify action_suffixes so rails create different keys for each fragment. Signed-off-by: Rafael Reggiani Manzo <rr.manzo@protonmail.com>
13 Apr, 2016
2 commits
-
The acceptance test has been refactored accordingly and got more extended to untested features.
-
It now has to click first on the dorpdown.
11 Apr, 2016
2 commits
-
The repository/notify_push feature was making post request directly using Rack::Test methods, which is not optimal when we have Capybara to handle all the driver setup and flexibility for us. Change it to use Capybara methods, and fix all the steps accordingly. To make things easier, add some helper methods to deal with headers in different drivers. Also fix a small clarity issue in the notify_push unity tests that also have to set headers.
-
Ensure webhook requests are only accepted after proper verification of expected headers, repository address and branch, using the newly implemented library. To that effect, split up the logic to extract that information from requests to it's own class, and use it in the notify_push action. Also, add factories to make better testing of the notify_push action possible, such as a factory similar to a real request from Gitlab, and one for the Kalibro Client repository on Gitlab. Adding other hook providers should be quite a lot easier after this is applied.
04 Apr, 2016
1 commit
-
A bug in notify_push was missed due to CSRF protection being disabled in the test environment. Fix that by adding a tag that can enabled it in some features. We might eventually want to enable it for all acceptance tests to make sure other cases like this don't show up.
22 Feb, 2016
2 commits
-
There were outdated tests that did not update from the deprecated 'Average' aggregation form to 'Mean'. Fix that, while simultaneously refactoring the configuration creation and repository processing features, into a single 'golden path' that tests boths, ensuring a very common user task works as expected. Signed-off-by: Daniel Miranda <danielkza2@gmail.com>
-
It previously kept running forever if the processing never succeeded. Signed-off-by: Daniel Miranda <danielkza2@gmail.com>
20 Jan, 2016
6 commits
-
Signed off by: Daniel Miranda <danielkza2@gmail.com>
-
Signed off by: Daniel Miranda <danielkza2@gmail.com>
-
Signed off by: Daniel Miranda <danielkza2@gmail.com>
-
Now it doesn't redirect to the tree metric configuration creation page after choosing a hotspot metric configuration Adds a bunch of code from removed commit ec4c3ef6f29aa34f3c58819df4f84725aff8bd60 that fixed the view after the modification introduced by 39bc97f568d6989ae98b1f5fd5452515ee54045f. It fixes the view to properly work with the path helper. This is a squash of two commits. Signed off by: Diego Araújo <diegoamc90@gmail.com> Signed off by: Heitor Reis <marcheing@gmail.com>
25 Nov, 2015
1 commit
-
Signed off by: Eduardo Araújo <duduktamg@hotmail.com>
19 Nov, 2015
3 commits
-
* Creates a step to create a ruby configuration with the Saikuro metric * Define new factories for a saikuro metric and saikuro metric configuration -
* Also fixed a typo on a repository step that waits for an errored processing Signed off by: Diego Araújo <diegoamc90@gmail.com> Signed off by: Eduardo Araújo <duduktamg@hotmail.com>
09 Nov, 2015
2 commits
-
* Closes Issue #218 KalibroClient returns 0 instead of nil when the module has no parent. Signed-off-by: Eduardo Silva Araújo <duduktamg@hotmail.com>
-
* Renamed ProjectAttributes' column hidden to public and inverted default values * Implemented Project#"public_or_owned_by_user" * All features now create ProjectAttributes after creating a Project * Implemented ProjectAttributes#project and ProjectAttributes#project= * Fix Project#attributes to return nil when there is no ProjectAttribute * Fixes #263 Signed off by: Diego Araújo <diegoamc90@gmail.com>
06 Nov, 2015
2 commits
-
Signed off by: Diego Araújo <diegoamc90@gmail.com>
-
Signed off by: Diego Araújo <diegoamc90@gmail.com>
28 Oct, 2015
1 commit
-
* Also the previous conditional in the view was unnecessary because the kalibro_ranges method never returns nil, at most it returns an empty array, which is checked by another conditional in the same view Signed off by: Eduardo Araújo <duduktamg@hotmail.com>
26 Oct, 2015
1 commit
-
The previous test was creating the MetricConfiguration directly through factories/kalibro_client. While there is a bug on the MetricConfiguration creation form that saves hotspot as tree ones. Signed off by: Diego Araújo <diegoamc90@gmail.com>