Add comprehensive tests for ERC721EnumerableFacet and LibERC721Enumer… #229
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Added comprehensive test coverage for
ERC721EnumerableFacetandLibERC721Enumerablecomponents. Created test harnesses and implemented 71 new test cases covering metadata, enumeration, approvals, transfers, and edge cases.Changes Made
Created
ERC721EnumerableFacet.t.sol- 38 test cases covering:Created
LibERC721Enumerable.t.sol- 33 test cases covering:Created
ERC721EnumerableFacetHarness.sol- Test harness providing:initialize()function for test setupmint()helper function that properly updates enumeration arraysCreated
LibERC721EnumerableHarness.sol- Test harness providing:Checklist
Before submitting this PR, please ensure:
Code follows the Solidity feature ban - No inheritance, constructors, modifiers, public/private variables, external library functions,
using fordirectives, orselfdestructCode follows Design Principles - Readable, uses diamond storage, favors composition over inheritance
Code matches the codebase style - Consistent formatting, documentation, and patterns (e.g. ERC20Facet.sol)
Code is formatted with
forge fmtforge fmtbefore merge)Existing tests pass - Run tests to be sure existing tests pass.
New tests are optional - If you don't provide tests for new functionality or changes then please create a new issue so this can be assigned to someone.
All tests pass - Run
forge testand ensure everything worksDocumentation updated - If applicable, update relevant documentation
Additional Notes