<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 02.04.2015 00:45, Alexander Duda
wrote:<br>
</div>
<blockquote cite="mid:F64C824C-3D52-486D-A3FB-48F590A854EB@dfki.de"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<br>
<div>
<div>Am 01.04.2015 um 19:13 schrieb Sylvain Joyeux <<a
moz-do-not-send="true" href="mailto:bir.sylvain@gmail.com">bir.sylvain@gmail.com</a>>:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><br>
It is more than past time for that, so:<br>
- do you see a better way ? (I would personally really avoid
putting<br>
them in the orogen project for clarity and compilation times)<br>
- if you agree with the scheme, how would you feel about
moving the<br>
'test' packages along with the corresponding package (i.e.<br>
tests-orogen-transformer would go in rock.core), but disabled
by<br>
default ?<br>
</blockquote>
</div>
</blockquote>
-1 see below<br>
<blockquote cite="mid:F64C824C-3D52-486D-A3FB-48F590A854EB@dfki.de"
type="cite">
<div>
<div><br>
</div>
<div>For me the best solution would be to add the tests to the
orogen package itself. </div>
<div>orogen-camera/tests/tests.orogen </div>
<div>orogen-camera/tests/tasks/Task.hpp</div>
<div>…</div>
<div><br>
</div>
<div>I guess this is not supported by orogen. A fallback for me
would be to add all orogen unit tests of core orogen packages
into one common repository to not get too many repositories.</div>
</div>
</blockquote>
<br>
+1 for putting the in the orogen project itself instead of creating
anoteher one...<br>
...the tests can be disabled by default and need (simlar to the
metadata-support) to be activated explicitly.<br>
<br>
Matthias
</body>
</html>