decouple unittest assertions from the TestCase class

Open
#63,844 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by examining the unittest assertion methods and the TestCase class, using the issue's Tests component as the entry point. Determine the intended separation and identify the relevant tests; done means assertions no longer depend on TestCase while the existing unittest behavior remains covered.

Written by the indexing model from the issue text.

Description

3.9 (EOL) tests type-feature
BPO 19645
Nosy @ncoghlan, @rbtcollins, @merwok, @pakal, @bitdancer, @voidspace, @Julian, @vadmium, @serhiy-storchaka

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-11-18.14:38:14.516>
labels = ['type-feature', 'tests', '3.9']
title = 'decouple unittest assertions from the TestCase class'
updated_at = <Date 2019-07-10.01:01:52.598>
user = 'https://bugs.python.org/GregorySalvan'

bugs.python.org fields:

activity = <Date 2019-07-10.01:01:52.598>
actor = 'rbcollins'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2013-11-18.14:38:14.516>
creator = 'Gregory.Salvan'
dependencies = []
files = []
hgrepos = []
issue_num = 19645
keywords = []
message_count = 18.0
messages = ['203295', '203303', '203351', '227588', '230813', '254427', '345477', '345483', '345484', '345487', '345496', '345497', '345498', '345499', '345500', '347584', '347586', '347587']
nosy_count = 10.0
nosy_names = ['ncoghlan', 'rbcollins', 'eric.araujo', 'pakal', 'r.david.murray', 'michael.foord', 'Julian', 'martin.panter', 'serhiy.storchaka', 'Gregory.Salvan']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue19645'
versions = ['Python 3.9']

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.