Automated cross-compatibility checking between various implementations

[drewhk]

Apart from the TCK, which is a common point to be validated against, it would be nice to have a test infastructure which plugs together various different implementations and tests that they work together properly.

This ticket might not be strictly in the scope of this project (it is more of a "community" effort), but I found this to be the best place for this proposal.

[viktorklang]

👍

It sounds like that fits well into the plan to have 2+ TCK-passing impls before 1.0-RC1—i.e. we could make a test for the reactive-streams project that runs interop-checking of all TCK-passing impls. Wdyt?

[drewhk]

The complete interop-checking will grow as O(n^2) but we are not there yet where this is an issue, so why not.

[viktorklang]

@drewhk Iso going n^2 we can go stochastic

[drewhk]

Yep

[ktoso]

Neat idea, I like it. Good place to discuss this, but in the end it would probably end up being better served as separate repo (with more loose PR rules?)

[viktorklang]

This seemed to never be needed. A testament to the quality of the TCK!