FIxing the input parity test (#9897)

Author: prawalagarwal

Tasks/VsTestV2/inputdatacontract.ts

@@ -24,6 +24,7 @@ export interface TestReportingSettings {
     TestRunTitle : string;
     TestResultsDirectory : string;
     TestRunSystem : string;
+    TestSourceSettings : TestSourceSettings;
 }
 
 export interface TestSelectionSettings {
@@ -102,6 +103,10 @@ export interface ExecutionSettings {
     DiagnosticsSettings : DiagnosticsSettings;
 }
 
+export interface TestSourceSettings {
+    PullRequestTargetBranchName : string;
+}
+
 export interface DiagnosticsSettings {
     Enabled : boolean;
     DumpCollectionType : string;

Tasks/VsTestV2/inputparser.ts

@@ -158,7 +158,9 @@ function getTestReportingSettings(inputDataContract : idc.InputDataContract) : i
     inputDataContract.TestReportingSettings = <idc.TestReportingSettings>{};
     inputDataContract.TestReportingSettings.TestRunTitle = tl.getInput('testRunTitle');
     inputDataContract.TestReportingSettings.TestRunSystem = 'VSTS - vstest';
-
+    inputDataContract.TestReportingSettings.TestSourceSettings = <idc.TestSourceSettings>{};
+    inputDataContract.TestReportingSettings.TestSourceSettings.PullRequestTargetBranchName = tl.getVariable('System.PullRequest.TargetBranch');
+    
     if (utils.Helper.isNullEmptyOrUndefined(inputDataContract.TestReportingSettings.TestRunTitle)) {
 
         let definitionName = tl.getVariable('BUILD_DEFINITIONNAME');

Tasks/VsTestV2/task.loc.json

@@ -620,4 +620,4 @@
     "diagnosticsInput": "ms-resource:loc.messages.diagnosticsInput",
     "UncPathNotSupported": "ms-resource:loc.messages.UncPathNotSupported"
   }
-}
+}