You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 22, 2023. It is now read-only.
Perhaps this is a good moment to revive #94 and agree on a standard to enforce for NEO3? We can use a json schema + validator to make sure all json files pass.
Other items I'd like to include:
not all tests have a name field (e.g. TRHOW, ABORT,ASSERT, PUSHM1_to_PUSH16, PUSHINT8_to_PUSHINT256.json)
hex strings are sometimes prefixed with 0x and sometimes not. Let's just fix them in some format (either with or without)
Restrict elements in the list under the script key to be either an instruction name or a hex string. Not "PUSH0*1048576" like CAT.json has.
It has
//
comments which are not permitted by JSON specification.https://github.com/neo-project/neo-vm/blob/master/tests/neo-vm.Tests/Tests/OpCodes/Splice/MEMCPY.json
The text was updated successfully, but these errors were encountered: