chore: add code coverage

[LeeDongGeon1996]

THIS DRAFT PR IS STILL WORK IN PROGRESS

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation, context, and sources of information or recipes.

Fixes #

Checklist

• My code follows the existing style, code structure, and naming taxonomy
• I have performed a self-review of my own code and included any verifying manual calculations
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings and running code analysis does not produce any issues
• I have added or updated unit tests that prove my fix is effective or that my feature works, and achieves sufficient code coverage
• I have added or run the performance tests that depict optimal execution times
• New and existing unit tests pass locally and in the build (below) with my changes

Acknowledgements

• I have read and understand the Apache 2.0 license
• I agree to the Developer Certificate of Origin (DCO) 1.1

[LeeDongGeon1996]

@DaveSkender Can you check code coverage settings and artifact settings in Azure Piplines? Looks like all the settings for code-coverage and artifacts are already set.

[DaveSkender]

I’ll take a look, but may take a while. It’s probably generating code coverage, but not publishing it. It should look like the build got .NET

[LeeDongGeon1996]

FYI, on my screen.

[DaveSkender]

You were just missing the publish step. See file diffs.

[DaveSkender]

On a related note, I've set up the internal package manager, something we can use for intermediate packages before we publish to PyPi or other public package managers. You can access it here: https://dev.azure.com/skender/Stock.Indicators/_packaging?_a=feed&feed=Internal

You can also use this to test it out from a user's perspective.

[LeeDongGeon1996]

Thanks. It works well :)

[github-actions]

This Pull Request has been automatically locked since there has not been any recent activity after it was closed. Please open a new Issue for related bugs.