Description

We're working on interoperability tests with the go & rust libp2p projects,
we want to express:

• test cross-version compatibility in go: a go test built with different go versions and different libraries versions,
• test cross-version compatibility in rust: a rust test built with different rust versions and different libraries versions,
• test cross-implementation compatibility: a combination of the tests above that compares go and rust implementations.

There are ways to "hack" these using file manipulations, artifacts rewrites, etc. But we want to move past scripts & tweaks now.

What defines this endeavour to be complete?

• go interoperability testing
  • have the ability to run the same test written in go, but using different modfiles and different go versions, (Add additional parameters to groups in composition files #1337)
• rust interoperability testing (will be implemented later)
  • implement native rust support,
  • add dependencies rewrite in rust (similar to go), and maybe selectors support too (to be discussed with Rust maintainers),
  • have the ability to run the same test written in rust, but using different cargofiles,
• go - rust interoperability testing (Add builders parameters to groups in composition files #1357)
  • add the ability to run multiple test plan (one test in go and one test in rust) with the same composition file, (Run plan with two instances based on two different builds #1305)