Issue with Test Plan (StaticTestSuite) migration..

[sridharravva]

@MrHinsh
I am trying to migrate my Test Plans that has state field with "Active" value in it from source TFS server (TFS 2015) into Target TFS Server (TFS 2017).
It tries to create the test plan (StaticTestSuite) and as soon as it hits this line ((IStaticTestSuite)parent).Entries.Add(newTestSuite);
under method SaveNewTestSuiteToPlan, it throws out the exception message saying "The field 'State' contains the value 'Active' that is not in the list of supported values"

Can you please advise what could be cause of this issue? Please let me know if I am missing anything over here or if the "State" field for this Test plan needs to be changed to something to migrate it to TFS 2017 server.
Thanks for the help!

[18:29:45 INF] Migration Context Complete TestConfigurationsMigrationContext
[18:30:05 INF] == Plan[1/1] Suite[1/2] Cases[0/0] - suiteid[214142] | Processing StaticTestSuite : 214142 - New_Static_Suite_ABC
[18:30:10 INF] == Plan[1/1] Suite[1/2] Cases[0/0] - suiteid[0 ] | Saving StaticTestSuite : 0 - New_Static_Suite_ABC

Exception/Error Message :
at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.HandleReply(TfsClientOperation operation, TfsMessage message, Object[]& outputs)
at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.Invoke(TfsClientOperation operation, Object[] parameters, TimeSpan timeout, Object[]& outputs)
at Microsoft.TeamFoundation.TestManagement.Client.TestManagementWebService4.AddSuiteToSuite(IdAndRev parent, ServerTestSuite suite, String teamProjectName, UpdatedProperties& newSuiteProperties, Int32 toIndex)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteHelper.<>c__DisplayClass26_0.b__0()
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteHelper.TrySuiteOperationWithRefreshAndRetry(Action operation, TestSuite& source, TestSuite& destination)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteHelper.ServerAddSuiteToSuite(TestSuite parent, TestSuite child, Int32 toIndex)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuite.InsertSuiteEntry(Int32 newIndex, TestSuiteEntry entry)
at Microsoft.TeamFoundation.TestManagement.Client.GenericCollection`2.Add(TInterface item)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteEntryCollection.Add(ITestSuiteBase suite)
at VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.SaveNewTestSuiteToPlan(ITestPlan testPlan, IStaticTestSuite parent, ITestSuiteBase newTestSuite) in C:\azure-devops-migration-tools-11.9.26\src\VstsSyncMigrator.Core\Execution\MigrationContext\TestPlansAndSuitesMigrationContext.cs:line 962

[sridharravva]

Could you please provide any comments on this reported issue as in what could have caused this reported issue while migrating the test plans from Source TFS 2015 to Target TFS 2017? Please let me know if I am missing anything over here or any configuration issue in configuration.json file.
Below is my configuration.json that I am using for migrating test plans from source TFS Server into Target TFS Server.
configuration_TestPlansMigrate.json.txt

Here it is error message that I am getting while migrating test plans for your reference :
2021-01-11 21:51:13.510 -05:00 [FTL] Error while running TestPlansAndSuitesMigrationContext
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at Microsoft.Extensions.Logging.LogValuesFormatter.GetValue(Object[] values, Int32 index)
at Microsoft.Extensions.Logging.FormattedLogValues.d__14.MoveNext()
at Serilog.Extensions.Logging.SerilogLogger.Log[TState](LogLevel logLevel, EventId eventId, TState state, Exception exception, Func3 formatter) at Microsoft.Extensions.Logging.Logger1.Microsoft.Extensions.Logging.ILogger.Log[TState](LogLevel logLevel, EventId eventId, TState state, Exception exception, Func`3 formatter)
at Microsoft.Extensions.Logging.LoggerExtensions.Log(ILogger logger, LogLevel logLevel, EventId eventId, Exception exception, String message, Object[] args)
at Microsoft.Extensions.Logging.LoggerExtensions.LogError(ILogger logger, Exception exception, String message, Object[] args)
at VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.SaveNewTestSuiteToPlan(ITestPlan testPlan, IStaticTestSuite parent, ITestSuiteBase newTestSuite) in C:\azure-devops-migration-tools-11.9.26\src\VstsSyncMigrator.Core\Execution\MigrationContext\TestPlansAndSuitesMigrationContext.cs:line 966
at VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.ProcessTestSuite(ITestSuiteBase sourceSuite, ITestSuiteBase targetParent, ITestPlan targetPlan) in C:\azure-devops-migration-tools-11.9.26\src\VstsSyncMigrator.Core\Execution\MigrationContext\TestPlansAndSuitesMigrationContext.cs:line 869
at VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.ProcessTestPlan(ITestPlan sourcePlan) in C:\azure-devops-migration-tools-11.9.26\src\VstsSyncMigrator.Core\Execution\MigrationContext\TestPlansAndSuitesMigrationContext.cs:line 772
at VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.InternalExecute() in C:\azure-devops-migration-tools-11.9.26\src\VstsSyncMigrator.Core\Execution\MigrationContext\TestPlansAndSuitesMigrationContext.cs:line 88
at MigrationTools._EngineV1.Processors.MigrationProcessorBase.Execute() in C:\azure-devops-migration-tools-11.9.26\src\MigrationTools_EngineV1\Processors\MigrationProcessorBase.cs:line 46
2021-01-11 21:51:13.535 -05:00 [ERR] TestPlansAndSuitesMigrationContext The Processor MigrationEngine entered the failed state...stopping run

