add tests for #220 and #221
Open
- Dominant language
- Go
- Stars
- 2.3k
- Forks
- 136
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
#222 and #224 were merged to fix #220 and #221.
as noted in https://github.com/go-python/gopy/pull/222#issuecomment-604050120, it would be great to add tests for those, to make sure we don't regress at some point.
(tentatively "assigning" to @cosnicolaou )
Contributor guide
No contributing guide indexed for this repository
Research direction
Read issues #220 and #221, then inspect merged PRs #222 and #224 and the linked comment for the behaviors that need regression coverage. Locate the relevant existing Go tests, add cases covering both fixes, and run the repository test suite to confirm they pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100