Use a Test Plan’s history to review recorded changes, see who made them, and understand which iteration they relate to. This helps you investigate changes to Test Cases, assignments, execution properties, and results.
You can review activity for the selected iteration or open the plan’s broader History view.
View history for an iteration
Open the Test Plan you want to review.
Select the relevant Iteration.
Open Details.
In Activity, select History.
Review the recorded changes. Use Newest first or Oldest first to change their order, and Refresh to reload the activity.
For a Test Run entry, use View test run when available to inspect the related execution.
Understand the scope of a change
Scope | What it means |
Iteration and a number | The entry relates to that round of testing. Check the iteration number before comparing it with another execution. |
All iterations | The entry describes a shared plan configuration change, such as changes to requirements or Test Case links. It is also relevant when viewing other iterations. |
A plan configuration change can appear in an iteration’s history even when no Test Run was created in that iteration. Some updates are summarized in one entry with counts of added or removed requirements and Test Case links.
Open the plan’s History view
Open the Test Plan.
Click the More Options menu (three dots) in the upper-right corner.
Select History, labeled Revision History beneath the menu item.
Review the timeline. Entries show the recorded change, its date and time, the person who made it, and the iteration or Test Case context where available.
What to look for
Recorded change | How it helps |
Test Cases linked or unlinked | Understand how the testing scope changed. Configuration entries can also identify the linked Test Case version. |
Requirements added or removed | Review changes to the work items or folders included in an Advanced Test Plan. |
Assignments and bulk updates | Check recorded changes to testers or Test Case details. Bulk entries may summarize the affected fields and number of items. |
Iteration properties | Review recorded Environment, Version, or Sprint changes for the relevant testing round. |
Test Run activity | Follow recorded execution changes, such as a run being created, its result changing, or a run being deleted. |
Example: A configuration entry shows that two Test Case links were added. A later entry for iteration 2 shows a failed execution. Review both to understand the plan’s scope at the time of that testing.
History, comments, and work logs
In the Activity section, use History for recorded changes, Comments for team discussion, and Work log for logged execution time. These views provide different details about the selected iteration.
If an expected entry is missing
Confirm that you opened the correct Test Plan and selected the intended iteration.
Click Refresh in Activity, or reopen the plan’s History view.
Check the plan-wide History view when you need context beyond the selected iteration.
If an error says the history could not be loaded, refresh and try again rather than treating it as an empty history.