diff options
author | Alexander Kanavin <alex@linutronix.de> | 2025-09-29 14:56:08 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-10-04 11:16:43 +0100 |
commit | ec7c31497d261f0b8973e8d8aee876775b89b153 (patch) | |
tree | 4f7cd076620c9a2b0aace5a91e4bb7e8917f39f1 /meta/lib/patchtest/patchtest_parser.py | |
parent | 5e0593f116b351d7981175dc63af1ff0e123a2d6 (diff) | |
download | poky-ec7c31497d261f0b8973e8d8aee876775b89b153.tar.gz |
bitbake: bitbake-setup: add tests to bitbake-selftest
Run like this:
alex@Zen2:/srv/work/alex/bitbake$ bin/bitbake-selftest -v bb.tests.setup
test_setup (bb.tests.setup.BitbakeSetupTest.test_setup) ... ok
----------------------------------------------------------------------
Ran 1 test in 9.223s
OK
The test does a basic run-through of init, then status/update
on an unchanged configuration, then status/update on a
configuration changed via new commits to the test layer,
then status/update on configuration changed via the top
level json config file.
Note that nothing whatsoever is fetched from the network;
the test relies entirely on synthetic data contained inside
itself, including minimal stubs for oe-setup-build and
bitbake-config-build. This data is used to create temporary
git repositories then clone them via local filesystem URIs.
Later on this can be supplemented by an oe-selftest that
tests bitbake-setup against real config files in the
official configuration repository and real layers,
templates and fragments.
(Bitbake rev: 59ec7e2ac56e364bae39ccb5e884c447a5379531)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib/patchtest/patchtest_parser.py')
0 files changed, 0 insertions, 0 deletions