Record and Playback - Refactoring and Improvements #4229
Labels
Client
This issue points to a problem in the data-plane of the library.
Epic
test-utils-recorder
Label for the issues related to the common recorder
Milestone
TO DO
Tier 1
RecorderEnvironmentSetup
with the record call [Recorder] CouplingRecorderEnvironmentSetup
with the record call #7135RecorderEnvironmentSetup
with the record call #7085Tier 2
this.skip()
[Storage] Regenerating all the recordings at once fail because of the tests withthis.skip()
#5697.beforeEach
recording even when the test is skipped #6284.Record and Playback
- Improvements to browser console.logs #4205.Tier 3
Previously done tasks
Tasks that will make our lives easier [Total estimate: 12]
A copy of a single recorded test with a new name, with an accordingly name recorded file, should work as is on play. [Recorder] A copy of a single recorded test with a new name, with an accordingly name recorded file, should work as is on play. #6414Can't reproduce. Closed the issue.[Recorder] Ensure that no recordings have time-sensitive information stored #6415
[Estimate: 1] [Priority: normal] Follow script guidelines [Recorder] Follow script guidelines #6555Not needed.After talking with Jonathan and Jeff, seems most appropriate to fix the issues above before refactoring the current recorder. By the time we finish, we will know if Mike Harder has an update on whether we can move to a centralized recorder.
Other tasks with estimates and considerations
uniqueString()
in favour ofrecorder.getUniqueName()
- [KeyVault] Make sure our repos follow the new recorder guidelines #4872@azure/test-utils-recorder
in keyvault-secrets package HarshaNalluru/azure-sdk-for-js#15The text was updated successfully, but these errors were encountered: