There is a Jenkins job available for running Network Scenario tests. To run, use the Build with Parameters button and enter the appropriate information. You can change the fork and branch for the azure-powershell GitHub repo. Additionally, you can use your own service principal and subscription by entering the clientID, clientSecret, tenantId, and subId. The default values use our test subscription and service principal for running tests.
The test results are created as build artifacts in the Jenkins job. The NetworkTests.htm is the xUnit tests results log. The artifacts also contain a folder, src/Network/Network.Test/bin/Debug/SessionRecords. This folder has subfolders for all the session records created when running the tests.
Note: A session records are created for all tests, despite if they pass or fail. Make sure to only use session records from passing tests if you use these files to update the stored records in the repo.
Some tests may fail if you do not have the appropriate features enabled on your subscription. If the test requires a certain feature, here is an example how to register for a feature.
# If your subscription is not registered with the provider...
Register-AzureRmResourceProvider -ProviderNamespace Microsoft.Network
# Register the feature
Register-AzureRmProviderFeature -FeatureName AllowApplicationSecurityGroups -ProviderNamespace Microsoft.Network
# Check registration
Get-AzureRmProviderFeature -FeatureName AllowApplicationSecurityGroups -ProviderNamespace Microsoft.NetworkRegister the feature AllowApplicationSecurityGroups for Microsoft.Network to your subscription.
Register the feature AllowILBAllPortsRule for Microsoft.Network to your subscription.
Register for the Load Balancer Standard Preview on your subscription.
Enable Availability Zones for your subscription.
Register for the Standard SKU Preview on your subscription.