- 
                Notifications
    
You must be signed in to change notification settings  - Fork 16
 
feat: add the mint_and_register_ip_and_make_derivative method #119
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just 2 minor comments.
| 
               | 
          ||
| 
               | 
          ||
| class TestSPGNFTOperations: | ||
| @pytest.fixture(scope="module") | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume we remove these since they are included in the newly added test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I move into conftest.py, which saves the common fixture.
| ip_asset, | ||
| "_parse_tx_ip_registered_event", | ||
| return_value={"ip_id": IP_ID, "token_id": 1}, | ||
| return_value={"ip_id": IP_ID, "token_id": 3}, | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we use a different hardcoded token_id?  I mean I don't know the reason that use 3 instead of 1.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to make sure all test cases pass.
Description
mint_and_register_ip_and_make_derivativemethodRegistrationResponseconfest.pyTest Plan