posit-dev / posit-dev/positron
e2e tests need a way to know Positron is loaded and extensions installed.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 195
Description
As the startup of Positron gets more complex, it is causing issues in e2e testing. For example, see #6535
It would be good to have a way to know that Positron has been:
- UI Loaded fully
- Interpreter discovery done
- Any terminal restarts finished
- All bootstrap/bundled extensions installed
This would ensure Positron is in a good state before tests start running. We have put in several individual checks in the tests framework in the past for some of these.. but these are getting to be quite the burden to find and maintain. And now with the latest (#6535) we don't have a good way to check for it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the e2e test framework and the individual startup checks already used for UI loading, interpreter discovery, terminal restarts, and bundled extension installation. Read issue #6535 for the latest failure scenario. Done means tests have one maintained way to know Positron is fully ready before execution begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100