From 6ab7ee3439ab87df3e0bc9dc8afbdfd132f313be Mon Sep 17 00:00:00 2001 From: Harsha Nalluru Date: Fri, 21 Apr 2023 11:35:18 -0700 Subject: [PATCH] Inspecting recordings in VS Code --- sdk/test-utils/recorder/ASSET_SYNC_MIGRATION.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/sdk/test-utils/recorder/ASSET_SYNC_MIGRATION.md b/sdk/test-utils/recorder/ASSET_SYNC_MIGRATION.md index 881e05ae4bf5..16e8f08b3ef2 100644 --- a/sdk/test-utils/recorder/ASSET_SYNC_MIGRATION.md +++ b/sdk/test-utils/recorder/ASSET_SYNC_MIGRATION.md @@ -136,6 +136,21 @@ There is an [open issue](https://github.com/Azure/azure-sdk-tools/issues/4652) t For more information on this topic, see the [asset sync reference documentation][asset-sync-reference]. +### Through VS Code [GIT Source Control](https://code.visualstudio.com/docs/sourcecontrol/overview) UI + +Suppose you want to update the recording for a test, you'll re-run the test like below. + +image + +The changes in the recordings can be seen in the GIT Source Control section in VS Code. + +(Installing GIT should be enough to get this view. [VS Code Source control overview](https://code.visualstudio.com/docs/sourcecontrol/overview)) + +Click the file on the left side to view the diff for it on the right side as shown below. + +image + + ## Other `test-proxy` commands A few commands have been added to `dev-tool` to facilitate pushing and fetching the recordings to and from your local: