Should use the different storage account and eventhub namespace variables for live tests

[moarychan]

Follow this PR Upgrade Sinks api for eventhub/servicebus IT case's comments, improve live test configuration for reducing resource creation.

Conclusion:

• We should use different eventhub namespaces and storage account for each IT class due to the different parameter 'baseName' value.
• Use junit 5 classes.

[moarychan]

@saragluna please help to commit the live test command, thanks.

[chenrujun]

/azp run java - spring - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[chenrujun]

Please check the pipeline log, make sure related integration tests are executed.

I'm fixing the problem that pipeline passed but tests are not executed.
Refs: #20700

[backwind1233]

/azp run java - spring - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run java - [service] - ci

[saragluna]

/azp run java - spring - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[backwind1233]

/azp run java - spring - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[saragluna]

/azp run java - spring - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[saragluna]

LGTM.

[moarychan]

Hi @saragluna , I found the guide about migration from Junit 4 and the other post of Junt 5 architecture introduce. Currently, the configuration will trigger all Junit test cases we used, after upgrade all the Junit 4 test cases, it's possible to remove the junit-vintage-engine and junit dependencies in each pom.xml file.