Advanced integration testing #4
Conversation
|
@bkchr how would this testing be different from the emulated integration tests? They cover the runtime config and inter-parachain integration too. |
|
Yeah. I included these in the "existing integration tests". Generally these are complicated to maintain. Just look at the sdk upgrade prs and the changes required to these tests. They are also complicated to write. Also they are mainly being used for Xcm right now :) |
| The runtimes governed by the *Polkadot Technical Fellowship* are built using FRAME. FRAME provides a lot of small components, the pallets, when combined together form a runtime. | ||
| Each pallet is tested extensively via unit tests. However, the exact behavior of these pallets in the final runtime depends on their configuration in each runtime. So, integration tests are a must. | ||
| The runtimes themselves provide some integration tests, but their coverage is quite low. The [ecosystem tests](https://github.com/open-web3-stack/polkadot-ecosystem-tests) are integration tests | ||
| that are tailored for XCM, but could maybe also be extended for other use cases. |
There was a problem hiding this comment.
could maybe also be extended for other use cases.
I have been working on just that: testing use cases beyond XCM (see PET PRs #115, #165, #174, #195).
These contemplate the use-case you mention below:
End user focused integration tests should ensure that basic functionality, like sending some tokens, is working as expected
Whoever picks this up can take a look at the above work; I believe it'll be a helpful example, whether to a human or an AI system.
See the text :)