{"id":3935,"date":"2012-08-31T20:54:29","date_gmt":"2012-08-31T18:54:29","guid":{"rendered":"http:\/\/daniel.haxx.se\/blog\/?p=3935"},"modified":"2012-08-31T20:54:29","modified_gmt":"2012-08-31T18:54:29","slug":"ptest-because-make-test-is-insufficient","status":"publish","type":"post","link":"https:\/\/daniel.haxx.se\/blog\/2012\/08\/31\/ptest-because-make-test-is-insufficient\/","title":{"rendered":"ptest because “make test” is insufficient"},"content":{"rendered":"

\"CAUTION:Much thanks to autoconf and automake we have an established more or less standardized way to build and install tools, libraries and other software. We build them with ‘make’ and we install them with ‘make install<\/a>‘. This works great and it works equally fine even when we build stuff cross-compiled.<\/p>\n

For testing however, the established concept and procedure is not as good. For testing we have ‘make test’ or ‘make check’ which typically first builds whatever needs to get built for the tests to run and then it runs all tests.<\/p>\n

This is not good enough<\/strong><\/h2>\n

Why? Because in lots of use-cases we build software using a cross-compiler on a build system that can’t run the executables. Therefore we need to first build the tests, then install the tests (somewhere that is reachable from the target system)\u00c2\u00a0and finally execute them. These steps need to be possible to run independently since at least the building and installing will sometimes happen on a different host than the execution of the tests.<\/p>\n

\"yocto-project\"Introducing ptest<\/strong><\/h2>\n

Within the yocto<\/a> project, Bj\u00c3\u00b6rn Stenberg<\/a> has pushed for ptest<\/a> to be the basis of this new reform and concept. The responses he’s gotten so far has been positive and there’s a pending updated patch to be posted to the upstream oe-core list<\/a> soon.<\/p>\n

The work does not end there<\/h2>\n

Even if or when this can be incorporated into OpenEmbedded<\/a> and Yocto – and I really think it is a matter of when since I believe we can work out all the flaws and quirks until virtually everyone involved is happy. The bulk of the changes however, really should be done upstream, in hundreds and thousands of open source packages. We (as upstream open source projects) need to start doing testing in at least two different steps, where one step build everything that needs to be built for the tests and then a second step that run the suite. The two steps could then in a cross-compiled scenario get executed first on the host system and then on the target system.<\/p>\n

I expect that this will mean a whole bunch of patches and scripts to have to be maintained within OpenEmbedded for a while, when things will be tried to get merged into upstream projects and I also foresee that a certain percentage of all projects just won’t accept this new approach and will reject all patches in this vein.<\/p>\n

Output format<\/h2>\n

I think the most controversial part of these suggested “universal” changes is the common test suite output format. The common format is of course required so that we can “supervise” the output and results from any package without having to know any specifics.<\/p>\n

While the ptest output format follows the automake test output syntax<\/a>, I expect many projects that have selected a particular output format to rather stick with that. Hopefully we can then make projects introduce a separate make target or option that runs the test suite with the standard output format.<\/p>\n

One little step forward<\/h2>\n

Building full-fledged Linux distributions cross-compiled that are completely tested on target will remain being hard work for a while more. But we are improving things, one step at a time.<\/p>\n

Of course, the name ‘ptest’ is what the system is currently called by Bj\u00c3\u00b6rn within the yocto\/OE environment. It is not supposed to be a catchy name for this idea outside of there. The ‘P’ refers to package, as opposed to for example system test and to make it less generic than simply test.<\/p>\n","protected":false},"excerpt":{"rendered":"

Much thanks to autoconf and automake we have an established more or less standardized way to build and install tools, libraries and other software. We build them with ‘make’ and we install them with ‘make install‘. This works great and it works equally fine even when we build stuff cross-compiled. For testing however, the established … Continue reading ptest because “make test” is insufficient<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,6],"tags":[350,351,267,322,355,349,354],"class_list":["post-3935","post","type-post","status-publish","format-standard","hentry","category-development","category-floss","tag-autoconf","tag-automake","tag-autotools","tag-bjorn","tag-openembedded","tag-testing","tag-yocto"],"_links":{"self":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts\/3935","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/comments?post=3935"}],"version-history":[{"count":29,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts\/3935\/revisions"}],"predecessor-version":[{"id":4141,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts\/3935\/revisions\/4141"}],"wp:attachment":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/media?parent=3935"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/categories?post=3935"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/tags?post=3935"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}