ozontech / ozontech/testo

Merge test coverage with e2e tests in CI

Open
#21 1 comment 0 reactions 1 assignee View on GitHub

@metafates is already working on this.

Since Jun 15, 2026.

enhancement good first issue
Dominant language
Go
Stars
160
Forks
6
Avg merge
24m
Merged PRs (30d)
1

Description

Feature

To display that nice coverage: X% in the README Testo uses coverage report from unit tests.

But there are also end-to-end tests (see here) - it would nice to include their coverage when generating that badge in GitHub workflow.

We can start from doing so in the Makefile first to ensure it works and then proceed with implementing it inside workflow.

As I hint, I can suggest running all tests (just add -tags e2e to go test) and ignore possible failures (some examples will fail but that is expected as they show how errors work).

Something like this:

go test -coverprofile=coverage.out -coverpkg=./... ./... # run all unit tests
go test -tags e2e -coverprofile=coverage.out -coverpkg=./... ./... || true  # run all tests and ignore errors

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.