Ptest - Revision history

Simonew: /* General recipe preparations */

2023-12-25T14:36:52Z

General recipe preparations

← Older revision		Revision as of 14:36, 25 December 2023
Line 63:		Line 63:
	If a test adds build-time or run-time dependencies to the package which are not there normally (such as requiring "make" to run the test suite), add those with a -ptest suffix, like this:		If a test adds build-time or run-time dependencies to the package which are not there normally (such as requiring "make" to run the test suite), add those with a -ptest suffix, like this:

	~~RDEPENDS_~~${PN}-ptest += "make"		RDEPENDS:${PN}-ptest += "make"

	==Building the test suite==		==Building the test suite==

RandyMacLeod: /* Adding ptest to your build */

2022-06-14T15:51:02Z

Adding ptest to your build

← Older revision		Revision as of 15:51, 14 June 2022
Line 8:		Line 8:

	DISTRO_FEATURES:append = " ptest"		DISTRO_FEATURES:append = " ptest"
	or		or
	DISTRO_FEATURES_append = " ptest"		DISTRO_FEATURES_append = " ptest"
	# Adding "ptest" to your DISTRO_FEATURES variable causes -ptest packages to be built.		# Adding "ptest" to your DISTRO_FEATURES variable causes -ptest packages to be built.

RandyMacLeod: /* Adding ptest to your build */

2022-06-14T15:50:37Z

Adding ptest to your build

← Older revision		Revision as of 15:50, 14 June 2022
Line 7:		Line 7:
	To add package testing to your build, set the <code>DISTRO_FEATURES</code> and <code>EXTRA_IMAGE_FEATURES</code> variables in your <code>conf/local.conf</code> file, which is found in the Build Directory:		To add package testing to your build, set the <code>DISTRO_FEATURES</code> and <code>EXTRA_IMAGE_FEATURES</code> variables in your <code>conf/local.conf</code> file, which is found in the Build Directory:

			DISTRO_FEATURES:append = " ptest"
			or
	DISTRO_FEATURES_append = " ptest"		DISTRO_FEATURES_append = " ptest"
	# Adding "ptest" to your DISTRO_FEATURES variable causes -ptest packages to be built.		# Adding "ptest" to your DISTRO_FEATURES variable causes -ptest packages to be built.

PaulEggleton at 00:12, 5 April 2018

2018-04-05T00:12:30Z

← Older revision		Revision as of 00:12, 5 April 2018
Line 90:		Line 90:
	The <code>ptest</code> class will automatically copy the required <code>run-ptest</code> file and run <code>make install-ptest</code> if there is such a target in the top-level <code>Makefile</code>. For packages where this is enough, you don't need to do anything else.		The <code>ptest</code> class will automatically copy the required <code>run-ptest</code> file and run <code>make install-ptest</code> if there is such a target in the top-level <code>Makefile</code>. For packages where this is enough, you don't need to do anything else.

	If you need to do something more than the automatic <code>make install-ptest</code>, create a <code>do_install_ptest</code> function within the recipe and put the required actions there. This function will be called after <code>make install-ptest<code> has completed.		If you need to do something more than the automatic <code>make install-ptest</code>, create a <code>do_install_ptest</code> function within the recipe and put the required actions there. This function will be called after <code>make install-ptest</code> has completed.

	==Recipes with ptest Enabled==		==Recipes with ptest Enabled==

PaulEggleton at 00:11, 5 April 2018

2018-04-05T00:11:50Z

← Older revision		Revision as of 00:11, 5 April 2018
Line 25:		Line 25:
	The "ptest-runner" package installs a "ptest-runner" which loops through all installed ptest test suites and runs them in sequence. You may therefore want to add "ptest-runner" to your image.		The "ptest-runner" package installs a "ptest-runner" which loops through all installed ptest test suites and runs them in sequence. You may therefore want to add "ptest-runner" to your image.

	==~~Ptest~~-runner Usage==		==ptest-runner Usage==

	The usage for the ptest-runner is as follows:		The usage for the ptest-runner is as follows:
Line 31:		Line 31:
	Usage: ptest-runner [-d directory] [-l list] [-t timeout] [-h] [ptest1 ptest2 ...]		Usage: ptest-runner [-d directory] [-l list] [-t timeout] [-h] [ptest1 ptest2 ...]

	==Executing ~~Ptest~~-runner==		==Executing ptest-runner==

	To execute a full ptest run you can do the following command line anywhere in the target:		To execute a full ptest run you can do the following command line anywhere in the target:

PaulEggleton: Explain how to add an individual ptest package

2018-04-05T00:11:13Z

Explain how to add an individual ptest package

