You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[ ] Typing code into Python interactive window works
362
-
358
+
#### P0 Test Scenarios
359
+
-[ ] Start and connect to local Jupyter server
360
+
1. Open the file src/test/datascience/manualTestFiles/manualTestFile.py in VSCode
361
+
1. At the top of the file it will list the things that you need installed in your Python environment
362
+
1. On the first cell click `Run Cell And All Below`
363
+
1. Interactive Window should open, show connection information, and execute cells
364
+
1. The first thing in the window should have a line like this: `Jupyter Server URI: http://localhost:[port number]/?token=[token value]`
365
+
-[ ] Verify basic outputs
366
+
1. Run all the cells in manualTestFile.py
367
+
1. Check to make sure that no outputs have errors
368
+
1. Verify that graphs and progress bars are shown
369
+
-[ ] Verify export / import
370
+
1. With the results from `Start and connect to local server` open click the `Export as Jupyter Notebook` button in the Interactive Window
371
+
1. Choose a file location and save the generated .ipynb file
372
+
1. When the prompt comes up in the lower right choose to open the file in the browser
373
+
1. The file should open in the web browser and contain the output from the Interactive Window
374
+
1. In VSCode open up the exported .ipynb file in the editor, when the prompt for `Do you want to import the Jupyter Notebook into Python code?` appears click import
375
+
1. The imported file should match the original python file
376
+
-[ ] Verify text entry
377
+
1. In the Interactive Window type in some new code `print('testing')` and submit it to the Interactive Windows
378
+
1. Verify the output from what you added
379
+
-[ ] Verify dark and light main themes
380
+
1. Repeat the `Start and connect to local server` and `Verify basic outputs` steps using `Default Dark+` and `Default Light+` themes
381
+
382
+
#### P1 Test Scenarios
383
+
-[ ] Connect to a `remote` server
384
+
1. Open up a valid python command prompt that can run `jupyter notebook` (a default Anaconda prompt works well)
385
+
1. Run `jupyter notebook` to start up a local Jupyter server
386
+
1. In the command window that launched Jupyter look for the server / token name like so: http://localhost:8888/?token=bf9eae43641cd75015df9104f814b8763ef0e23ffc73720d
387
+
1. Run the command `Python: Select Jupyter server URI` then `Type in the URI to connect to a running jupyter server`
388
+
1. Input the server / token name here
389
+
1. Now run the cells in the manualTestFile.py
390
+
1. Verify that you see the server name in the initial connection message
391
+
1. Verify the outputs of the cells
392
+
-[ ] Interactive Window commands
393
+
-[ ] Verify per-cell commands
394
+
1. Expand and collapse the input area of a cell
395
+
1. Use the `X` button to remove a cell
396
+
1. Use the `Goto Code` button to jump to the part of the .py file that submitted the code
397
+
-[ ] Verify top menu commands
398
+
1. Use `X` to delete all cells
399
+
1. Undo the delete action with `Undo`
400
+
1. Redo the delete action with `Redo`
401
+
1. In manualTestFile.py modify the trange command in the progress bar from 100 to 2000. Run the Cell. As the cell is running hit the `Interrupt iPython Kernel` button
402
+
1. The progress bar should be interrupted and you should see a KeyboardInterrupt error message in the output
403
+
1. Test the `Restart iPython kernel` command. Kernel should be restarted and you should see a status output message for the kernel restart
404
+
1. Use the expand all input and collapse all input commands to collapse all cell inputs
405
+
-[ ] Verify code lenses
406
+
1. Check that `Run Cell``Run All Cells Above` and `Run Cell And All Below` all do the correct thing
407
+
-[ ] Verify context menu navigation commands
408
+
1. Check the `Run Current Cell` and `Run Current Cell And Advance` context menu commands
409
+
1. If run on the last cell of the file `Run Current Cell And Advance` should create a new empty cell and advance to it
410
+
-[ ] Verify command palette commands
411
+
1. Close the Interactive Window then pick `Python: Show Interactive Window`
412
+
1. Restart the kernel and pick `Python: Run Current File In Python Interactive Window` it should run the whole file again
413
+
-[ ] Verify shift-enter
414
+
1. Move to the top cell in the .py file
415
+
1. Shift-enter should run each cell and advance to the next
416
+
1. Shift-enter on the final cell should create a new cell and move to it
417
+
-[ ] Verify file without cells
418
+
1. Open the manualTestFileNoCells.py file
419
+
1. Select a chunk of code, shift-enter should send it to the terminal
420
+
1. Open VSCode settings, change `Send Selection To Interactive Window` to true
421
+
1. Select a chunk of code, shift-enter should send that selection to the Interactive Windows
422
+
1. Move your cursor to a line, but don't select anything. Shift-enter should send that line to the Interactive Window
423
+
-[ ] Multiple installs
424
+
1. Close and re-open VSCode to make sure that all jupyter servers are closed
425
+
1. Also make sure you are set to locally launch Jupyter and not to connect to an existing URI
426
+
1. In addition to your main testing environment install a new python or miniconda install (conda won't work as it has Jupyter by default)
427
+
1. In VS code change the python interpreter to the new install
428
+
1. Try `Run Cell`
429
+
1. You should get a message that Jupyter was not found and that it is defaulting back to launch on the python instance that has Jupyter
430
+
-[ ] LiveShare Support
431
+
1. Install the LiveShare VSCode Extension
432
+
1. Open manualTestFile.py in VSCode
433
+
1. Run the first cell in the file
434
+
1. Switch to the `Live Share` tab in VS Code and start a session
435
+
-[ ] Verify server start
436
+
1. Jupyter server instance should appear in the live share tab
437
+
1. Open another window of VSCode
438
+
1. Connect the second instance of VSCode as a Guest to the first Live Share session
439
+
1. After the workspace opens, open the manualTestFile.py on the Guest instance
440
+
1. On the Guest instance run a cell from the file, both via the codelens and via the command palette `Run Cell` command
441
+
-[ ] Verify results
442
+
1. Output should show up on the Guest Interactive Window
443
+
1. Same output should show up in the Host Interactive Window
444
+
1. On the Host instance run a cell from the file, both via the codelens and via the command palette
445
+
-[ ] Verify results
446
+
1. Output should show up on the Guest Interactive Window
447
+
1. Same output should show up in the Host Interactive Window
448
+
449
+
#### P2 Test Scenarios
450
+
-[ ] Directory change
451
+
-[ ] Verify directory change in export
452
+
1. Follow the previous steps for export, but export the ipynb to a directory outside of the current workspace
453
+
1. Open the file in the browser, you should get an initial cell added to change directory back to your workspace directory
454
+
-[ ] Verify directory change in import
455
+
1. Follow the previous steps for import, but import an ipynb that is located outside of your current workspace
456
+
1. Open the file in the editor. There should be python code at the start to change directory to the previous location of the .ipynb file
457
+
-[ ] Interactive Window input history history
458
+
1. Start up an Interactive Window session
459
+
1. Input several lines into the Interactive Window terminal
460
+
1. Press up to verify that those previously entered lines show in the Interactive Window terminal history
461
+
-[ ] Extra themes
462
+
1. Try several of the themes that come with VSCode that are not the default Dark+ and Light+
0 commit comments