How to setup jupyterlab-lsp for Browser-based Acceptance Tests
See original GitHub issueWhat I am trying to do…
I am trying to run browser acceptance tests. When I run python scripts/atest.py
it kinda works (after removing the testcase with flaky bash server which does not work), but I get a fail on tests (smoke is fine) due to “build recommended” dialogue. Screenshot:
How I would like to learn how to do it…
This might a common issue, worth adding to troubleshooting
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Contributing
Browser -based Acceptance Tests#. The browser tests will launch JupyterLab on a random port and exercise the Language Server features with Robot Framework...
Read more >LSP Integration for Python Not Working · Issue #203 - GitHub
Hi, I am newbie here. Wanting to learn Python with Jupyter Lab 1.26 and wanted to have the auto completion feature as in...
Read more >RPA and Web Scraping using Jupyter | by alpha2phi - Medium
Since I am going to perform web scraping, I need to install SeleniumLibrary from Robot Framework. $ pip install --upgrade robotframework-seleniumlibrary ...
Read more >Jupyter Documentation - Read the Docs
The Jupyter Notebook interface is a Web-based application for authoring ... fork (fast and more clever autocompletion for jupyterlab-lsp!)
Read more >Automated tests? - JupyterLab - Jupyter Community Forum
I was wondering if jupyterlab has an automated test suite Also are there any be… ... There are many tools for doing full...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Indeed. We’ve been trying to get the ability to skip that check into core but it hasn’t shown up on the 1.x line.
The other option is to not have
node
available onPATH
… which is not an option for us because of all the language servers.So that leaves having a “clean” build. This should work given some hot changes:
In CI, I go even further, and install only the built tarballs, but that seems a bit much.
will PR a doc change!