Find a way to detect incorrectly skipped tests

Open
#63,168 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
testing-qa

Research direction

No files, tests, or entry points are named in the issue. Start by reading the linked BPO issue and its discussion, then locate the CPython test-skipping mechanisms involved. Done means a concrete, agreed approach exists to detect incorrectly skipped tests, with corresponding coverage or validation identified.

Written by the indexing model from the issue text.

Description

tests type-feature
BPO 18968
Nosy @terryjreedy, @ncoghlan, @ezio-melotti, @xdegaye

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 2013-09-08.03:05:34.920>
labels = ['type-feature', 'tests']
title = 'Find a way to detect incorrectly skipped tests'
updated_at = <Date 2015-07-21.08:11:36.857>
user = 'https://github.com/ncoghlan'

bugs.python.org fields:

activity = <Date 2015-07-21.08:11:36.857>
actor = 'ethan.furman'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2013-09-08.03:05:34.920>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 18968
keywords = []
message_count = 4.0
messages = ['197218', '197228', '197646', '197647']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'ncoghlan', 'ezio.melotti', 'xdegaye']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue18968'
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.