Test: Sublime Text Keymap Extension

[tsalinger]

Test for #45984

• macOS @RMacfarlane
• linux @jrieken
• windows @sbatten

Complexity: 3

Authors: @tsalinger, @sandy081

Note: Please file issues in this repository: https://github.com/Microsoft/vscode-sublime-keybindings

Prerequisite

• Download sublime-keybindings-4.0.0.zip
• Rename it from .zip to .vsix and Install.
• Make sure you have Sublime Text 3 installed

Known bugs in config API

There are currently two known bugs in the config API that affect this extension:

• Light to dark theme flickering Settings getting cleared when updating them using API #47763
  During the import process the settings might be reverted to an empty object for an instant. This leads to a flickering from a light theme to the default dark theme and back. Additionally, the 'screen-reader optimized' message box might be visible for an instant.
• Default VS Code setting not recognized as already set if it was the last setting being imported User Settings: Adding 'editor.matchBrackets: true' is not reflected in config.inspect's globalValue #47730

1. To reproduce select editor.matchBrackets as the only setting to import.
2. Use the Import Sublime Text Settings command again and notice that the editor.matchBrackets setting is still visible in the multi-picker

Test

1. A prompt is shown when the user starts VS Code with the extension for the very first time. Test that the prompt is not shown in any other case.
2. Import settings from Sublime Text using the command Import Sublime Text Settings
3. The importer tries to find your sublime settings folder on startup
   3.1 Verify that your settings folder is correctly detected.
   The default locations are:

OS X: ~/Library/Application Support/Sublime Text 3/Packages/User/Preferences.sublime-settings
Windows: %APPDATA%\Sublime Text 3\Packages\User\Preferences.sublime-settings
Linux: ~/.config/sublime-text-3/Packages/User/Preferences.sublime-settings

3.2 Move your sublime settings file to a different folder. You should be asked to browse to the settings file manually.
4. There exist mappings for the following Sublime Text settings. Pick some and put them into your Sublime Settings file. Verify that they are imported and mapped to valid VS Code settings.

"scroll_speed"
"hot_exit"
"open_files_in_new_window"
"close_windows_when_empty"
"show_full_path"
"preview_on_click"
"show_tab_close_buttons"
"save_on_focus_lost"
"find_selected_text"
"word_separators"
"ensure_newline_at_eof_on_save"
"auto_indent"
"tab_size"
"use_tab_stops"
"trim_automatic_white_space"
"detect_indentation"
"draw_white_space"
"trim_trailing_white_space_on_save"
"tab_completion"
"auto_complete_delay"
"auto_complete_commit_on_tab"
"copy_with_empty_selection"
"auto_find_in_selection"
"drag_text"
"default_encoding"
"font_face"
"font_size"
"line_numbers"
"fade_fold_buttons"
"scroll_past_end"
"word_wrap"
"indent_subsequent_lines"
"match_brackets"
"match_selection"
"draw_indent_guides"
"remember_full_screen"

5. Check the handling of settings that already exist in your VS Code user settings:
   5.1 Settings which have the same value as the existing one should not show up in the quickpick
   5.2 Settings with a different value should show up in the quickpick but are not selected by default