[improve][pip] PIP-390 Improve the reusability of Pulsar test code and best practice for unit and integration tests for Pulsar

[heesung-sn]

This is a PIP

[github-actions]

@heesung-sn Please add the following content to your PR description and select a checkbox:

- [ ] `doc` <!-- Your PR contains doc changes -->
- [ ] `doc-required` <!-- Your PR changes impact docs and you will update later -->
- [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
- [ ] `doc-complete` <!-- Docs have been already added -->

[zzzk1]

Suggested change

	- Currently, Pulsar tests run on the `testng` framework.
	- Currently, Pulsar tests run on the [TestNG](https://testng.org/#_welcome_to_testng).

[zzzk1]

I believe that directly providing the framework link may be clearer.

[falser101]

So is Pulsar's testing going to switch to using JUnit 5 and remove testng？

[lhotari]

So is Pulsar's testing going to switch to using JUnit 5 and remove testng？

@falser101 Perhaps eventually, but that will take a very long time. Instead of having the goal of converting from TestNG to JUnit5, I believe that it would be more valuable to first provide ways to create JUnit5 tests. There's not much value in doing a 1-to-1 mapping from TestNG to JUnit5.

[falser101]

So is Pulsar's testing going to switch to using JUnit 5 and remove testng？

@falser101 Perhaps eventually, but that will take a very long time. Instead of having the goal of converting from TestNG to JUnit5, I believe that it would be more valuable to first provide ways to create JUnit5 tests. There's not much value in doing a 1-to-1 mapping from TestNG to JUnit5.

yes, maybe we can commit the first JUnit5 test case

[heesung-sn]

I realized this pip is too much ambitious, and I am not sure it is practical any more. I am thinking of closing this PIP.