Duplicate test Plan Names message update #2616
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… plan names Enhance the `FindTestPlan` method to handle scenarios where multiple test plans have the same name. Previously, the code assumed that test plan names were unique, which could lead to unexpected behavior or errors if duplicates existed. The updated logic checks for multiple test plans with the same name, logs a warning with their IDs, and throws an exception to prevent further execution. This ensures that the migration process does not proceed with ambiguous test plan identification, maintaining data integrity.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-river-093197403-2616.westeurope.5.azurestaticapps.net |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🐛 (TfsTestPlansAndSuitesMigrationProcessor.cs): handle duplicate test plan names
Enhance the
FindTestPlanmethod to handle scenarios where multiple test plans have the same name. Previously, the code assumed that test plan names were unique, which could lead to unexpected behavior or errors if duplicates existed. The updated logic checks for multiple test plans with the same name, logs a warning with their IDs, and throws an exception to prevent further execution. This ensures that the migration process does not proceed with ambiguous test plan identification, maintaining data integrity.