Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • P poky
  • 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
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
    • Model experiments
  • 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
  • automation
  • so
  • mirror
  • poky
  • Repository
  • poky
  • bitbake
  • bin
  • bitbake-selftest
Find file Blame History Permalink
  • Paul Eggleton's avatar
    bitbake: bitbake-selftest: enable specifying tests to run on command line · 2f8be92d
    Paul Eggleton authored Feb 24, 2014
    
    
    If you are just trying to fix one test at a time, it can be useful to be
    able to specify an individual test(s) rather than running them all:
    
     bitbake-selftest bb.tests.codeparser bb.tests.cow
    
    You can even specify the test class or function to run, e.g.:
    
     bitbake-selftest bb.tests.fetch.URITest
     bitbake-selftest bb.tests.fetch.FetcherNetworkTest.test_fetch
    
    (Bitbake rev: 4df9c72663e972437131a848e6ddcf3769ae1d2b)
    
    Signed-off-by: default avatarPaul Eggleton <paul.eggleton@linux.intel.com>
    Signed-off-by: default avatarRichard Purdie <richard.purdie@linuxfoundation.org>
    2f8be92d