Add missing unit tests

[matextrem]

This PR closes #2

• Added missing unit tests
• Add coveralls npm task
• Add github action to perform coveralls task when there is a push in a pull request

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	6	0
Ignored	0	N/A

• Result: ✅ success

• Annotations: 6 total

  ---

[failure] @typescript-eslint/no-explicit-any

• src/api/cow/index.ts Line 67 - Unexpected any. Specify a different type.
• src/api/cow/index.ts Line 340 - Unexpected any. Specify a different type.
• src/api/cow/index.ts Line 349 - Unexpected any. Specify a different type.
• src/api/cow/index.ts Line 358 - Unexpected any. Specify a different type.
• src/api/cow/index.ts Line 370 - Unexpected any. Specify a different type.
• src/utils/appData.spec.ts Line 103 - Unexpected any. Specify a different type.

---

^{Report generated by eslint-plus-action}

[matextrem]

I'm not pretty sure why Coveralls BOT is not commenting the PR.

[alfetopito]

Left a few comments regarding individual tests

Regarding the coverage, while there are no comments published by the bot (🤷), it's not hard to find the report by looking at the PR checks

Looking that the current coverage of 57%, is your goal to increase that further with this or follow up PRs?

[ramirotw]

We are getting there!

Apart from the code comments, I'd also add some tests to validate that the passed appDataHash on the SDK's constructor is actually set on the X-AppId header

[matextrem]

Left a few comments regarding individual tests

Regarding the coverage, while there are no comments published by the bot (🤷), it's not hard to find the report by looking at the PR checks

Looking that the current coverage of 57%, is your goal to increase that further with this or follow up PRs?

Yeah, the idea is to have our features tested as long as we can. We have reached around 90% in CowApi with this PR. We should also trying to achieve the same for the others APIs (It could be achieved in follow up PRs). Also, it is a good practice to create unit tests with new features (The PR of a new feature should include the logic and also the tests) to keep the coverage.

[ramirotw]

🚢

[alfetopito]

Nice job!

Left a few nitpicks and questions but it's approved already