Here is my .gitlab-ci.yml: image: python:3 stages: - test coverage: stage: test script: - pip install coverage - coverage run ./main.py - coverage report -m - coverage xml artifacts: paths: - ./coverage.xml reports: cobertura: ./coverage.xml only: - master In logs I can see . My GitLab version is "GitLab Enterprise Edition 13.6.7-ee", and content in cobertura.xml is like the following, because it is a private project, so I replace some key info . I'm using jest, and cobertura as coverage reporter. The collected coverage fuzzing report uploads to GitLab as an artifact. GitLab development guidelines - testing best practices. Inside cobertura-coverage.xml file I see all needed information (as described in documentation), but in MR I can't see any green/red vertical lines illustrating coverage. Test Coverage Visualization doesn't display when you have required manual jobs in a pipeline #327097 Backlog Make test coverage visualisation available for blocked pipelines #343630 0 Assignees Epic None Labels None Milestone None Iteration None Weight None Due date None Time tracking No estimate or time spent Health status None Confidentiality For customers utilizing Git Flow getting test data like coverage and test summaries from features branches is hard . GitLab.com (15.1-pre) GitLab.com (15.1-pre) 15.0 14.10 14.9 14.10 13.12 . Category Direction - Code Testing and Coverage | GitLab Ask Question Asked 1 year, 2 months ago. As you can see, I've got job named "test:coverage", which has coverage report. Show code coverage diff as soon as coverage report is ... - gitlab.com How to trigger Coverage badge and Test Coverage Visualization with ... Version history. Test Coverage Visualization doesn't easily support C# ... - gitlab.com Documentation for GitLab Community Edition, GitLab Enterprise Edition, Omnibus GitLab, and GitLab Runner.