-
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 ERC721 tests #1148
Comments
This seems to be an old issue. If it is still open I can pick this up. I am currently setting up the project, will report back with findings. Edit: In the related bug #1137 , you point our that ERC721 tests are mess. IF you can give more detail on what needs to be improved, it will be helpful. |
Hey @logeekal, thanks for volunteering for this! I haven't looked at these tests in quite some time, but like you said, they are correct, and have 100% line coverage. The issues that I recall with them come from a maintainability/readability point of view, as mentioned in one of the comments:
That said, it is very possible that I was being too harsh when evaluating these tests 😅 So don't sweat it if you don't find anything other than these naming issues I mentioned. |
@logeekal Cool! Feel free to suggest improvements if you think of anything else. 🙂 |
Sure @frangio . I am thinking of doing this fix in 2 parts.
For the first one, I will be opening the pull request soon. You can let me know if it is not the correct way. Thanks. |
@frangio & @nventuro , I did not see any code in ERC721 test suite using accounts[] format, so we are good on that front. On the left most column, I give my suggestions but those are very minor changes, please let me know what you guys think and if I should go ahead with these changes. |
Niiice, I didn't expect a full-fledged spreadsheet 😅 Your suggestions look good, please go ahead! |
The account names refactor (#1137) didn't cover ERC721 because the whole suite is somewhat problematic: there are multiple references to accounts with weird names (e.g.
creator
,sender
, etc), inconsistent naming, among others. We should take a look at these four files and polish them a bit so that they are more in-line with the rest of the suite. While there's no testing guide yet (#1077), some test suites can be used as a reference point, likeERC20
andEscrow
.The text was updated successfully, but these errors were encountered: