documentation/test-manual/intro.rst

122       $ bitbake image -c testsdkext
132       $ bitbake image -c testimage
152       $ bitbake image -c testsdk
158    through :ref:`bitbake-selftest <ref-manual/release-process:Testing and Quality Assurance>` and
171 -  *bitbake-selftest:*
173    These tests are self-contained and test BitBake as well as its APIs,
175    ``bitbake/lib/*/tests``.
177    From within the BitBake repository, run the following::
179       $ bitbake-selftest
182    variable when running "bitbake-selftest" as follows::
184       $ BB_SKIP_NETTESTS=yes bitbake-selftest
189       $ bitbake-selftest -v
194    "bitbake-selftest" command. For example, to specify the tests for the
197       $ bitbake-selftest bb.test.data.module
202       $ bitbake-selftest bb.tests.data.TestOverrides.test_one_override
256          $ bitbake image -c testimage
267          $ bitbake image -c testsdk
278          $ bitbake image -c testsdkext
318 For oe-selftest. bitbake testcases reside in the ``lib/bb/tests/``
321 ``bitbake-selftest``
343 Bitbake selftests are straightforward python unittest. Refer to the
358             result = runCmd('bitbake-layers show-cross-depends')
359 …self.assertTrue('aspell' in result.output, msg = "No dependencies were shown. bitbake-layers show-…
363 from ``unittest.TestCase``, which runs the ``bitbake-layers`` command
370 -  *Obtaining the value of a bitbake variable:* Use
374 -  *Running a bitbake invocation for a build:* Use
375    ``oeqa.utils.commands.bitbake()``
387 launch the ``bitbake`` command and exist outside of its context. As a
388 result, common bitbake library functions (bb.\*) are also unavailable.
482             """Bitbake parsing (bitbake -p)"""
486             self.measure_cmd_resources(['bitbake', '-p'], 'parse_1',
487                      'bitbake -p (no caches)')
490             self.measure_cmd_resources(['bitbake', '-p'], 'parse_2',
491                      'bitbake -p (no tmp/cache)')
493             self.measure_cmd_resources(['bitbake', '-p'], 'parse_3',
494                      'bitbake -p (cached)')
497 measured, with and without various caches, to show how BitBake's parsing
518 option with the ``bitbake`` command to "taint" tasks by changing the
525 confuses BitBake while running in parallel. If this is necessary, copy