Configuration history
View every saved version of a load test’s configuration, restore an earlier version, and compare two versions side by side.
Every time you save changes to a load test’s configuration, BrowserStack records a new version. The History tab keeps a running record of those versions so you can see what changed, who changed it, and when. From the testb history, you can restore an earlier version or compare any two versions side by side.
With configuration history, you can:
- See every saved version of a load test, newest first.
- Track who modified the configuration and when.
- Restore an earlier version in one step.
- Compare two versions to see exactly which settings changed.
Open the History tab
Open the load test whose configuration you want to review, then select the History tab next to Details. The tab lists every saved version of that load test in a paginated table.
What the history table shows?
Each row is one saved version of the configuration. The table includes the following columns:
| Column | What it shows? |
|---|---|
| Version | The version number of the configuration. Numbers increase with each saved change. |
| Change type | How the version was created, such as a new test, an edit, or a restore. |
| Modified by | The user who saved this version. |
| Test type | The kind of load test, such as Playwright or JMeter. |
| Max VUs | The maximum number of virtual users set for this version. |
| Duration | How long the test was set to run. |
| Date | When the version was saved. |
| Actions | The restore option, available on every version except the current one. |
The newest version carries a Current badge and has no restore option, because it is already the active configuration. Each row also shows a change type badge that tells you how the version was created:
| Change type | Meaning |
|---|---|
| Created | The version was saved when the load test was first created. |
| Updated | The version was saved when you edited an existing load test. |
| Restored | The version was created by restoring an earlier version. |
| Legacy | The version was saved before configuration history was available, so its details are limited. |
Restore an earlier version
Restoring brings back the settings from an earlier version without overwriting your history. Instead of replacing the current version, a restore creates a new version with the older settings, so the full record stays intact.
To restore a version, find the version you want in the table and select Restore in its Actions column. BrowserStack saves the restored settings as the new current version, and the History tab and the load test details refresh to show the change.
The next time you run the load test, it uses the restored configuration.
Compare two versions of tests
Comparing test version helps you understand what changed between two points in time, such as before and after a spike in errors.
To compare versions:
- Select the checkbox on any two versions in the table.
- Select Compare.
The comparison opens a side by side view of both versions with every setting listed. Settings that differ between the two versions are highlighted, so you can spot changes such as a higher maximum VU count, a longer duration, or an edited threshold at a glance.
You can compare only two versions at a time. To compare a different version, clear one of the selected checkboxes, then select the version you want.
Points to remember
Keep the following in mind when you work with configuration history:
- Versions saved before configuration history was introduced show Unknown for the person who modified them and a Legacy change type badge.
- Checkboxes for comparison appear only when a load test has at least two saved versions.
- Restoring and comparing are available on your own projects. The actions are hidden on the sample project.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!