Commit Graph

5 Commits

Author SHA1 Message Date
Edwin Zhai 9a1b5329aa Clean config in source code
Update .gitignore to skip editor files and .coveragerc to remove
nonexisted directory

Change-Id: Icab626dfcd8d71993e0d7e6e218a86ec8cd0c502
2016-02-05 08:45:38 +00:00
Monty Taylor 3e6880becb Change ignore-errors to ignore_errors
Needed for coverage 4.0

Change-Id: I8f3a4ca33ab5415b0265a857344f46bd736acd0e
2015-09-21 14:24:28 +00:00
Julien Danjou 8372f48b7a Rename to aodh
Change-Id: Ibd4c9811daa6e9e692457ce480a58c964fef7cb9
Signed-off-by: Julien Danjou <julien@danjou.info>
2015-06-25 14:46:39 +02:00
Tong Li 5746d52ea8 test code should be excluded from test coverage summary
Since the recent movement of the test code directory, now entire test
code is included in the test coverage summary, it makes a rather
strange loop, test code in the summary also shows being tested or
not tested. This patch will fix the problem so that the test
coverage summary will not show the coverage percentage for test code.

Change-Id: Ibbb4a009f01515befdd7045d6eec1afaf24ca99f
2013-12-11 11:40:51 -05:00
Tong Li 50a7dcf421 add coverage config file to control module coverage report
Ceilometer copies oslo common code into its code stream. When run
unit tests with coverage option, the overall test code coverage
percentage is low due to the enclosure of the common libraries.
Adding the coverage config file will exclude these modules in
the code coverage report so that developers can easily see if
new test cases has increased or decreased the code test coverage.

to see the code coverage report, following the following steps:

1. In ceilometer root directory, execute the following command
   ./run-tests --coverage
2. Once the test run completed successfully, open up the follwoing
   file in your browser and scroll down to the bottom to see the
   total number. (this patch makes that number to be 90%)
   <ceilometer_root_dir>/cover/index.html

To keep up with this effort, whenever you add new code, please
run the test code with coverage option and make sure your new
code and test won't decrease the total percentage. If it did,
that means you may have new code un-tested :-)

Change-Id: I277c243b6aadb0e8524915452326ed875e14ce9c
2013-09-30 10:52:34 +00:00