Search
⌘K
    to navigateEnterto select Escto close

    Test coverage

    In the previous chapter, we had mentioned adding some tests. But currently, we don't have any mechanism to ensure that people are actually writing the necessary tests.

    In this chapter we will see how to add a test coverage report for all tests in the project.

    What is test coverage?

    Test coverage is a technique which determines whether our tests are actually covering the application code and how much code is executed when we run those tests.

    Let's take an example where our application has 10 features, and when we run our tests, they cover only 7 of those features. In this case, we could say that our tests cover 70% of the application.

    Why do we need to have test coverage?

    Test coverage helps monitor the quality of testing and assists developers in create tests to cover areas that are missing.

    Test coverage using SimpleCov

    We will be using simplecov gem for our test coverage.

    SimpleCov is a code coverage analysis tool for Ruby. It uses Ruby's built-in Coverage library to gather code coverage data.

    Add simplecov to your Gemfile and run bundle install:

    1gem 'simplecov', require: false, group: :test

    Load and launch simplecov at the very top of your test/test_helper.rb:

    1def enable_test_coverage
    2  require 'simplecov'
    3  SimpleCov.start do
    4    add_filter '/test/'
    5    add_group 'Models', 'app/models'
    6    add_group 'Mailers', 'app/mailers'
    7    add_group 'Controllers', 'app/controllers'
    8    add_group 'Uploaders', 'app/uploaders'
    9    add_group 'Helpers', 'app/helpers'
    10    add_group 'Workers', 'app/workers'
    11    add_group 'Services', 'app/services'
    12  end
    13end
    14
    15enable_test_coverage if ENV['COVERAGE']
    16
    17# Previous content of test helper as is

    We are enabling the test coverage only on demand if the ENV variable named COVERAGE exists in our environment. We don't need to execute this enable_test_coverage method while running the tests every time.

    Remember the SimpleCov.start must be issued before any of your application code is required! If simplecov starts after your application code is already loaded (via require), then it won't be able to track your files and their coverage.

    add_filter is a filter method for test coverage given by simplecov. This filter method can be used to remove selected files from our coverage data.

    We have added such a filter for our test files because we don't need to cover test files. We have to cover code inside the app folder for Models, Services, Controllers and Helpers etc.

    We can separate our source files into groups with the help of add_group.

    We have separated coverage listings for Models, Mailers, Controllers, Helpers, Workers and Services, etc.

    Before running simplecov via tests, we need to make the change in the below mentioned line from test/test_helper.rb:

    1# Run tests in parallel with specified workers
    2  parallelize(workers: :number_of_processors) unless ENV['COVERAGE']

    The reason why we added a conditional to the above line is because simplecov gem has issues while running tests in parallel with workers.

    So by adding a conditional we are not executing parallelize(workers: :number_of_processors) method, if we are running test coverage.

    Let's run our full test suite to see the percentage coverage in our application:

    1COVERAGE=true bundle exec rails test -v

    By any chance, if your terminal shows a segmentation issue, then exit out of the process using Ctrl+C or Cmd+C. This segmentation error is one of the issues with simplecov, when it runs under some specific Ruby versions. It doesn't have any negative impacts, because we'd be getting the generated report either way.

    View the coverage reports

    After running tests, open coverage/index.html in the browser of your choice. In a Mac Terminal, run the following command from the application's root directory:

    1open coverage/index.html

    We will get a test coverage report, which might look like the following image:

    Test coverage report 1

    In cases where we don't have enough test cases, this is how the report would look like:

    Test coverage report 2

    Run the following command from the terminal to make sure coverage reports are not tracked by Git:

    1echo "coverage" >> .gitignore

    If you want to share the whole test coverage report then share the coverage folder containing index.html file and assets folder. Because for running index.html properly we need an assets folder.

    You can also share screenshot of the HTML page from the browser for coverage report.

    Now, let's commit the changes:

    1git add -A
    2git commit -m "Added test coverage reporting"
    Previous
    Next