Rename repository to interop

[thomaseizinger]

Suggestion to change test-plans to interop-tests everywhere. I think it is more expressive in what these tests are testing.

[MarcoPolo]

Agreed. Lower priority for me, but I like it.

To list what else would have to change:

• go-libp2p test-plan test (and rename to interop-tests as well)
• rust-libp2p test-plan test (and rename to interop-tests as well)

[p-shahi]

Does interop-tests cover the scope of planned future tests too? And if we're already testing stuff like expected RTT, maybe it should be e2e-tests

[thomaseizinger]

Does interop-tests cover the scope of planned future tests too? And if we're already testing stuff like expected RTT, maybe it should be e2e-tests

Good point, I am okay with e2e-tests too.

[p-shahi]

Is doing this still worthwhile? I think it's a nice distinction to make and allows us to leave test-plans in the past but it also might be harder to pull off with the way testing is embedded in repo

[thomaseizinger]

I am almost certain that GitHub creates redirects if you rename a repo. Alternatively, we can just push it under a new name, update all implementation repositories and then delete this one.

[marten-seemann]

Yes, GitHub creates a redirect, I recently went through this process when I migrated quic-go to its own org. It still makes sense to update implementations to use the correct path.

That said, are we getting a lot out of a renaming?

[thomaseizinger]

With the redirect, the good news is that we don't have to do anything in lockstep, thus my point would be that a more expressive name is worth it.

Let's set a deadline for end of June.

Regarding the actual name, what I most commonly hear from people in conversations is interop-tests and not e2e-tests. interop-tests for me suggests that we are testing interoperability whereas e2e-tests has more a focus on testing functionality.

I'd consider hole-punching tests more on the functional side rather than on the interop side.

With the addition of the performance benchmarks, one could even debate whether "tests" is the right category for all of this. Just interop perhaps? Even with the addition of hole-punching tests, I find interop to be a much more intriguing name compared to e2e.

[p-shahi]

interop sounds good to me. Shall we go ahead with the change.

Let's set a deadline for end of June.

That sounds good.

That said, are we getting a lot out of a renaming?

It is cosmetic but why keep referring to test-plans when Testground is no longer used. It also is more evident to newcomers (new implementation adding their interop tests).

[thomaseizinger]

interop seems to be already taken by the JS specific interop runner? :/

https://github.com/libp2p/interop