Creating workspaces test suit

[jaswinder6991]

Resolves #35

wip PR for creating test suit using workspaces-rs

[jaswinder6991]

Hi @frol, this is the WIP PR for workspaces tests. You can check the migrations issue which occurs if you self_upgrade with the same wasm code that is already deployed.
I can meanwhile write the test to check wasm incompatibility if any.

[jaswinder6991]

Closes #35

[frol]

@jaswinder6991 The issue you observe is related to Wasm binaries produced by Rust 1.70.0 being not compatible with nearcore runtime:

Use the following rust-toolchain.toml in the root of the project and re-compile the contract:

[toolchain]
channel = "1.69.0"

The test runs successfully when the contract is compiled with Rust 1.69:

[jaswinder6991]

Hi @frol, thanks for your comment. I was just testing the case where wasm was not 1.69.0 so sort of a negative case.
Anyway, I was able to deploy 1.71.0 compiled code on testnet. Not sure how?

So for closing #35, is this PR enough? Should I add some more tests?
I can work on adding this to github workflows.
@ailisp

[frol]

Here are the remaining items for this PR to land:

• add CI workflow
• finalize the ergonomics (e.g. cargo run --example devhub is clearly not expected way to run tests, try making cargo test work)
• check for the result, so it does not rely on human sitting there and reading the output, the test should check and pass if everything is good and fail otherwise
• As part of the test, download the production Wasm from mainnet (https://github.com/near/workspaces-rs#spooning---pulling-existing-state-and-contracts-from-mainnettestnet) and deploy it first, and compile the current version of the contract (https://github.com/near/workspaces-rs#compiling-contracts-during-test-time) as part of the test to deploy it and check migration goes well.

[jaswinder6991]

Hi @frol
The latest commit works on the list of tasks you suggested.

1. CI workflow already has cargo test check, the integration tests execute as a part of cargo test too. Do I need something additional.
2. Tests can be run via "cargo test"
3. I have added assert statements. These are however incomplete at the moment, pending resolving the upgrade issue mentioned in next point.
4. I have successfully used both import_contract and compile_project in the tests. I am currently struggling with the below issue when I call the self_upgrade at line.

status: Failure(ActionError(ActionError { index: Some(0), kind: FunctionCallError(ExecutionError("Exceeded the prepaid gas.")) }

Once I am done with the Gas fees issue, I will update the PR. Any help with the issue is updated.

[jaswinder6991]

After multiple attempts to solve the below issue (mentioned here in more details.).

status: Failure(ActionError(ActionError { index: Some(0), kind: FunctionCallError(ExecutionError("Exceeded the prepaid gas.")) }

I have written a helper function to mimic compile_project functionality. It does not do error handling as well as the workspaces library but it is working. The reason of above issue produced by workspaces-rs version [0.7.0] is still unknown. However, the workspaces-rs current unreleased codebase do have updates for this function. We can switch to using workspaces-rs if we solve the issue in the future. For noe we continue with the helper function.

[frol]

Can you make this README formatting look nicer?

[frol]

I am marking this PR as draft as CI still fails.

[jaswinder6991]

I am marking this PR as draft as CI still fails.

The CI worked fine a few weeks ago. Now I am seeing the same Gas Exceeded Error for which I wrote the custom function.
Details mentioned here: #46 (comment)

I will look into it again. However, can you think of a reason why self_upgrade would fail with prepaid gas exceeded error.

[jaswinder6991]

The Prepaid Gas exceeded issue occured due to lack of gas assigned in self_upgrade function to code deployment and function execution. This PR solves it: #53

[frol]

@jaswinder6991 I had refactored some bits of the changes, please, review them for your future reference.