Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TestPlan: DataFrame viewer on the web #10915

Closed
1 task done
sadasant opened this issue Jul 25, 2022 · 0 comments
Closed
1 task done

TestPlan: DataFrame viewer on the web #10915

sadasant opened this issue Jul 25, 2022 · 0 comments

Comments

@sadasant
Copy link
Contributor

sadasant commented Jul 25, 2022

Testing the DataFrame viewer on the web.

Refs: #9665

Complexity: 3

Authors: @sadasant

Create Issue


Requirements

Set up

  1. Go to a command prompt where you've installed jupyter into a python environment
  2. Switch to a folder you're using for testing
  3. Run jupyter with the following command jupyter notebook --no-browser --NotebookApp.allow_origin=*

Test steps

  1. Open insiders.vscode.dev and create a new .ipynb file.
  2. Connet to the jupyter server:
    1. Run the 'Jupyter: Specify jupyter server for connections' command.
    2. Pick 'Existing'.
    3. Paste the URL from the jupyter notebook server you started in step 3 of the setup.
  3. In one of the Notebook cells, enter one or more array variables of any length.
  4. Run the cell in any way. For example: by clicking the ▶️ button at the left of the cell.
  5. It might ask which kernel to use. Pick the remote kernel.
  6. Run the command Jupyter: Focus on Variables View.
  7. See that the variables in the Variable View matched the expectations.
  8. In the Variables View, hover over any of the array variables. An icon will appear at the left-most column of the table. Click on that icon.
  9. An expanded view of that variable should replace the notebook in the editor view.
  10. Try that again with any other variable.
dataviewer.mov
@github-actions github-actions bot added the triage-needed Issue needs to be triaged label Jul 25, 2022
@ghost ghost assigned rebornix Jul 26, 2022
@rebornix rebornix removed the triage-needed Issue needs to be triaged label Jul 26, 2022
@rebornix rebornix added this to the July 2022 milestone Jul 26, 2022
@rebornix rebornix removed their assignment Jul 27, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants