Commit 117b619b by Calen Pennington

Namespace the coverage html and xml report generation tasks

parent 8ffe91d4
...@@ -23,7 +23,7 @@ rake test_common/lib/capa || TESTS_FAILED=1 ...@@ -23,7 +23,7 @@ rake test_common/lib/capa || TESTS_FAILED=1
rake test_common/lib/xmodule || TESTS_FAILED=1 rake test_common/lib/xmodule || TESTS_FAILED=1
rake phantomjs_jasmine_lms || true rake phantomjs_jasmine_lms || true
rake phantomjs_jasmine_cms || true rake phantomjs_jasmine_cms || true
rake xml html rake coverage:xml coverage:html
[ $TESTS_FAILED == '0' ] [ $TESTS_FAILED == '0' ]
rake autodeploy_properties rake autodeploy_properties
\ No newline at end of file
...@@ -21,7 +21,7 @@ rake test_lms[false] || TESTS_FAILED=1 ...@@ -21,7 +21,7 @@ rake test_lms[false] || TESTS_FAILED=1
rake test_common/lib/capa || TESTS_FAILED=1 rake test_common/lib/capa || TESTS_FAILED=1
rake test_common/lib/xmodule || TESTS_FAILED=1 rake test_common/lib/xmodule || TESTS_FAILED=1
rake phantomjs_jasmine_lms || true rake phantomjs_jasmine_lms || true
rake xml html rake coverage:xml coverage:html
[ $TESTS_FAILED == '0' ] [ $TESTS_FAILED == '0' ]
rake autodeploy_properties rake autodeploy_properties
\ No newline at end of file
...@@ -184,16 +184,20 @@ task :test do ...@@ -184,16 +184,20 @@ task :test do
end end
end end
task :html do namespace :coverage do
TEST_TASK_DIRS.each do |dir| desc "Build the html coverage reports"
sh("coverage html --rcfile=#{dir}/.coveragerc") task :html do
TEST_TASK_DIRS.each do |dir|
sh("coverage html --rcfile=#{dir}/.coveragerc")
end
end end
end
task :xml do desc "Build the xml coverage reports"
TEST_TASK_DIRS.each do |dir| task :xml do
# Why doesn't the rcfile control the xml output file properly?? TEST_TASK_DIRS.each do |dir|
sh("coverage xml -o reports/#{dir}/coverage.xml --rcfile=#{dir}/.coveragerc") # Why doesn't the rcfile control the xml output file properly??
sh("coverage xml -o reports/#{dir}/coverage.xml --rcfile=#{dir}/.coveragerc")
end
end end
end end
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment