Adding Unit Test from .NET Microframework

[Ellerbach]

Adding Unit Test from .NET Microframework

Description

Adding Unit Test from .NET Microframework

Motivation and Context

• related to #704
• Still some Decoder tests will have to be added, none were existing

How Has This Been Tested?

• All tests run and all is green

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[Ellerbach]

Note: SonarCloud adjusted to avoid security anyalize on Tests/**

[josesimoes]

LGTM! Nice, our next class lib with unit tests after mscorlib.