Page MenuHomePhabricator

Usages of unittest.expectedFailure or unittest.skip should be solved (goal)
Open, LowPublicGoal

Description

There are a lot of unittest.expectedFailure decorators. There should be a good reason to keep it. Otherwise the problem should be solved.

I found some inside

  • aspects.py
  • api-tests.py
  • cosmetic_changes_tests.py
  • file_tests
  • imagecopy_tests.py (archived)
  • interwiki_link_tests
  • isbn_tests.py (archived)
  • page_tests.py
  • pagegenerators_tests.py
  • pwb_tests.py
  • reflinks_tests.py
  • script_tests.py
  • site_detect_tests.py
  • site_generators_tests
  • site_tests.py
  • template_bot_tests.py
  • tests_tests.py <-- probably intentional as test
  • textlib_tests.py <-- some tests look wrong to me
  • time_tests.py
  • tools_ip_tests.py
  • tools_tests.py
  • upload_tests.py
  • utils.py
  • wikibase_tests.py

bold means bug tasks are created and marked as blocker

Find untagged issues:
https://codesearch.wmcloud.org/pywikibot/?q=%40.*expectedFailure%24&files=&excludeFiles=&repos=

Find all unsolves issues:
https://codesearch.wmcloud.org/pywikibot/?q=%40.*expectedFailure&files=&excludeFiles=&repos=

Find other issues added by tests config
https://codesearch.wmcloud.org/pywikibot/?q=%3D+.*expectedFailure&files=&excludeFiles=&repos=

Details

Related Objects

StatusSubtypeAssignedTask
OpenGoalNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenXqt
OpenBUG REPORTNone
OpenNone
StalledBUG REPORTNone
OpenNone
OpenNone
ResolvedXqt
ResolvedBUG REPORTXqt
ResolvedBUG REPORTXqt
ResolvedXqt
ResolvedXqt
ResolvedXqt
ResolvedXqt
ResolvedXqt
ResolvedXqt
ResolvedXqt
OpenNone
ResolvedXqt
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenBUG REPORTNone
ResolvedBUG REPORTXqt
DeclinedBUG REPORTNone
ResolvedLadsgroup
OpenNone
OpenFeatureNone
OpenBUG REPORTNone
OpenNone
OpenBUG REPORTNone
OpenBUG REPORTMahveotm
OpenBUG REPORTXqt
OpenBUG REPORTNone
ResolvedGoalXqt
ResolvedXqt
ResolvedBUG REPORTXqt
ResolvedBUG REPORTXqt
ResolvedBUG REPORTXqt
ResolvedXqt
ResolvedBUG REPORT Kgraessle
ResolvedXqt
OpenBUG REPORTNone
OpenBUG REPORTNone
ResolvedBUG REPORTXqt

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
Xqt renamed this task from Usages of unittest.expectedFailure should be solved (goal) to Usages of unittest.expectedFailure or unittest.skip should be solved (goal).Mar 8 2024, 12:30 PM
Xqt updated the task description. (Show Details)

Change #1156282 had a related patch set uploaded (by Xqt; author: Xqt):

[pywikibot/core@master] tests: add pbab tasks hints to expectedFailure decorators

https://gerrit.wikimedia.org/r/1156282

Change #1156282 merged by jenkins-bot:

[pywikibot/core@master] tests: add pbab tasks hints to expectedFailure decorators

https://gerrit.wikimedia.org/r/1156282

Xqt changed the subtype of this task from "Task" to "Goal".Jun 23 2026, 9:12 AM