length check in match mock

[amexjake]

Attempts to address some issues when the length property is assumed from the mocks parameter of the matchMock utility.

Description

This attempts to address issue #99, where an error is thrown about there being no length property for mocks.

Requires #129 to be merged first.

Motivation and Context

This will throw a more helpful and verbose error if no mocks are defined for a scenario, or if for some reason an unexpected value is passed to the matchMock util, and thus give more insight into the error thrown in #99 when parrot is used in conjunction with One App.

How Has This Been Tested?

Unit tests have been written to account for these new errors.

Types of Changes

• 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 not work as expected)
• Documentation (adding or updating documentation)
• Dependency update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• My changes are in sync with the code style of this project.
• There aren't any other open Pull Requests for the same issue/update.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• This change impacts caching for client browsers.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using parrot?

[AdamFoskit]

This looks good

[github-actions]

This pull request is stale because it has been open 30 days with no activity.

[github-actions]

This pull request is stale because it has been open 30 days with no activity.