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
I wanted to inquire if there are considerations to support third party testing with the consensus-spec-tests. It would be interesting to have an endpoint or a standardized log message format that allows for external testing tools to validate the state of a consensus implementations at a certain point in time. It would be great to have a standardized way to validate a consensus node against the spec after performing chaos testing.
The text was updated successfully, but these errors were encountered:
The LICENSE file for the repository ethereum/consensus-spec-tests is an MIT License, granting permission to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software, provided that the copyright notice and permission notice are included in all copies or substantial portions of the Software. The software is provided "as is", without warranty of any kind.
I wanted to inquire if there are considerations to support third party testing with the consensus-spec-tests. It would be interesting to have an endpoint or a standardized log message format that allows for external testing tools to validate the state of a consensus implementations at a certain point in time. It would be great to have a standardized way to validate a consensus node against the spec after performing chaos testing.
I wanted to inquire if there are considerations to support third party testing with the consensus-spec-tests. It would be interesting to have an endpoint or a standardized log message format that allows for external testing tools to validate the state of a consensus implementations at a certain point in time. It would be great to have a standardized way to validate a consensus node against the spec after performing chaos testing.
The text was updated successfully, but these errors were encountered: