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

Provide strict mode #4

Open
PiotrSikora opened this issue Aug 11, 2020 · 2 comments
Open

Provide strict mode #4

PiotrSikora opened this issue Aug 11, 2020 · 2 comments

Comments

@PiotrSikora
Copy link
Member

In this mode (or maybe by default?) tests should fail if the extension is making unexpected hostcalls.

@PiotrSikora
Copy link
Member Author

cc @agiachris

@agiachris
Copy link
Contributor

I think this should be optional. Currently, the user has the option to mock parameters and returns from vm->host and vm<-host on specific host functions. We could also create an expectation over the host functions themselves (i.e. without considering the parameters/returns). Low-level mocking on host function parameters and returns should add the host function to the list of expected host calls. This will enable tracking of in-bound host function calls in a specified ordering. What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants