-
Notifications
You must be signed in to change notification settings - Fork 1
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
FIP-40 testing #344
FIP-40 testing #344
Conversation
FIP-40 first tests calling fio.perms actions
FIP-40 develop parameter validation and tests
FIP-40 smoke tests for permissions and action arguments
FIP-40 test cleanup
FIP-40 add tests for register address
FIP-40 tests for register address, transfer domain, and burn expired.
FIP-40 make test work for non fio.address call to clearperm.
FIP-40 add happy path tests for getters
FIP-40 endpoint tests
FIP-40 update tests and fix tpid is domain only bug
FIP-40 prepare for develop merge
FIP-40 merge develop into dev branch
hi Adam. ************************** nft-uniqueness.js ************************** I recommend first, for tests that fail, when performing QA level testing, it is helpful to understand if the failure occurs when the test in question is run as .only in the test suite....when we QA fio, we always do runs as a whole, then if there are failures we run the failed tests as .only on the same server, if the error persists in the .only configuration then the error is logged as a bug and assigned... presently there are no tests that fail when performing the tests in this manner....for the tests you mention, the tests passed without having to run them .only in a local dev env... let me know if you want to do more follow up on this, it might be more useful if we go offline from FIP-40 and ensure you are comfortable with how the QA level testing is performed.... thanks |
FIP-40 timing issue and error message
FIP-40 first tests calling fio.perms actions