Report correct coverage.py data for tests that invoke subprocesses

Open
#56,187 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Start by reviewing PR #1865 and the issue history for the existing approach to coverage.py data from tests that invoke subprocesses. Locate the affected CPython test entry points from that discussion, then verify that subprocess-invoking tests report correct coverage data without regressing ordinary test coverage.

Written by the indexing model from the issue text.

Description

tests type-feature
BPO 11978
Nosy @ncoghlan, @nedbat, @ultimatecoder
PRs
  • python/cpython#1865
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
closed_at = None
created_at = <Date 2011-05-02.13:46:09.479>
labels = ['type-feature']
title = 'Report correct coverage.py data for tests that invoke subprocesses'
updated_at = <Date 2020-01-24.23:32:56.556>
user = 'https://github.com/ncoghlan'

    bugs.python.org fields:

    activity = <Date 2020-01-24.23:32:56.556>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2011-05-02.13:46:09.479>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 11978
keywords = []
message_count = 9.0
messages = ['134967', '134968', '291218', '291219', '291221', '291242', '294672', '296735', '298399']
nosy_count = 3.0
nosy_names = ['ncoghlan', 'nedbat', 'jaysinh.shukla']
pr_nums = ['1865']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue11978'
versions = []

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.