You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Classes such as ActivationToken do not have public property setters and therefore cannot be constructed in in unit tests with expected responses. They also cannot be mocked using Moq because they do not implement an interface.
Another example, in a unit test, a user is created and subsequently activated. Activation requires a user id, but the user id cannot be set on the User object, so I cannot unit test my process.
New or Affected Resource(s)
ActivationToken and User at least but there are others.
Provide a documentation link
No response
Additional Information?
No response
The text was updated successfully, but these errors were encountered:
This request has to be coordinated with API teams that provide the OpenAPI specification. In the meantime, I recommend using WireMock to mock the server response. You can see some examples here.
Describe the feature request?
Classes such as ActivationToken do not have public property setters and therefore cannot be constructed in in unit tests with expected responses. They also cannot be mocked using Moq because they do not implement an interface.
Another example, in a unit test, a user is created and subsequently activated. Activation requires a user id, but the user id cannot be set on the User object, so I cannot unit test my process.
New or Affected Resource(s)
ActivationToken and User at least but there are others.
Provide a documentation link
No response
Additional Information?
No response
The text was updated successfully, but these errors were encountered: