removing mocked function from ts-jest

[gagoar]

no need to see this when running tests!

I had some issues with sonarCloud so I took it out. The issues were around ignoring tests for duplication and then re-running the check. I believe some duplication in tests is necessary to understand use-cases. IMO It is documentation. Verbosity is desired in some cases.

[coveralls]

Pull Request Test Coverage Report for Build 2480554512

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 2470350865:	0.0%
Covered Lines:	230
Relevant Lines:	230

---

💛 - Coveralls

[codecov]

Codecov Report

Merging #312 (727b4e8) into master (5266499) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #312   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          246       246           
  Branches        52        52           
=========================================
  Hits           246       246           

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5266499...727b4e8. Read the comment docs.

[gustavkj]

Looks good, but using jest.mocked would not require adding the types yourself.

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
9.7% Duplication