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
All the integration tests just null out the parameters (the transaction simulator does pass in real values, so the code is exercised by tests). Should there be at least one integration test that passes in a non-null pair to validate via integration? If not what purpose do the integration tests provide? Should they be removed if they are not keeping pace with the evolution of the APIs they are testing?
The text was updated successfully, but these errors were encountered:
I assume this would remove Enclave tests that integrate with a running Tessera started up by testcontainers? That is a pretty large footprint that we could remove.
I assume this would remove Enclave tests that integrate with a running Tessera started up by testcontainers? That is a pretty large footprint that we could remove.
think these have already been removed (they were ATs) - there's very few Integration Tests actually (like a dozen)
Make a call on the integration tests
Integration tests - are very out of date. Either update them or remove them if the code is covered elsewhere.
This question can be answered once we have aggregated test coverage #6650
Eg EthCallIntegrationTest - comment on #6661
All the integration tests just null out the parameters (the transaction simulator does pass in real values, so the code is exercised by tests). Should there be at least one integration test that passes in a non-null pair to validate via integration? If not what purpose do the integration tests provide? Should they be removed if they are not keeping pace with the evolution of the APIs they are testing?
The text was updated successfully, but these errors were encountered: