Ideally we can use as-pect with near-lib. Currently the as-pect tests we use are to test encoding/decoding and mock the imported functions. If we add near-lib we can do the compiling and testing all in one step instead of two.
One issue that might arise is that currently as-pect binaries contain exported functions that use floating point numbers. Is it the case that any floats in a binary case issues with the nearcore?
The other feature that will be useful in NEARStudio and in general is to properly mock near-lib such that a connection to a node isn't required. Or I should say a "real" node. Perhaps in the web context it's another web worker.
Ideally we can use as-pect with near-lib. Currently the as-pect tests we use are to test encoding/decoding and mock the imported functions. If we add near-lib we can do the compiling and testing all in one step instead of two.
One issue that might arise is that currently as-pect binaries contain exported functions that use floating point numbers. Is it the case that any floats in a binary case issues with the nearcore?
The other feature that will be useful in NEARStudio and in general is to properly mock near-lib such that a connection to a node isn't required. Or I should say a "real" node. Perhaps in the web context it's another web worker.