-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
NV18: FEVM: Basic smoke test #9635
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh no, this test is far too CLI-y and string-matchy for my preference. This is problematic for 2 reasons:
- Such tests are notoriously brittle and lead to future 😿
- Such tests are less useful as "demonstrators" of how things work (what messages are sent, what's returned, etc.)
I think it would be much nicer to actually read the contract bytes, formulate the messages as appropriate, and parse returns with assertions. This will definitely be a more bloated test (much more code), but overall better.
(If we want this as a separate CLI test, just to cover CLI functionality, I'm less opposed to that).
Basically you want me to copy the cli code ;) I guess I could do that. |
But yes, we do want to cover cli functionality too. |
That would go in |
It is an itest however, and there plenty of cli tests in the itest bundle. I propose we keep this here and add a second test that does everything by hand. |
Yeah, I don't think there should be, and don't really want more. Here's a good test to use as a model -- it's basically laid out as:
|
ok, I rewrote the thing as requested and removed the cli test; I will squash on merge and there will be no sign of it.... |
The basic FEVM smoke test with SimpleCoin.