Setup Codecov integration in CI

[wojtek-coreum]

Description

Reviewers checklist:

• Try to write more meaningful comments with clear actions to be taken.
• Nit-picking should be unblocking. Focus on core issues.

Authors checklist

• Provide a concise and meaningful description
• Review the code yourself first, before making the PR.
• Annotate your PR in places that require explanation.
• Think and try to split the PR to smaller PR if it is big.

---

This change is 

[dzmitryhil]

Reviewed 1 of 2 files at r1.
Reviewable status: 1 of 2 files reviewed, all discussions resolved (waiting on @miladz68 and @ysv)

[codecov]

Welcome to Codecov 🎉

Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.

Thanks for integrating Codecov - We've got you covered ☂️

[ysv]

Reviewed 1 of 2 files at r1, 1 of 1 files at r3, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @miladz68 and @wojtek-coreum)

---

.github/workflows/ci.yml line 150 at r3 (raw file):

        with:
          token: ${{ secrets.CODECOV_TOKEN }}
          files: ${{ github.workspace }}/coreum/coverage/coreum,${{ github.workspace }}/coreum/coverage/coreum-integration-tests

we don't create codecov for integraiton tests we do only for unit tests ?

Code quote:

coreum-integration-tests

[wojtek-coreum]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @miladz68 and @ysv)

---

.github/workflows/ci.yml line 150 at r3 (raw file):

Previously, ysv (Yaroslav Savchuk) wrote…

we don't create codecov for integraiton tests we do only for unit tests ?

We didn't inspect the possibility of building a binary version which could track covered lines.
There is a potential way to do it described here: https://go.dev/doc/build-cover but it's definitely a separate task.

[ysv]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @miladz68 and @wojtek-coreum)

---

.github/workflows/ci.yml line 150 at r3 (raw file):

Previously, wojtek-coreum (Wojtek) wrote…

We didn't inspect the possibility of building a binary version which could track covered lines.
There is a potential way to do it described here: https://go.dev/doc/build-cover but it's definitely a separate task.

yes, I'm ok with this it is not in scope of this task
My concern is that file name is coreum-integration-tests while you do codecov for unit tests

[dzmitryhil]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @miladz68 and @wojtek-coreum)

[wojtek-coreum]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @miladz68 and @ysv)

---

.github/workflows/ci.yml line 150 at r3 (raw file):

Previously, ysv (Yaroslav Savchuk) wrote…

yes, I'm ok with this it is not in scope of this task
My concern is that file name is coreum-integration-tests while you do codecov for unit tests

yes, because this is the result or running unit tests in integration-tests module

[miladz68]

Reviewed 1 of 2 files at r1, 1 of 1 files at r3, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @ysv)

[ysv]

Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @wojtek-coreum)