Test VS Live Server/Preview - Embedded Preview

[andreamah]

Refs #124608

• macOS @lszomoru
• linux @connor4312
• windows @DavidKutu

Complexity: 4

Create Issue

---

Prep

Please download the extension from the marketplace. The features should be explained in the Features section of the README.

Test

Please play around with the extension and file issues for UX suggestions and/or bugs!

!!! Please test primarily with the in-editor (internal) embedded preview, as there is a separate testplan item testing the external preview #127165 !!!

Focus on Testing

Features Exclusive to Embedded Preview

• Using the navigation buttons
  
  • Using the URL bar to navigate to different pages.
  • Using the back, forward, and open in external browser buttons.

Generic Live Server Features

• Running the Live Preview task (using --verbose and without it).
  • Using the links in the task's pseudo-terminal (clicking on the blue server URLs to open/reveal files) and the http://127.0.0.1/<PORTNUM> to open the index in preview. Note: clicking on directory links should reveal the folder in the file explorer if possible and file links should open the file.
    
• Using the different preview-refreshing settings to see if the preview refreshes when expected.
  
• Rendering special characters (ie: emojis) in the HTML.
• Using links to navigate between pages.
• Navigating the file system hosted by the server using the default index page (should show up when showing index if no index.html is available).
• Previewing files that are not a part of the current workspace OR previewing any files with no workspace open.
  • Using the custom task when previewing files that are not a part of the current workspace.
• Testing the multi-workspace scenario (allows user to choose workspace for server, defaults to first workspace)

Known limitations

Most of the known limitations have to do with the out-of-workspace previewing.

• If you have a preview of a non-workspace file and reload the window, the webview will either revive at the index of the current workspace (if one was open) or it will dispose of itself (if no workspace was opened). This is because the encoded endpoint names (and what they map to) do not persist between sessions.
• If you choose to preview a non-workspace file, links that are not a descendant of the file's parent (ie: ../../file.html) will not link correctly. This is because the custom endpoint created for the non-workspace file only hosts from the parent of the current file.