confluentinc / confluentinc/vscode
Clean up Mocha test contamination between Resources view and FlinkLanguageClientManager
- Dominant language
- TypeScript
- Stars
- 34
- Forks
- 17
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 8
Description
We started seeing a lot of logs relating to these two areas:
This may be caused by some event emitter being fired in tests and the (real) provider/manager not being stubbed, so their listeners handle the callbacks for a given event (or multiple) which leads to a lot of test log noise.
If left unchecked, this could cause test flakiness and/or timeouts.
Contributor guide
Research direction
Inspect the Mocha tests covering the Resources view and FlinkLanguageClientManager, then trace which event emitters invoke real providers or managers instead of stubs. Run the affected test suite and confirm that listener callbacks no longer produce cross-test log noise, flakiness, or timeouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100