-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
deprecate the builtin junitxml module and plan for moving it to a external plugin #3777
Copy link
Copy link
Closed
Labels
plugin: junitxmlrelated to the junitxml builtin pluginrelated to the junitxml builtin plugintype: backward compatibilitymight present some backward compatibility issues which should be carefully noted in the changelogmight present some backward compatibility issues which should be carefully noted in the changelogtype: deprecationfeature that will be removed in the futurefeature that will be removed in the futuretype: removalmarks the actual removal of a feature, usually done in major releasesmarks the actual removal of a feature, usually done in major releases
Description
Metadata
Metadata
Assignees
Labels
plugin: junitxmlrelated to the junitxml builtin pluginrelated to the junitxml builtin plugintype: backward compatibilitymight present some backward compatibility issues which should be carefully noted in the changelogmight present some backward compatibility issues which should be carefully noted in the changelogtype: deprecationfeature that will be removed in the futurefeature that will be removed in the futuretype: removalmarks the actual removal of a feature, usually done in major releasesmarks the actual removal of a feature, usually done in major releases
Type
Fields
Give feedbackNo fields configured for issues without a type.
followup to #1126
junitxml in pytest itself is broken and not seeing any real maintenance, as such it should be considered for removal from the core
as the plugin is not part of the public api, it can be turned into a required dependency even in a minor release without needing to have a breaking release
it can however only turned into a optional thing by a major release