Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • N nxdtest
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • nxdtest
  • Repository
  • nxdtest
  • nxdtest
  • nxdtest_pytest_test.py
Find file BlameHistoryPermalink
  • Jérome Perrin's avatar
    PyTest.summaryf: better detection of summary line · f89c3b55
    Jérome Perrin authored Jun 20, 2022
    If program output after pytest's summary line, our summary function
    would be confused and detect 0 test run.
    Make this matching more robust by expecting the actual status of tests
    reported by pytest: (x)passed, (x)failed, skipped errors or "no test run"
    
    From Kirill's suggestion on !17 (comment 162070)
    
    /reviewed-by @kirr
    /reviewed-on !17
    f89c3b55
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7