Armadeus Integration Test - Revision history

Jorasse at 18:51, 1 October 2013

2013-10-01T18:51:30Z

Jorasse: /* Armadeus Test Integration */

2013-10-01T18:46:18Z

‎Armadeus Test Integration

Jorasse at 22:26, 30 September 2013

2013-09-30T22:26:02Z

Jorasse: /* Compilation Test Plan */

2013-09-30T22:24:05Z

‎Compilation Test Plan

Jorasse: /* Compilation Tests */

2013-09-30T21:26:24Z

‎Compilation Tests

Jorasse: /* Changelog */

2013-09-30T21:18:26Z

‎Changelog

Jorasse: developping...

2008-11-19T08:27:33Z

developping...

Jorasse: /* Compilation Tests */

2008-11-19T08:26:02Z

‎Compilation Tests

WikiSysop: /* Compilation Tests */

2008-11-18T20:45:08Z

‎Compilation Tests

JulienB: /* Compilation Tests */

2008-11-18T20:38:32Z

‎Compilation Tests

@@ Line 34: / Line 34: @@
 #publish results on internet (pass or fail)
 ===On target tests===
@@ Line 63: / Line 42: @@
 * Armadeus packages need their own stategy (TBD)
+====Principle:====
-==On target Test Plan==
-−
 ===Principle:===
 * reset the board
 * take control of the target within uboot
@@ Line 79: / Line 55: @@
 * publish results on internet
-===Busybox testsuite - howto===
+====Busybox testsuite - howto====
 Busibox provides its own testsuite. The following description prepare and run busybox tests:
@@ Line 100: / Line 76: @@
 ...<br>
-===uclibc test - howto===
+====uclibc test - howto====
 Seems to require compilation on target. :-(
 * Within 'make menuconfig' -> toolchain enable 'Compile and install uClibc tests'
-==Test cases==
+postpone..

← Older revision		Revision as of 18:46, 1 October 2013
Line 1:		Line 1:
−	=Armadeus ~~Test~~ Integration=	+	=Armadeus Integration Test=

	Create automatic test & Validation tools		Create automatic test & Validation tools

@@ Line 33: / Line 33: @@
 #notify results (failure/fixed) to the lest commiters - Hudson and Jenkins feature
 #publish results on internet (pass or fail)
 ==Compilation Test Plan==
@@ Line 62: / Line 55: @@
 |----------------
 |}
 ==On target Test Plan==

← Older revision		Revision as of 22:24, 30 September 2013
Line 42:		Line 42:

	==Compilation Test Plan==		==Compilation Test Plan==
		+
		+	{\| border="1" cellpadding="5" cellspacing="0" summary="Compilation tests"
		+	\|- style="background:#efefef;"
		+	\| '''Test''' \|\| '''description''' \|\| '''Trigger''' \|\| '''Targets''' \|\| '''Severity'''
		+	\|----------------
		+	\| '''Source check''' \|\| check all packages for valid download URLs \|\| periodic / daily \|\| main boards \|\| medium / quite easy to find a backup server
		+	\|----------------
		+	\| '''Source checkout''' \|\| Downloads all sources needed for offline-build \|\| periodic / weekly \|\| main boards \|\| medium / quite easy to find a backup server
		+	\|----------------
		+	\| '''Build update''' \|\| rebuild (incremental) a board on a git change / Check makefile and BR patches \|\| GIt commit \|\| one board / apf51 \|\| critic / BSP is broken
		+	\|----------------
		+	\| '''Build boards ''' \|\| Offline build boards' main configs \|\| periodic / daily \|\| main boards \|\| critic / BSP is broken for some boards
		+	\|----------------
		+	\| '''Build test config''' \|\| Offline build all armadeux test configs \|\| periodic / weekly \|\| test configs \|\| medium
		+	\|----------------
		+	\| '''Release Source check''' \|\| check all packages for valid download URLs for the current release \|\| periodic / daily \|\| main boards \|\| medium / quite easy to find a backup server
		+	\|----------------
		+	\| '''Release build boards''' \|\| build boards' main configs with the current release \|\| periodic / monthly \|\| main boards \|\| critic / BSP release is broken
		+	\|----------------
		+	\|}

	==On target Test Plan==		==On target Test Plan==

@@ Line 24: / Line 24: @@
 ===Compilation Tests===
-Use a build farm to run the tests periodicaly (for each commit). [https://hudson.dev.java.net/ Hudson]  or [http://buildbot.net/trac buildbot] are good pretenders. There are many competitors here [http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix CI Matrix] <br>
+Use a build farm to run the tests periodicaly (for each commit). [https://hudson.dev.java.net/ Hudson] / [http://jenkins-ci.org jenkins] or [http://buildbot.net/trac buildbot] are good pretenders. There are many competitors here [http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix CI Matrix] <br>
-The packages have to be tested one at a time to avoid dependency problems. '''<- ! not for compilation ?!!'''
-<br>'''Do you mean download packages with make defconfig or test dependencies of each package? '''
-#checkout the head of svn
+#checkout the head of GIT
 #run build for each supported target
-#check build result ?? point 4 is not sufficient ? : '''Yes, It could be. This point aims to check the makefile.'''
+#check build result
-#check presence of binary images
+#check presence of binary images: post condition to be checked.
-#log error and warning (only the last xxx lines of the console ?) '''or at your convenience the full log of errors. It is open'''
+#log error and warning (only the last xxx lines of the console ?)
 #publish results on internet (pass or fail)

← Older revision		Revision as of 21:18, 30 September 2013
Line 5:		Line 5:
	==Changelog==		==Changelog==

		+	september 2013: Installation of a test server with Hudson / Jenkins

	==Introduction==		==Introduction==