-----------------------------------------------------------------------------------------------

"'Active' is not a valid status of TestSuite."
" at Microsoft.TeamFoundation.TestManagement.Client.ProcessConfigurationBase.ConvertStatusToState(String newstatus)\r\n at Microsoft.TeamFoundation.TestManagement.Client.TestSuite.get_State()"

'((Microsoft.TeamFoundation.TestManagement.Client.TestSuite)parent).State' threw an exception of type 'Microsoft.TeamFoundation.TestManagement.Client.TestManagementValidationException'

{"The field 'State' contains the value 'Active' that is not in the list of supported values"}
at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.HandleReply(TfsClientOperation operation, TfsMessage message, Object[]& outputs)
at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.Invoke(TfsClientOperation operation, Object[] parameters, TimeSpan timeout, Object[]& outputs)
at Microsoft.TeamFoundation.TestManagement.Client.TestManagementWebService4.AddSuiteToSuite(IdAndRev parent, ServerTestSuite suite, String teamProjectName, UpdatedProperties& newSuiteProperties, Int32 toIndex)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteHelper.<>c__DisplayClass26_0.b__0()
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteHelper.TrySuiteOperationWithRefreshAndRetry(Action operation, TestSuite& source, TestSuite& destination)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteHelper.ServerAddSuiteToSuite(TestSuite parent, TestSuite child, Int32 toIndex)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuite.InsertSuiteEntry(Int32 newIndex, TestSuiteEntry entry)
at Microsoft.TeamFoundation.TestManagement.Client.GenericCollection`2.Add(TInterface item)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteEntryCollection.Add(ITestSuiteBase suite)
at VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.SaveNewTestSuiteToPlan(ITestPlan testPlan, IStaticTestSuite parent, ITestSuiteBase newTestSuite) in C:\azure-devops-migration-tools-11.9.26\src\VstsSyncMigrator.Core\Execution\MigrationContext\TestPlansAndSuitesMigrationContext.cs:line 962

[MrHinsh]

Are the States the same on the TestSuit work item type between the two locations?

[sridharravva]

Yes, the States are same on both the TestSuite and also Test Plan work item types on both Source TFS Server and Target TFS Server, please refer below screenshot for your reference.

TestSuite showing States dropdown values and having these same values at both locations:

TestPlan showing States dropdown values and having these same values at both locations:

[sridharravva]

Please let me know if @MrHinsh or anyone has any update on this test plans migration issue, and how to go about to resolve this issue, if there are any suggestion, kindly advice on the same. Thanks!

[MrHinsh]

I am unable to reproduce. Perhaps debugging in Visual Studio will yield results. Have you tried that?

Also providing the whole log and config would be valuable.

[sridharravva]

@MrHinsh :
Yes, I have tried debugging it in Visual studio and it was keep failing at this line for this method (VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.SaveNewTestSuiteToPlan) and I was getting the same below exception only :
**Attached the whole log and configuration.js file for your reference.

By the way, I ran the migration tool for the first run with work items and I believe, it creates Test cases already at the first run with
this processor config "WorkItemMigrationConfig" and in the second run I have added these configs (TestVariablesMigrationConfig, TestConfigurationsMigrationConfig and TestPlansAndSuitesMigrationConfig) to create test plans, test suites etc. Please let me know if I am missing anything over here. Thanks for the help!

configuration.json.txt

migration.log
**

Here it is error message that I am getting while migrating test plans for your reference :
2021-01-11 21:51:13.510 -05:00 [FTL] Error while running TestPlansAndSuitesMigrationContext
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at Microsoft.Extensions.Logging.LogValuesFormatter.GetValue(Object[] values, Int32 index)
at Microsoft.Extensions.Logging.FormattedLogValues.d__14.MoveNext()
at Serilog.Extensions.Logging.SerilogLogger.Log[TState](LogLevel logLevel, EventId eventId, TState state, Exception exception, Func3 formatter) at Microsoft.Extensions.Logging.Logger1.Microsoft.Extensions.Logging.ILogger.Log[TState](LogLevel logLevel, EventId eventId, TState state, Exception exception, Func`3 formatter)
at Microsoft.Extensions.Logging.LoggerExtensions.Log(ILogger logger, LogLevel logLevel, EventId eventId, Exception exception, String message, Object[] args)
at Microsoft.Extensions.Logging.LoggerExtensions.LogError(ILogger logger, Exception exception, String message, Object[] args)
at VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.SaveNewTestSuiteToPlan(ITestPlan testPlan, IStaticTestSuite parent, ITestSuiteBase newTestSuite) in C:\azure-devops-migration-tools-11.9.26\src\VstsSyncMigrator.Core\Execution\MigrationContext\TestPlansAndSuitesMigrationContext.cs:line 966
at VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.ProcessTestSuite(ITestSuiteBase sourceSuite, ITestSuiteBase targetParent, ITestPlan targetPlan) in C:\azure-devops-migration-tools-11.9.26\src\VstsSyncMigrator.Core\Execution\MigrationContext\TestPlansAndSuitesMigrationContext.cs:line 869
at VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.ProcessTestPlan(ITestPlan sourcePlan) in C:\azure-devops-migration-tools-11.9.26\src\VstsSyncMigrator.Core\Execution\MigrationContext\TestPlansAndSuitesMigrationContext.cs:line 772
at VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.InternalExecute() in C:\azure-devops-migration-tools-11.9.26\src\VstsSyncMigrator.Core\Execution\MigrationContext\TestPlansAndSuitesMigrationContext.cs:line 88
at MigrationTools._EngineV1.Processors.MigrationProcessorBase.Execute() in C:\azure-devops-migration-tools-11.9.26\src\MigrationTools_EngineV1\Processors\MigrationProcessorBase.cs:line 46
2021-01-11 21:51:13.535 -05:00 [ERR] TestPlansAndSuitesMigrationContext The Processor MigrationEngine entered the failed state...stopping run

