Improvement for test, #789 and #788

[dolauli]

Live Only Test

Describe 'New-AzDatabricksWorkspace' -Tag 'LiveOnly'{
}

Run Specific Test Cases

./test-module.ps1 -TestName Get-AzDatabricksWorkspace,New-AzDatabricksWorkspace

Record Specific Test Cases

# -UsePreviousConfigForRecord
# When this switch is turned on, we will try to use values defined in env.json instead of randomly
# generating them 
./test-module.ps1 -TestName Get-AzDatabricksWorkspace,New-AzDatabricksWorkspace -Record -UsePreviousConfigForRecord

Required Code Change to Support Recording Specific Cases

Change #1

Previous

$null = $env.Add("rstr5", $rstr5)

Now

$rstr5 = $env.AddWithCache("rstr5", $rstr5, $UsePreviousConfigForRecord)

Or

Use following if some values are generated in service side.

$rstr5 = $env.AddWithCache("rstr5", $rstr5, $false)

Change #2

Add following if clause in the header of each test script which ends with .Tests.ps1. And you should replace 'Get-AzDatabricksVNetPeering' with the name in your test Describe.

if (($null -eq $TestName) -or ($TestName -contains 'Get-AzDatabricksVNetPeering')) {
    $loadEnvPath = Join-Path $PSScriptRoot 'loadEnv.ps1'
		.....
		. ($mockingPath | Select-Object -First 1).FullName
}

Limitations When Supporting Recording Specific Cases

Subscription can not be changed

Solutions:

• Full record
• After partial recording, replace the old subscription Id with the new one

Some data is generated in service side

For data like this, we can not use the previous one in env.json.