Test compound logs and filtering in Output view

[sandy081]

Refs: #237974 #237829 #237432

• Mac @Tyriar
• Win @bpasero
• Linux @TylerLeonhardt

Complexity: 5

Create Issue

---

Filtering

You can now filter the content in the Output view.

• Open any output view say Git
• Test filtering the content in the output view and make sure it is working as expected
  • Filter by Log Level
  • Filter by Category - Category of the log line is defined after the log level in square brackets.
  • Filter by Text

Compound Output View

You can now view multiple logs in a single compound output view. VS Code already has OOB some compound output views: Window, Shared & Telemetry. You can also create one by selecting existing.

• Open Window log in Output View and set log level to Trace from gear icon next to the dropdown
• Go to extensions view and run some searches to Marketplace
• Validate that the network logs appear in the Window output
• Validate that the filter dropdown shows Network category. Note that other categories available in the dropdown are logs composed into this view.
• Test filtering (follows steps from above) in the Window output view is working as expected
• Test creating a custom compound log using the action Add Compound Log... available in the overflow menu of the Output view.
• Test that the created compound log view is showing the data from all the logs you selected
• Test that the filtering this compound log view is working as expected
• Test that you can open the compound log in an editor or in an aux window using the actions available in the overflow menu

Export & Import

You can now export and import the logs using the actions available in the overflow menu of the Output view

• Test Save Output As... and Export Logs... actions in the overflow menu are working as expected
• Import these exported logs using Import Log... action and test the log is imported correctly.
  • Test that the filtering the imported log is working as expected

[bpasero]

Pretty solid 👏

[Tyriar]

Great addition! I also discovered that filtering turns out to be a fantastic way to reproduce bugs in editor GPU renderer 😃