Builds/Tests - Revision history

IHaveADrone: spelling

2016-06-14T13:29:11Z

spelling

← Older revision		Revision as of 07:29, 14 June 2016
Line 6:		Line 6:
	* <code>make test_math</code>: test math lib		* <code>make test_math</code>: test math lib
	* <code>make test_examples</code>: test compiles all aircrafts/targets in conf/conf_tests.xml		* <code>make test_examples</code>: test compiles all aircrafts/targets in conf/conf_tests.xml
	* <code>make test_all_confs</code>: test compiles all confs, i.e. all ~~aircrafs~~ found in all conf files found by <code>find_confs.py</code>		* <code>make test_all_confs</code>: test compiles all confs, i.e. all aircrafts found in all conf files found by <code>find_confs.py</code>

	To test compile all aircrafts in one specific conf file:<br />		To test compile all aircrafts in one specific conf file:<br />
Line 16:		Line 16:
	The test results can also be generated in JUnit format adding the option <code>JUNIT=1</code> to the command line i.e. <code>make test JUNIT=1</code> or <code>make test TEST_VERBOSE=1 JUNIT=1</code>		The test results can also be generated in JUnit format adding the option <code>JUNIT=1</code> to the command line i.e. <code>make test JUNIT=1</code> or <code>make test TEST_VERBOSE=1 JUNIT=1</code>

	JUnit formatting of test ~~resuls~~ requires that the Perl module <code>TAP::Formatters::JUnit</code> is installed on the machine that the tests are run on. Please see [[Builds/Tests#Installing Perl Modules\| installing Perl modules]] for more details		JUnit formatting of test results requires that the Perl module <code>TAP::Formatters::JUnit</code> is installed on the machine that the tests are run on. Please see [[Builds/Tests#Installing Perl Modules\| installing Perl modules]] for more details

	= Hardware tests =		= Hardware tests =

Flixr: /* Automated testing */

2015-10-03T13:00:02Z

Automated testing

← Older revision		Revision as of 07:00, 3 October 2015
Line 8:		Line 8:
	* <code>make test_all_confs</code>: test compiles all confs, i.e. all aircrafs found in all conf files found by <code>find_confs.py</code>		* <code>make test_all_confs</code>: test compiles all confs, i.e. all aircrafs found in all conf files found by <code>find_confs.py</code>

	To test compile all aircrafts in one specific conf file:		To test compile all aircrafts in one specific conf file:<br />
	<code>CONF_XML=conf/conf_personal.xml prove tests/aircrafts/</code>		<code>CONF_XML=conf/conf_personal.xml prove tests/aircrafts/</code><br />
			See [https://github.com/paparazzi/paparazzi/blob/master/tests/aircrafts/01_compile_all_aircrafts.t tests/aircrafts/01_compile_all_aircrafts.t] for more details.

	If you require more verbose output of the results run the command <code>make test TEST_VERBOSE=1</code>		If you require more verbose output of the results run the command <code>make test TEST_VERBOSE=1</code>

Flixr: /* Automated testing */

2015-09-25T12:02:21Z

Automated testing

← Older revision		Revision as of 06:02, 25 September 2015
Line 9:		Line 9:

	To test compile all aircrafts in one specific conf file:		To test compile all aircrafts in one specific conf file:
	<code>CONF_XML=conf/conf_personal.xml prove tests/~~examples~~/</code>		<code>CONF_XML=conf/conf_personal.xml prove tests/aircrafts/</code>

	If you require more verbose output of the results run the command <code>make test TEST_VERBOSE=1</code>		If you require more verbose output of the results run the command <code>make test TEST_VERBOSE=1</code>

Flixr: /* Automated testing */

2015-09-25T11:06:52Z

Automated testing

← Older revision		Revision as of 05:06, 25 September 2015
Line 1:		Line 1:
	= Automated testing =		= Automated testing =

	There are a number of automated tests that can be run from the command line.		There are a number of automated tests that can be run from the command line from the top level Paparazzi directory:

	~~To execute these tests execute the command~~ <code>make test</code> if you require more verbose output of the results run the command <code>make test TEST_VERBOSE=1</code>		* <code>make test</code>: runs test_math and test_examples
			* <code>make test_math</code>: test math lib
			* <code>make test_examples</code>: test compiles all aircrafts/targets in conf/conf_tests.xml
			* <code>make test_all_confs</code>: test compiles all confs, i.e. all aircrafs found in all conf files found by <code>find_confs.py</code>

			To test compile all aircrafts in one specific conf file:
			<code>CONF_XML=conf/conf_personal.xml prove tests/examples/</code>

			If you require more verbose output of the results run the command <code>make test TEST_VERBOSE=1</code>

	The test results can also be generated in JUnit format adding the option <code>JUNIT=1</code> to the command line i.e. <code>make test JUNIT=1</code> or <code>make test TEST_VERBOSE=1 JUNIT=1</code>		The test results can also be generated in JUnit format adding the option <code>JUNIT=1</code> to the command line i.e. <code>make test JUNIT=1</code> or <code>make test TEST_VERBOSE=1 JUNIT=1</code>

Flixr: /* Installing Perl modules */

2012-10-15T12:46:32Z

Installing Perl modules

← Older revision		Revision as of 06:46, 15 October 2012
Line 26:		Line 26:
	= Installing Perl modules =		= Installing Perl modules =
	On Ubuntu/Debian simply		On Ubuntu/Debian simply
	apt-get install libio-socket-multicast-perl		apt-get install libio-socket-multicast-perl libtap-formatter-junit-perl

	To install Perl modules directly from CPAN the following procedure can be run.		To install Perl modules directly from CPAN the following procedure can be run.

Flixr: /* Installing Perl modules */

2012-10-15T12:44:37Z

Installing Perl modules

← Older revision		Revision as of 06:44, 15 October 2012
Line 25:		Line 25:

	= Installing Perl modules =		= Installing Perl modules =
	To install Perl modules the following procedure can be run~~. There are alternatives depending on the operating system that is being used~~.		On Ubuntu/Debian simply
			apt-get install libio-socket-multicast-perl

			To install Perl modules directly from CPAN the following procedure can be run.

	# sudo perl -MCPAN -e shell		# sudo perl -MCPAN -e shell

Rbdavison: /* Hardware tests */

2012-07-16T12:04:48Z

Hardware tests

← Older revision		Revision as of 06:04, 16 July 2012
Line 22:		Line 22:
	The Perl module <code>IO::Socket::Multicast</code> is required to be installed to be able to execute the hardware tests. Please see [[Builds/Tests#Installing Perl Modules\| installing Perl modules]] for more details		The Perl module <code>IO::Socket::Multicast</code> is required to be installed to be able to execute the hardware tests. Please see [[Builds/Tests#Installing Perl Modules\| installing Perl modules]] for more details

	To execute the hardware tests run the command <code>make test TEST_HARDWARE=1</code>.		To execute the hardware tests run the command <code>make test TEST_HARDWARE=1</code>

	= Installing Perl modules =		= Installing Perl modules =

Rbdavison: /* Hardware tests */

2012-07-16T12:04:29Z

Hardware tests

← Older revision		Revision as of 06:04, 16 July 2012
Line 20:		Line 20:
	* Stop the '''server''' and '''link''' processes		* Stop the '''server''' and '''link''' processes

			The Perl module <code>IO::Socket::Multicast</code> is required to be installed to be able to execute the hardware tests. Please see [[Builds/Tests#Installing Perl Modules\| installing Perl modules]] for more details

	~~The Perl module~~ <code>~~IO::Socket::Multicast~~</code> ~~is required to be installed to be able to execute the hardware tests~~. ~~Please see [[Builds/Tests#Installing Perl Modules\| installing Perl modules]] for more details~~		To execute the hardware tests run the command <code>make test TEST_HARDWARE=1</code>.

	= Installing Perl modules =		= Installing Perl modules =

Flixr: added testing category

2012-03-06T14:35:54Z

added testing category

← Older revision		Revision as of 08:35, 6 March 2012
Line 30:		Line 30:

	This should install all of the required modules. note that errors may be reported during the installation process so you should pay attention to what is happening.		This should install all of the required modules. note that errors may be reported during the installation process so you should pay attention to what is happening.

			[[Category:Testing]]

Rbdavison: /* Hardware tests */

2012-03-06T12:33:43Z

Hardware tests

← Older revision		Revision as of 06:33, 6 March 2012
Line 11:		Line 11:
	= Hardware tests =		= Hardware tests =
	The hardware testing is executed using the Perl test framework.		The hardware testing is executed using the Perl test framework.

			To implement the hardware testing we need do the following
			* Build the firmware
			* Upload the firmware to the target board noting that multiple boards may be connected to the same computer
			* Start up the '''server''' program
			* Start up the '''link''' program
			* Run the test suite by reading and writing data to the Ivy bus.
			* Stop the '''server''' and '''link''' processes


	The Perl module <code>IO::Socket::Multicast</code> is required to be installed to be able to execute the hardware tests. Please see [[Builds/Tests#Installing Perl Modules\| installing Perl modules]] for more details		The Perl module <code>IO::Socket::Multicast</code> is required to be installed to be able to execute the hardware tests. Please see [[Builds/Tests#Installing Perl Modules\| installing Perl modules]] for more details