Add tests for integration-level intellisense checks
- Dominant language
- Python
- Stars
- 497
- Forks
- 77
- Avg merge
- 22h 37m
- Merged PRs (30d)
- 45
Description
Integration-level IntelliSense checks are about verifying what symbols, methods, properties, and type information are actually visible to external tools (like IDEs, LSPs, or static analyzers) when someone uses a Python library. Since IntelliSense is not part of Python's runtime, the idea is to simulate the perspective of a developer using the Python library in an IDE or editor. These checks are most commonly done using tools like [jedi](https://jedi.readthedocs.io/en/latest/).
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reviewing the repository's existing integration-test layout and the linked Jedi documentation, then define checks for externally visible symbols, methods, properties, and type information. Done means these IntelliSense checks run against the Python library and verify the intended developer-facing API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100