To increase ptest coverage we can check if the sources of a recipe looks like it contains unittest and warn the user that a test may be implemented there.
This series provide the check infrastructure as a package QA check and some checks for : python pytest, perl Test::, meson, cmake, autotools-based tests... as well as the naive check of "Is there a test/ directory in the sources?" which work surprisingly well. Currently, this check find: * 309 unimplemented ptest in oe-core/meta-poky/meta-yocto-bsp * 827 unimplemented ptest in meta-openembedded Full list : https://gist.githubusercontent.com/ycongal-smile/0969e92aec1ca37e61b6cdbcaf1f6885/raw/b1be8a5b576e144b6563f5481d31b32de9b22368/gistfile1.txt v1->v2: * Corrected: shortlog tag * Fixed infinite loop on source package containing symlink loops (e.g. md5deep) * Added test result Jérémy Rosen (4): insane: Add unimplemented-ptest infrastructure insane: Detect python and perl based tests insane: Detect build-system test harnesses insane: Add a naive heuristic to detect test subdirectories meta/classes-global/insane.bbclass | 50 ++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) -- 2.30.2
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#188680): https://lists.openembedded.org/g/openembedded-core/message/188680 Mute This Topic: https://lists.openembedded.org/mt/101754134/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
