We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As discussed in #878
I would even go one step further and propose a pattern for the property to tested. Thus, a name should be something like
[TestTarget_SituationUnderTest_ExpectedBehavior]
So, for instance here,
TestSelfDestruct_SuccessfulInvocation_ReturnsSelfdestructedStateAndConsumesGas
This might be a bit long, but I think it documents well what this test does. In contrast, a test checking for failure states would be named like
TestSelfDestruct_InsufficientGas_ReturnsStopStateAndError
If the SituationUnderTest is obvious, it may be omitted.
SituationUnderTest
Originally posted by @HerbertJordan in #878 (comment)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As discussed in #878
I would even go one step further and propose a pattern for the property to tested. Thus, a name should be something like
So, for instance here,
This might be a bit long, but I think it documents well what this test does. In contrast, a test checking for failure states would be named like
If the
SituationUnderTest
is obvious, it may be omitted.Originally posted by @HerbertJordan in #878 (comment)
The text was updated successfully, but these errors were encountered: