Страница:
Notebook Smoke Test
Страницы
Accessibility Guidelines
Adopting Multi Root Workspace APIs
Automated Issue Triaging
Build Champion
Build and run 32bit Code OSS on Windows
Code Editor Roadmap
Coding Guidelines
Color customization color id changes
Commit Signing
Community Issue Tracking
Contributor License Agreement
Cross Compiling for Debian Based Linux
Dealing with Test Flakiness
December Pre Release
December Test Plan
Design Goals
Development Process
Differences between the repository and Visual Studio Code
Editor decorations & colors
Explain extension causes high cpu load
Extension API guidelines
Extension API process
Feature Areas
Feedback Channels
File Watcher Internals
File Watcher Issues
Git & SCM Issues
Home
How to Contribute
IME Test
Insiders Release Notes
Interactive Window Documentation
Inventory of performance marks
Issue Grooming
Issue Tracking
Issues Triaging
Iteration Plans
Keybinding Issues
Known issues
Lists And Trees
Native Crash Issues
Notebook Smoke Test
Notebook documentation
Notebook layout
November Plan
Performance Issues (old)
Performance Issues
Pointer Device & Touch support
Publish vscode types
Related Projects
Release Process
Releasing vscode.dev
Removing Insiders
Roadmap 2017
Roadmap 2018
Roadmap 2019
Roadmap 2020
Roadmap
Roadmap‐2021‐2022
Running the Endgame
Sanity Check
Search Issues
Selfhosting on Windows WSL
Semantic Highlighting Overview
Setting Descriptions
Smoke Test
Source Code Organization
Submitting Bugs and Suggestions
Terminal Issues
TypeScript Issues
UX
VS Code Speech
Virtual Workspaces
Working Copies
Working with xterm.js
Writing Test Plan Items
Writing Tests
[DEV] Perf Tools for VS Code Development
[DEV] Programming advice and tips & tricks
[WIP] Code Editor Design Doc
[WIP] Design Checklist
[WIP] Design Principles
[dev perf] PerformanceError and unresponsive renderer telemetry
7
Notebook Smoke Test
Peng Lyu редактировал(а) эту страницу 2020-03-19 10:50:13 -07:00
Manual Smoke Test
Prereqs
- Clone the notebook extensions repository
git clone https://github.com/microsoft/notebook-extension-samples
yarn && yarn run install && yarn run build
- Run Insiders with specifying
notebook-extension-samples
as the extension directory (or you can symlink the folders)code-insiders --extensions-dir notebook-extension-samples
- Clone the notebook test repository
git clone https://github.com/microsoft/vscode-notebook-testdata
- Open the folder in OSS
File opening & rendering
One major goal of native notebook experience in VS Code is performance: file opening, scrolling and editing should be as performant as a normal text editor. Please test the code change doesn't regress the performance
- Open
samples/runCode.ipynb
, make sure markdown cell and code cells are rendered properly.- Scrolling in the editor is smooth, no significant noticeable lag.
- Open
samples/runCode50.ipynb
. This file contains 600 code cells and 1300 markdown cells, but opening this file should be fast too.- Test scrolling with scrollbar, try to scroll to the middle or the bottom of the document.
- Please check all outputs are rendered properly
Output rendering
Outputs are rendered under code cells. When an output is secure and simple, like text, png, we will render them in the core. If it's insecure, like html/javascript, we will render them in a webview.
- Open
samples/mimetypes.ipynb
- Make sure all outputs are rendered as expected
- Open
samples/runCode_iframe_form_15.ipynb
, test iframes and forms are rendered properly and they are interactive- Scroll the document to the bottom, scroll back and check if the iframe is still running
Editing
Open runCode.ipynb
- Hover on a cell, and click the gear icon on the left, test commands in the context menu works as expected
- Inserting a cell should focus the newly added cell (focus should be inside the nested monaco editor)
- After modifying the cells, the file should be a dirty state
- Cmd+S to save the document, the document should be persisted on disk and please check if the changes are correct.
Execution
- Open
test/ipywidgets.test.ipynb
, focus in the editor, clickExecute Notebook
actions on the editor toolbar- Check if the outputs are rendered properly
Project Management
- Roadmap
- Iteration Plans
- Development Process
- Issue Tracking
- Build Champion
- Release Process
- Running the Endgame
- Related Projects
Contributing
- How to Contribute
- Submitting Bugs and Suggestions
- Feedback Channels
- Source Code Organization
- Coding Guidelines
- Testing
- Dealing with Test Flakiness
- Contributor License Agreement
- Extension API Guidelines
- Accessibility Guidelines
Documentation