← Older revision		Revision as of 00:11, 5 April 2018
Line 5:		Line 5:
	=Adding ptest to your build=		=Adding ptest to your build=

	To add package testing to your build, ~~add~~ the DISTRO_FEATURES and EXTRA_IMAGE_FEATURES variables to your local.conf file, which is found in the Build Directory:		To add package testing to your build, set the <code>DISTRO_FEATURES</code> and <code>EXTRA_IMAGE_FEATURES</code> variables in your <code>conf/local.conf</code> file, which is found in the Build Directory:

	DISTRO_FEATURES_append = " ptest"		DISTRO_FEATURES_append = " ptest"
Line 11:		Line 11:

	EXTRA_IMAGE_FEATURES += "ptest-pkgs"		EXTRA_IMAGE_FEATURES += "ptest-pkgs"
	# Adding "ptest-pkgs" to IMAGE_FEATURES variable causes -ptest packages ~~to be~~ installed in your image.		# Adding "ptest-pkgs" to IMAGE_FEATURES variable causes all -ptest packages corresponding with other packages installed in your image to be additionally installed.

	All ptest files are installed in /usr/lib/<package>/ptest.		As an alternative to the <code>ptest-pkgs</code> image feature, if you want to be more selective about which tests to include, you can install them individually e.g. to install the tests for e2fsprogs and zlib you would do something like this:

			CORE_IMAGE_EXTRA_INSTALL += "e2fsprogs-ptest zlib-ptest"

			This is of course just one way to add packages to an image, see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Customizing images] section of the Yocto Project development manual for more information.

			All ptest files are installed in <code>/usr/lib/<package>/ptest</code>.

	=Running ptest=		=Running ptest=

PaulEggleton: More formatting

2018-04-05T00:03:58Z

More formatting

← Older revision		Revision as of 00:03, 5 April 2018
Line 82:		Line 82:
	==Installing the test suite==		==Installing the test suite==

	The ptest~~.bbclass~~ will automatically copy the required "run-ptest" file and run "make install-ptest" if there is such a target in the top-level Makefile. For packages where this is enough, you don't need to do anything else.		The <code>ptest</code> class will automatically copy the required <code>run-ptest</code> file and run <code>make install-ptest</code> if there is such a target in the top-level <code>Makefile</code>. For packages where this is enough, you don't need to do anything else.

	If you need to do something more than the automatic "make install-ptest", create a do_install_ptest function and put the required actions there. This function will be called after "make install-ptest" has completed.		If you need to do something more than the automatic <code>make install-ptest</code>, create a <code>do_install_ptest</code> function within the recipe and put the required actions there. This function will be called after <code>make install-ptest<code> has completed.

	==Recipes with ptest Enabled==		==Recipes with ptest Enabled==

PaulEggleton: Update and improve formatting

2018-04-05T00:01:27Z

Update and improve formatting

Show changes

Rebecca Chang Swee Fun: Undo revision 36102 by Rebecca Chang Swee Fun (talk)

2018-02-22T08:40:48Z

Undo revision 36102 by Rebecca Chang Swee Fun (talk)

← Older revision		Revision as of 08:40, 22 February 2018
Line 4:		Line 4:

	=Adding ptest to your build=		=Adding ptest to your build=

	~~To add package testing to your build, add the PTEST_ENABLED variable to your local.conf file, which is found in the build directory:~~
	~~PTEST_ENABLED = "1"~~
	* Adding this variable causes -ptest packages and its dependencies to be built.

	To add package testing to your build, add the DISTRO_FEATURES and EXTRA_IMAGE_FEATURES variables to your local.conf file, which is found in the Build Directory:		To add package testing to your build, add the DISTRO_FEATURES and EXTRA_IMAGE_FEATURES variables to your local.conf file, which is found in the Build Directory:

Rebecca Chang Swee Fun: Add PTEST_ENABLED variable to enable ptest

2018-02-22T07:47:32Z

Add PTEST_ENABLED variable to enable ptest

← Older revision		Revision as of 07:47, 22 February 2018
Line 4:		Line 4:

	=Adding ptest to your build=		=Adding ptest to your build=

			To add package testing to your build, add the PTEST_ENABLED variable to your local.conf file, which is found in the build directory:
			PTEST_ENABLED = "1"
			* Adding this variable causes -ptest packages and its dependencies to be built.

	To add package testing to your build, add the DISTRO_FEATURES and EXTRA_IMAGE_FEATURES variables to your local.conf file, which is found in the Build Directory:		To add package testing to your build, add the DISTRO_FEATURES and EXTRA_IMAGE_FEATURES variables to your local.conf file, which is found in the Build Directory: