-
Notifications
You must be signed in to change notification settings - Fork 214
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
remove xs:unit testing #10207
remove xs:unit testing #10207
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.
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.
I changed my mind...
I concur with "In the past year we've developed much more integration testing and I'm confident these tests are redundant."
So this need not be socialized more widely.
p.s. I think ava-xs contorts our dependency tree. It should be in its own package. Which would mean this PR might prune that package. Including it in the xsnap package adds otherwise irrelevant dependencies to xsnap. IOU an issue. not confident I'll find time to collect details to file it, though. |
Deploying agoric-sdk with Cloudflare Pages
|
There are few to no errors we've detected in unit tests running in XS that we didn't in Node. We now have many other tests that run XS and don't need to unit test these. It generally doesn't hurt to test more, but ava-xs is so different from XS that the cost of reconciliation is too great.
incidental
Description
While working on #10202 I got a CI error that "no function" for the Zoe tests. It turned out to be that ava-xs doesn't support
t.snapshot
. So I added it to the voluminous "exclude" value and pushed again. Later I see CI fails again because ava-xs is confused by thesnapshots
directory.The
test:xs-unit
job is not carrying its weight. I can't recall it ever detecting an error that wasn't detected in Node. Maybe a while ago it did and it was an important line of defense. In the past year we've developed much more integration testing and I'm confident these tests are redundant.It generally doesn't hurt to test more, but ava-xs is so different from XS that the cost of reconciliation is too great.
Security Considerations
none
Scaling Considerations
none
Documentation Considerations
none
Testing Considerations
see above
Upgrade Considerations
none