Skip to content

Update reorder test cases section for clarity#14349

Open
gasparnagy wants to merge 1 commit intoMicrosoftDocs:mainfrom
gasparnagy:patch-2
Open

Update reorder test cases section for clarity#14349
gasparnagy wants to merge 1 commit intoMicrosoftDocs:mainfrom
gasparnagy:patch-2

Conversation

@gasparnagy
Copy link

Clarify that reordering test cases is not possible from the user interface.

The section "Reorder test cases" (https://learn.microsoft.com/en-us/azure/devops/test/create-test-cases?view=azure-devops#reorder-test-cases) is incorrect.

It shows a screenshot of an edit test case screen claiming that the shown up/down buttons change the order of the test case in the suite, but those up/down buttons are for the test steps of the test case and they change the order of test steps not the order of the test case within test suite. (This option would anyway be impossible, because one test case can be included in multiple test suite, so it could not know in which test suite it changes the order).

The question came up, because I do want to change the order of the test cases in a suite, but could not find any way to do it through the UI and I would be interested in finding a way.

But the method described in the documentation is wrong and the proposed change clarifies that.

Clarify that reordering test cases is not possible from the user interface.
@prmerger-automator
Copy link
Contributor

@gasparnagy : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @rohit-batra

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR corrects misleading documentation about reordering test cases in Azure DevOps Test Plans. The previous documentation incorrectly claimed that test cases could be reordered using up/down arrows, but those arrows actually reorder test steps within a test case, not the test cases themselves within a suite.

Changes:

  • Removed incorrect instructions and screenshot claiming test cases can be reordered via UI
  • Replaced with clear statement that test case reordering is not available from the user interface

Open a test case, and then use the up and down arrows to change the order.

![Screenshot showing the arrows used to move test steps up or down.](media/create-test-cases/change-step-order.png)
Currently you cannot reorder manual test cases in static suites, requirement-based suites, and query-based suites from the user interface.
Copy link

Copilot AI Jan 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The statement "Currently you cannot reorder manual test cases..." implies this might be a temporary limitation that could change in the future. Consider whether this is the intended message. If reordering test cases is not planned as a feature, consider removing "Currently" to avoid setting expectations. Alternatively, if there are plans to support this feature, consider adding a note about alternative methods (such as using APIs or third-party tools) if they exist.

Suggested change
Currently you cannot reorder manual test cases in static suites, requirement-based suites, and query-based suites from the user interface.
You cannot reorder manual test cases in static suites, requirement-based suites, and query-based suites from the user interface.

Copilot uses AI. Check for mistakes.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would wait for a general feedback from the MSFT team first, maybe they would like to have the section completely removed.

@prmerger-automator
Copy link
Contributor

@gasparnagy : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @rohit-batra

@v-dirichards
Copy link
Contributor

@mijacobs

Can you review the proposed changes? The original author is not with MSFT anymore, so we're reaching out to you as a repo owner.

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants