Unify sys.settrace and sys.setprofile tests

[abalkin]

BPO	9398
Nosy	@terryjreedy, @ncoghlan, @abalkin

^{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 2010-07-28.15:04:00.980>
labels = ['type-feature', 'tests']
title = 'Unify sys.settrace and sys.setprofile tests'
updated_at = <Date 2016-09-10.18:36:18.310>
user = 'https://github.com/abalkin'

bugs.python.org fields:

activity = <Date 2016-09-10.18:36:18.310>
actor = 'belopolsky'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2010-07-28.15:04:00.980>
creator = 'belopolsky'
dependencies = []
files = []
hgrepos = []
issue_num = 9398
keywords = []
message_count = 1.0
messages = ['111823']
nosy_count = 3.0
nosy_names = ['terry.reedy', 'ncoghlan', 'belopolsky']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue9398'
versions = []

[abalkin]

Th sys.settrace and sys.setprofile functions have the same interface an very similar purpose. The difference is in the types of events that get reported. However the tests for these functions are implemented separately and cover different sets of scenarios. As proposed in python-dev thread, "Does trace modules have a unit test?" [1], this RFE proposes to

"""
Create tracetester helper file with abstract test cases made
from the union of test_sys_settrace and test_sys_setprofile test
cases and replace the concrete test cases in test_sys_set* with
subclasses that define setmethod, getmethod and expected_output.
"""
[1] http://mail.python.org/pipermail/python-dev/2010-July/102308.html

See also bpo-9315.

[kumaraditya303]

The issue is a decade old and has no comments apart from the initial post, the tests have changed since then hence closing, a new issue targeting main can be opened if desired.