ScopeNotFoundException on DropCollection does not have proper message

Description

The test Test_DropNonExistentScope_Throws_ScopeNotFoundException is failing as the ScopeNotFoundException message thrown from DropScopeAsync is not what is expected:

Assert.Equal() Failure
↓ (pos 0)
Expected: Scope with name scope_none not found
Actual: scope_none
↑ (pos 0)

Assertion failure here

The message contains only the scope name and not the whole message - this only happens when ScopeNotFoundException is thrown via DropScopeAsync, when it is thrown from other CollectionManager APIs it contains the full message, which leads me to believe this is a minor bug.

Environment

None

Gerrit Reviews

None

Release Notes Description

None

Activity

Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Fix versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created March 11, 2022 at 12:56 PM
Updated April 18, 2022 at 6:39 PM
Resolved April 18, 2022 at 6:39 PM
Instabug