---

"'Active' is not a valid status of TestSuite."
" at Microsoft.TeamFoundation.TestManagement.Client.ProcessConfigurationBase.ConvertStatusToState(String newstatus)\r\n at Microsoft.TeamFoundation.TestManagement.Client.TestSuite.get_State()"

'((Microsoft.TeamFoundation.TestManagement.Client.TestSuite)parent).State' threw an exception of type 'Microsoft.TeamFoundation.TestManagement.Client.TestManagementValidationException'

{"The field 'State' contains the value 'Active' that is not in the list of supported values"}
at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.HandleReply(TfsClientOperation operation, TfsMessage message, Object[]& outputs)
at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.Invoke(TfsClientOperation operation, Object[] parameters, TimeSpan timeout, Object[]& outputs)
at Microsoft.TeamFoundation.TestManagement.Client.TestManagementWebService4.AddSuiteToSuite(IdAndRev parent, ServerTestSuite suite, String teamProjectName, UpdatedProperties& newSuiteProperties, Int32 toIndex)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteHelper.<>c__DisplayClass26_0.b__0()
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteHelper.TrySuiteOperationWithRefreshAndRetry(Action operation, TestSuite& source, TestSuite& destination)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteHelper.ServerAddSuiteToSuite(TestSuite parent, TestSuite child, Int32 toIndex)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuite.InsertSuiteEntry(Int32 newIndex, TestSuiteEntry entry)
at Microsoft.TeamFoundation.TestManagement.Client.GenericCollection`2.Add(TInterface item)
at Microsoft.TeamFoundation.TestManagement.Client.TestSuiteEntryCollection.Add(ITestSuiteBase suite)
at VstsSyncMigrator.Engine.TestPlandsAndSuitesMigrationContext.SaveNewTestSuiteToPlan(ITestPlan testPlan, IStaticTestSuite parent, ITestSuiteBase newTestSuite) in C:\azure-devops-migration-tools-11.9.26\src\VstsSyncMigrator.Core\Execution\MigrationContext\TestPlansAndSuitesMigrationContext.cs:line 962

[sridharravva]

@MrHinsh , Any updates on this issue? Please let me know. Thanks!

[MrHinsh]

When debugging you can add a break just before the save and inspect the State field. Look for any mismatch between the Allowed values and the actual values.

[sridharravva]

@MrHinsh I have debugged the migration tool code for version 11.9.30 and finally, I have found the root cause of this test plans migration issue. Thanks for the help!
One last thing I would like to confirm, can you please confirm if I have got the below configuration.json correctly configured that I am planning to use it to migrate all test plans, test suites and test cases from source TFS Server into target TFS Server.

Attached configuration.json for all test plans, test suites and test cases migration. Please confirm if this looks good to you or if I am missing any configurations that needs to be added in configuration.json in order to migrate correctly all test plans, test suites and test cases.
configuration_TestPlansCasesSuitesMigration.json.txt

[sridharravva]

@MrHinsh,

1. can you please confirm if I have got the below configuration.json correctly configured that I am planning to use it to migrate all test plans, test suites and test cases from source TFS Server into target TFS Server.

Attached configuration.json for all test plans, test suites and test cases migration. Please confirm if this looks good to you or if I am missing any configurations that needs to be added in configuration.json in order to migrate correctly all test plans, test suites and test cases.

configuration_TestPlansCasesSuitesMigration.json.txt

2. Secondly, do we need to run this migration tool 2 times always, like for the first time, do we need to migrate all other work items except Test plans and Test Suites? And for the second run, do we need to run this migration tool again for second time in order to migrate correctly Test plans, Test Suites and Test Cases? OR Can we run this migration tool at once only one time in order to migrate all the work items including Test plans, Test Suites and Test Cases. Please confirm the same how efficiently can we run this migration tool. Thanks!

[MrHinsh]

1 - I don't see an issue. Try removing all of the field maps

2 - Correct

[sridharravva]

@MrHinsh , For 2) Are you saying Correct for this thing? Please confirm the same.
<<Secondly, do we need to run this migration tool 2 times always, like for the first time, do we need to migrate all other work items except Test plans and Test Suites? And for the second run, do we need to run this migration tool again for second time in order to migrate correctly Test plans, Test Suites and Test Cases?>>

[sridharravva]

@MrHinsh , I just want to double check on this: So For 2) Are you saying Correct for this below thing? Please confirm the same.
<<Secondly, do we need to run this migration tool 2 times always, like for the first time, do we need to migrate all other work items except Test plans and Test Suites? And for the second run, do we need to run this migration tool again for second time in order to migrate correctly Test plans, Test Suites and Test Cases?>>

[MrHinsh]

This should be fixed with #883 !