Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assert.Expect does not catch the error thrown by a called method , when parameters are not in order #8

Open
hyyan opened this issue Mar 9, 2020 · 0 comments
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@hyyan
Copy link
Member

hyyan commented Mar 9, 2020

It seems the Assert.Expect expects the parameter to be in a specific order

doing the following will fail :

Assert.Expect(256 , #Instance!.setFirstCondition(condition!))

Doing this will work

Assert.Expect(#Instance!.setFirstCondition(condition!),256)

The documentation does not state this case, so not sure if this is a bug or intended behavior

@SebastianAdams SebastianAdams added bug Something isn't working documentation Improvements or additions to documentation labels Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants