-
Notifications
You must be signed in to change notification settings - Fork 11.8k
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
Improve test suite descriptions #1157
Labels
good first issue
Low hanging fruit for new contributors to get involved!
tests
Test suite and helpers.
Comments
nventuro
added
good first issue
Low hanging fruit for new contributors to get involved!
kind:improvement
tests
Test suite and helpers.
labels
Aug 6, 2018
I like the proposal! |
This was referenced Aug 13, 2018
This was referenced Aug 24, 2018
Merged
@singhj1234 please do! I haven't been tackling this due to prioritizing other tasks, but these definitely need some love. |
This was referenced Apr 15, 2019
dibi91
added a commit
to dibi91/openzeppelin-contracts
that referenced
this issue
Aug 25, 2020
Co-authored-by: Francisco Giordano <frangio.1@gmail.com>
dibi91
added a commit
to dibi91/openzeppelin-contracts
that referenced
this issue
Aug 25, 2020
Co-authored-by: Francisco Giordano <frangio.1@gmail.com>
dibi91
added a commit
to dibi91/openzeppelin-contracts
that referenced
this issue
Aug 25, 2020
Co-authored-by: Francisco Giordano <frangio.1@gmail.com>
frangio
added a commit
that referenced
this issue
Aug 25, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Low hanging fruit for new contributors to get involved!
tests
Test suite and helpers.
The description of each tests (i.e. the text in the
describe
,context
andit
blocks) is a bit inconsistent, we should move towards a more standard structure.I suggest:
contract
()describe
(<feature/function>)context
(<context (!), e.g: once deployed, in refund period, when disabled, etc>)it
(<verb in present simple, e.g. 'accepts payments', 'allows owner to transfer ownership' // avoid using 'should do x', go for 'does x' instead>)This will allow us to write test chains that read very naturally, e.g.
PausableToken transfer when paused reverts
The text was updated successfully, but these errors were encountered: