Setup Integration Test

[Latrasis]

Reviewing #151, we sorely need a better test setup:

Integration Tests

Doing an integration test requires;

• Compiling a list of rust contracts to ewasm, for each contract:
  • Link the required rust modules
  • Compiled to wasm32-unknown-unknown
  • Inject cap9_syscall_low using cap9-build
  • Converted to ewasm using wasm-build and output *Contract.json Interface File
• Once done, the test script should have access to a *.wasm binary and *.json definition for each test contract

[JakeOShannessy]

Can I also request that we move the kernel down to the same level as the other crates and create a workspace? It'll make it easier to navigate and allow us to use cargo and RLS more easily.

[Latrasis]

@JakeOShannessy: Can you elaborate? Do you mean moving the kernel-ewasm code into the main directory?

[Latrasis]

One of the reasons I setup the kernel-evm1 and kernel-ewasm so that we work on the them seperately without merge conflicts. Would it be possible to move cap9-build into the kernel-ewasm instead?

For RLS to work, you just need to open the kernel-ewasm directory in vscode instead of the whole repo.

[JakeOShannessy]

Nope, I mean all of the contents of kernel-ewam. There are 4 crates in there currently, partly forced by separate contracts needing to be separate libs. 3 of the crates are inside another crate, and there is no workspace to coordinate them by.

[Latrasis]

How about moving cap9-build into kernel-ewasm, move the kernel code into a seperate crate and setup a workspace just in the kernel-ewasm folder. That way we don't have crates inside other crates and the ewasm code stays in a seperate folder.

[JakeOShannessy]

That's exactly what I mean.