Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • N nxdtest
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • 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

Switch branch/tag
  • nxdtest
  • nxdtest
Find file BlameHistoryPermalink
  • Kirill Smelkov's avatar
    Clarify meaning of error vs failure · 1561b3a0
    Kirill Smelkov authored Oct 01, 2020
    failure is assertion failure.
    error is any other error.
    
    Source: https://docs.python.org/3/library/unittest.html#organizing-test-code
    -> "If the test fails, an exception will be raised ... identify the test
    case as a failure. Any other exceptions will be treated as errors"
    
    While searching ERP5 code for failure_count to clarify its meaning, I've
    also discovered expected_failures and unexpected_successes (*) so they
    are also added to the table.
    
    (*) see e.g. https://lab.nexedi.com/nexedi/erp5/blob/1e31c091/product/ERP5Type/tests/ERP5TypeTestSuite.py#L6-8
    1561b3a0

Replace nxdtest

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7