diff --git a/docs/running-verification-tests.md b/docs/running-verification-tests.md
index 4898a9e7..de54de07 100644
--- a/docs/running-verification-tests.md
+++ b/docs/running-verification-tests.md
@@ -1,7 +1,19 @@
 # Running Verification Tests On Your Local Machine
 Verification tests are used to confirm that no detectors are lost when changes are made to the project. The tests are run on every PR build. They work by comparing the detection results from the main branch to detection results from the new changes on your PR. You can follow the steps below to run them locally.
 
-## Step 1 : Run Detection on the main branch
+An automation script is created to setup the  test artifact and execute the verification test. Ensure that your local changes builds and execute following powershell script **from repository root**.
+
+```
+.\test\Microsoft.ComponentDetection.VerificationTests\resources\VerificationTest.ps1
+```
+
+### Debug using visual studio
+The automation script above will output variables that needs to be replaced in `ComponentDetectionIntegrationTests.cs` file. Then, verification test can be debugged through Test Explorer by opening `\test\Microsoft.ComponentDetection.VerificationTests\Microsoft.DependencyDetective.VerificationTests.csproj` in visual studio. 
+
+
+## Manual setup
+
+### Step 1 : Run Detection on the main branch
 
 - Checkout the main branch in your local repo
 - Create a folder to store detection results (e.g C:\old-output-folder)
@@ -14,7 +26,7 @@ For Example:
 ```dotnet run scan --Verbosity Verbose --SourceDirectory C:\componentdetection --Output C:\old-output-folder```
 
 
-## Step 2 : Run Detection on your new branch
+### Step 2 : Run Detection on your new branch
 
 - Checkout the branch with the new changes you are trying to merge
 - Create a folder to store detection results. This folder should be seperate from the one you used in Step 1 (e.g C:\new-output-folder)
@@ -26,7 +38,7 @@ For Example:
 
 ```dotnet run scan --Verbosity Verbose --SourceDirectory C:\componentdetection --Output C:\new-output-folder```
 
-## Step 3 : Update variables in the test
+### Step 3 : Update variables in the test
 
 - Open the Microsoft.ComponentDetection.VerificationTests project in VS Studio
 - Navigate to  `GatherResources()`  in `ComponentDetectionIntegrationTests.cs`
@@ -36,7 +48,7 @@ For Example:
     - `allowedTimeDriftRatioString`:  This should be ".75"
 
 
-## Step 4: Run The tests
+### Step 4: Run The tests
 You can run the tests in two ways:
 - Run or Debug the tests in test explorer.
 - Use the command line to navigate to the Microsoft.ComponentDetection.VerificationTests folder, and run `dotnet test`.
\ No newline at end of file
diff --git a/test/Microsoft.ComponentDetection.VerificationTests/resources/VerificationTest.ps1 b/test/Microsoft.ComponentDetection.VerificationTests/resources/VerificationTest.ps1
new file mode 100644
index 00000000..66093206
--- /dev/null
+++ b/test/Microsoft.ComponentDetection.VerificationTests/resources/VerificationTest.ps1
@@ -0,0 +1,64 @@
+Set-StrictMode -Version 2.0
+$Script:ErrorActionPreference = 'Stop'
+
+function main()
+{
+    Write-Progress "starting verification tests."
+    $repoPath = Get-Location
+    $workspace = (Get-Item  $repoPath).Parent.FullName
+
+    # Test data directory is cleaned up before each run, we want to avoid the conflict and accidental removal of any other existing directory. 
+    # incorporating uid in testdata directory ensures there is no conflict in directory name. 
+    $uidForTestData = "1f8835c2" 
+    $testDataDir = $workspace + "\cd-verification-testdata-" + $uidForTestData
+
+    if (Test-Path $testDataDir) {
+        Write-Progress "Removing existing test data directory from previous runs at $testDataDir"
+        Remove-Item $testDataDir -Force -Recurse
+    }
+    
+    Write-Progress "Creating test data directory at $testDataDir"
+    mkdir $testDataDir
+
+    $verificationTestRepo = (Get-Item  $repoPath).FullName + "\test\Microsoft.ComponentDetection.VerificationTests\resources"
+    $CDRelease =  $testDataDir + "\component-detection-release"
+    $output = $testDataDir + "\output"
+    $releaseOutput = $testDataDir + "\release-output"
+
+    Write-Progress "cloning released component-detection at $CDRelease"
+    git clone "https://github.com/microsoft/component-detection.git" $CDRelease
+
+    mkdir $output
+    mkdir $releaseOutput
+
+    Write-Progress "Running detection....."
+    Set-Location (Get-Item  $repoPath).FullName
+    dotnet restore
+    Set-Location ((Get-Item  $repoPath).FullName + "\src\Microsoft.ComponentDetection")
+    dotnet run scan --SourceDirectory $verificationTestRepo --Output $output
+
+    Set-Location $CDRelease
+    dotnet restore
+    Set-Location ($CDRelease + "\src\Microsoft.ComponentDetection")
+    dotnet run scan --SourceDirectory $verificationTestRepo --Output $releaseOutput
+
+    
+
+    $env:GITHUB_OLD_ARTIFACTS_DIR = $releaseOutput
+    $env:GITHUB_NEW_ARTIFACTS_DIR = $output
+    $env:ALLOWED_TIME_DRIFT_RATIO = "0.75"
+
+    Write-Progress "Executing verification tests....."
+    Set-Location ((Get-Item  $repoPath).FullName + "\test\Microsoft.ComponentDetection.VerificationTests\")
+    dotnet restore  
+    dotnet test
+
+    Set-Location $repoPath
+
+    Write-Host "Verification tests were completed. The generated testdata can be found at $testDataDir `n To debug test with visual studio, replace values for following variables in ComponentDetectionIntegrationTests.cs"  -ForegroundColor red -BackgroundColor white
+    Write-Host "oldGithubArtifactsDir = @`"$releaseOutput`""  -ForegroundColor red -BackgroundColor white
+    Write-Host "newGithubArtifactsDir = @`"$output`""  -ForegroundColor red -BackgroundColor white
+    Write-Host "allowedTimeDriftRatioString = "`"0.75`"  -ForegroundColor red -BackgroundColor white
+}
+
+main
\ No newline at end of file