Open weidongxu-microsoft opened 1 year ago
I'm adding test to postgresqlflexibleserver. @v-hongli1 You can leave this out.
In Sept. (service may do it themselves)
Although the selfhelp
service can create diagnostics
, it does not have the deletion function and requires the intervention of azuer supporter. so it is recommended that the service does not add any live test cases.
The networkcloud
service needs to specify an ISP
provider when creating an application service, so it is recommended that the service does not add any live test cases.
A few new GAed (or to be GAed) libs
The kubernetesconfiguration
service needs Owner
permission, but a empower exceptions occurs when deploy test resources. so it is recommended that the service does not add any live test cases.
DployTestResource.log
HybridCompute
needs to be used in the live test case of the HybridConnectivity
service, but this front-end service can only be created through bicep
, arm template
or terraform
. I think this way of creating front-end services is not suitable for appearing in live tests. so it is recommended that the service does not add any live test cases.
Sure. Just check the box that you've added live test (in comments above).
The connectedvmware
service must be supported by the front-end service Kubernetes cluster with Azure Arc
, but Kubernetes cluster with Azure Arc
can only be created by script. This way of creating front-end services is not suitable for use in live test. So it is recommended that the service does not add any live test cases.
The azure-resourcemanager-nginx
requires the use of paid azure service NGINXSaas
, so it is recommended that the service does not add any live test cases.
The azure-resourcemanager-mobilenetwork
service involves property settings of mobile network providers, so it is recommended that the service does not add any live test cases.
The azure-resourcemanager-confluent
service requires permission to create Marketplace offer
on Partner Center, so it is recommended that the service does not add any live test cases.
The live test case of the service healthcareapis
has been added at 2024/2/9.
The hybridcontainerservic
e service must be supported by the front-end service Kubernetes cluster with Azure Arc
, but Kubernetes cluster with Azure Arc
can only be created by script. So just leave a List (and enable that test).
The resource removal method is missing in the azure-resourcemanager-support
service, so it is recommended not to add any live test cases for this service.
Guide https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/resourcemanager/docs/HOW_TO_ADD_LIVE_TESTS.md
Sample PR (databricks) https://github.com/Azure/azure-sdk-for-java/pull/35315
Test can be very simple, just find the basic resource, create it (one can refer to samples for parameters, but it could be wrong; a better place would be Portal and its "export ARM template"), do some get/list, then delete it in
finally
block.Have a pair of
// @embedmeStart
// @embedmeEnd
enclosing the code that create a resource. Autorest.Java will extract it to README.md "Examples" section in next codegen.Following lib would be avoided at present
test-resources.json/bicep
), e.g. https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/eventgridPS: for shared folder, we should be able to specify another folder for bicep in "tests.mgmt.yml" e.g. https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/communication/communication-tests-template.yml#L14-L17. But better to delay it, as they are not many.
high priority
lower priority