26 Oct, 2015
40 commits
-
Version 2.1.1 and below was creating the supported metric list with all Native type. Signed off by: Diego Araújo <diegoamc90@gmail.com>
-
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>
-
* Now it is correctly checking for the names of the files in the repositories#show page Signed off by: Diego Araújo <diegoamc90@gmail.com>
-
Signed off by: Diego Araújo <diegoamc90@gmail.com>
-
* Also renamed some step definitions to explicitly use tree metric configurations or hotspot metric configurations * Also added translations for the cases when there are no metric configurations of each type * Showing name and code on the table for hotspot metric configurations * When adding a hotspot metric configuration, the weight will be Signed off by: Diego Araújo <diegoamc90@gmail.com>
-
Signed off by: Diego Araújo <diegoamc90@gmail.com>
-
Signed off by: Diego Araújo <diegoamc90@gmail.com>
-
The version 2.1.0 had a bug when trying to retrieve MetricResult's ModuleResult. That's why we force at least 2.1.1 on Gemfile as well.
-
It checks for the messages of the given HotspotMetricResults. This test may be broken if the used repository developer fix all the listed issues.
-
Those were probably fixed by 206c0ccc54cec5033242ef7d15e8d24b4702a2f1.
-
It was still wipped because a random fail probably because of time dependency. Signed off by: Heitor Reis <marcheing@gmail.com>
-
Those were probably fixed by 206c0ccc54cec5033242ef7d15e8d24b4702a2f1. Signed off by: Heitor Reis <marcheing@gmail.com>
-
It was modified by the introduction of Hotspot listing but the acceptance test step never got updated. Signed off by: Heitor Reis <marcheing@gmail.com>
-
The edition acceptance test was unable to find which table the matcher was referencing since the HotspotListing one got introduced to the layout. Signed off by: Heitor Reis <marcheing@gmail.com>
-
Those were probably fixed by 206c0ccc54cec5033242ef7d15e8d24b4702a2f1. Signed off by: Heitor Reis <marcheing@gmail.com>
-
* These tests were fixed by 9f423c238409f03157117dd50f4a94783f5a3dcb Signed off by: Rafael Reggiani Manzo <rr.manzo@gmail.com>
-
* The acceptance test got ambiguous when trying to assert for links inside metric configuration tables. Signed off by: Rafael Reggiani Manzo <rr.manzo@gmail.com> -
They were fixed by 9f423c238409f03157117dd50f4a94783f5a3dcb which fixed cache expiration. Signed off by: Heitor Reis <marcheing@gmail.com>
-
The search and replace missed this. Now when a new CompoundMetriConfiguration gets created or updated the KalibroConfiguration show page gets a clear cache. Signed off by: Heitor Reis <marcheing@gmail.com>
-
* Now using the latest versions of kalibro processor (v1.1.1), kalibro configurations (v1.2.0) and kalibro_install (v4.0). Signed off by: Rafael Reggiani Manzo <rr.manzo@gmail.com>
-
* Subsequent commits will fix these tests Signed off by: Rafael Reggiani Manzo <rr.manzo@gmail.com>
-
We were missing metric configuration listing behavior Signed off by: Rafael Reggiani Manzo <rr.manzo@gmail.com>
-
The mock used was outdated regarding new KalibroClient API. Signed off by: Rafael Reggiani Manzo <rr.manzo@gmail.com>
-
Since kalibro_client v2.1.0 granlrty attribute has been renamed to granularity. Signed off by: Eduardo Araújo <duduktamg@hotmail.com>
-
Put a blank space between # and text and don't forget about tagging pending fixes with FIXME. Signed off by: Eduardo Araújo <duduktamg@hotmail.com>
-
Signed off by: Eduardo Silva Araújo <duduktamg@hotmail.com> Signed off by: Diego Araújo <diegoamc90@gmail.com>
-
Signed off by: Diego Araújo <diegoamc90@gmail.com> Signed off by: Eduardo Silva Araújo <duduktamg@hotmail.com>
-
* WIP: cucumber feature to show hotspot metric results * Add partials to list hotspot metric results * Add necessary JS to render the list of hotspot metric results on the right place div of the accordion * Translations specific to hotspot metric results * HotspotMetric and HotspotMetricConfiguration factories Signed off by: Eduardo Silva Araújo <duduktamg@hotmail.com>
-
* Includes translations * Replaces "Metric Results" with "Tree Metric Results" * Creates a feature for hotspot metric results * Handles the view when the processing fails Signed off by: Eduardo Silva Araújo <duduktamg@hotmail.com>
-
* Analizo 1.17.0, used by Travis, did not work. So the test has been kept wipped for a very long time. Signed off by: Rafael Reggiani Manzo <rr.manzo@gmail.com>
-
Signed off by: Rafael Reggiani Manzo <rr.manzo@gmail.com>
-
Signed off by: Rafael Reggiani Manzo <rr.manzo@gmail.com>
-
It is expected to have been fixed by travis' script update at: 704e074329a85379003284986e71f3559cc92cdb Signed off by: Heitor Reis <marcheing@gmail.com>
-
Clear both kalibro databases before running the first test to ensure that seeds do not affect it. Signed off by: Heitor Reis <marcheing@gmail.com>
-
The test was wipped and forgotten long ago and now been bought back to life! Signed off by: Heitor Reis <marcheing@gmail.com>
-
The step was using an outdated API. Signed off by: Heitor Reis <marcheing@gmail.com>
-
* Currently using tree_metric_results to get the results from the module Signed off by: Diego Araújo <diegoamc90@gmail.com>
-
* Also created date_metric_result factory and started using it on the metric history unit test Signed off by: Diego Araújo <diegoamc90@gmail.com>
-
* Renamed the classes, mocks and factory class on unit tests Signed off by: Diego Araújo <diegoamc90@gmail.com>
-
Some tests were still trying to access the external servers. Signed-off-by: Heitor Reis <marcheing@gmail.com>
