The test plan for the December iteration plan #917.
Debug - long text wraps in repl
Verify that long text now nicely wraps across multiple lines in the debug repl both for evaluation requests and for output text.
Debug - breakpoint state
We have changed breakpoints states and now show it differently in the UI. Verify:
- new UI properly and intuitivly reflects if breakpoints are enabled, disabled, verified or deactivated.
- breakpoints get hit / not hit depending on their enablement state
Debug - extension debugging
Extension debugging is now using a new strategy to attach the debugger to the extension
- verify you can debug your extension as before
- verify you can restart debugging from the debugger side and the debugger reconnects properly
- verify you can change folders or refresh on the extension development side and the debugger reconnects
- verify closing the extension development side stops debugging
- verify stopping the session from the debugger closes the extension development window
Update - channel from settings
Verify you can change the update channel from settings.
View - persisted zoom settings
Verify you can change and persist the zoom factor for windows.
- negative and positive values work
- the zoom actions are still working as before but do not persist
- the change is live
Quick open - Path and Fuzzy matching
Unless you include a path character in your query or enabled fuzzy matching, quick open for files should work as before:
- results are sorted properly with most relevant ones to the top
- editor history always comes first on top of matching file results
- if you narrow down a search, subsequent matching is fast and does not go to the disk (verify with a larger workspace)
Verify the new support to match on paths if included in search
- using the native path separator in the search enables matching on (workspace relative) paths for both editor history results and file matching
- more relevant results are still sorted to the top
- results are highlighted properly also in their path segment
Verify the new support for fuzzy file matching
- find and enable the new setting to enable fuzzy matching for quick open. this will only enable fuzzy matching for file search, it should not have any impact to other quick open providers, nor the editor history search
- verify results from file searches match on the entire (workspace relative) path of the file without having to use the native path separator
- verify matching happens in substrings of the path, not requiring the characters to be in sequence (e.g. "fr" would match "foo_bar")
- more relevant results are sorted to the top
Extensions info in status bar #1123
Verify that the extensions status shows up in the status bar if you have extension errors. Verify clicking on the status bar shows all the error / warning messages to the user and that you can uninstall the extension via action in message.
The test plan for the December iteration plan #917.
Debug - long text wraps in repl
Verify that long text now nicely wraps across multiple lines in the debug repl both for evaluation requests and for output text.
Debug - breakpoint state
We have changed breakpoints states and now show it differently in the UI. Verify:
Debug - extension debugging
Extension debugging is now using a new strategy to attach the debugger to the extension
Update - channel from settings
Verify you can change the update channel from settings.
View - persisted zoom settings
Verify you can change and persist the zoom factor for windows.
Quick open - Path and Fuzzy matching
Unless you include a path character in your query or enabled fuzzy matching, quick open for files should work as before:
Verify the new support to match on paths if included in search
Verify the new support for fuzzy file matching
Extensions info in status bar #1123
Verify that the extensions status shows up in the status bar if you have extension errors. Verify clicking on the status bar shows all the error / warning messages to the user and that you can uninstall the extension via action in message.