Marks currently are transferred between nested Python objects after collection, by mutating the objects themselves. For example, marks applied to classes are copied over all the test methods of the class, being added as attributes of the methods themselves.
This approach brings with it some surprising problems and is hard to get it right (#199, #842 and probably many others which have been fixed along the years).
@RonnyPfannschmidt has proposed to get rid of the current mark transfer mechanism in favor of a new one where marks are transfered from parent items to children, instead of mutating the Python objects.
Marks currently are transferred between nested Python objects after collection, by mutating the objects themselves. For example, marks applied to classes are copied over all the test methods of the class, being added as attributes of the methods themselves.
This approach brings with it some surprising problems and is hard to get it right (#199, #842 and probably many others which have been fixed along the years).
@RonnyPfannschmidt has proposed to get rid of the current mark transfer mechanism in favor of a new one where marks are transfered from parent items to children, instead of mutating the Python objects.