ci: add CI script for pop-api tests and integration tests

[chungquantin]

Link to issue: #109

• Build contracts listed under integration-tests/contracts when running cargo build --features integration-tests
• CI to run integration tests of contracts

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 34.10%. Comparing base (6482a43) to head (ba66dd9).

@@             Coverage Diff              @@
##           daan/api     #228      +/-   ##
============================================
+ Coverage     34.08%   34.10%   +0.02%     
============================================
  Files            34       34              
  Lines          3013     3011       -2     
  Branches       3013     3011       -2     
============================================
  Hits           1027     1027              
+ Misses         1954     1952       -2     
  Partials         32       32              

see 2 files with indirect coverage changes

[evilrobot-01]

Hmmm, could we not have solved this with a build.rs that takes a dependency on cargo-contract to build the relevant contracts?

[chungquantin]

@evilrobot-01 Thanks for the feedback. I have redesigned the CI to simplify the script and move the contract build process to the integration-tests crate build script. Please take a look and let me know if there are any needed changes.

cc: @Daanvdplas

[evilrobot-01]

Gave it a quick test and it failed as I did not specify the 'contracts' feature. Is there any reason that this needs to be specified explicitly? The goal is that we can just run cargo test in the integration tests folder and the build script will ensure that the contracts are built, as the integration tests are reliant on them being built.

Running it again with the feature then worked, but it took a long time on 'building' after having cleared out the caches of all contracts and integration tests. Would outputting something to the console help here possibly? Just a message stating 'building xxx contract...' for each should be enough.

[peterwht]

Great job, this will be quite useful! It would be a nice addition to have all .wasms get outputted to an artifacts folder. That way we can persist the same artifacts without requiring a rebuild of the contracts in CI.

[chungquantin]

@peterwht Contracts are archived as artifacts
@evilrobot-01 Remove contract feature, contracts are built whenever we run cargo test in the integration-tests folder

[evilrobot-01]

Rebuilding contracts each time should be instant if no changes and ensures that any local contract changes are always included when running tests, improving our devex flow.

In the past we had to know to run all these extra commands, now we just make changes and run the tests and everything 'just works'

[Daanvdplas]

Thanks a lot Tin! Provided a suggested refactor.

[evilrobot-01]

Looks fine and works as is. I personally dont see the need for storing the artifacts to would be interested to see how they will actually be used.

I still think that a console log per contract build would be better than nothing whatsoever, especially as we expect many more test contracts to be added in the near term.

[chungquantin]

Update:

• Remove archiving artifacts in the CI script
• Build mode is changed to Debug mode instead so we can track the debug message of the ink! contract.
• Build artifact is added with CodeOnly mode because we only need .wasm file for the integration tests, no metadata needed.

cc: @evilrobot-01 @peterwht @Daanvdplas

[Daanvdplas]

LGTM!