pytest-dev / pytest-dev/pytest
tests: revisit pdb/debugging tests
Open
Nobody has claimed this yet.
type: bug
type: enhancement
type: selftests
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
- a lot of tests expect only "Pdb", but that could also be in an internal error (f36f9d269)
- the pexpect.spawn's
senddoes not ensure the child is alive still, so you might get an internal error, send something and then compare "rest", missing the internal error - there should be a
expect_pdb_prompthelper probably - a generic method to configure the pexpect.spawn class is useful in general (Popen could be used on Windows)
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
Locate the pdb/debugging tests and their pexpect.spawn setup, then review the existing prompt and child-process assertions. The work is done when internal errors cannot be mistaken for successful Pdb output, prompt checks are centralized, and process configuration supports the stated platform needs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100