<div dir="ltr"><div>Good day Mr. Engwer, <br><br></div><div>At first, thank you for your reply, it definitely helped me through to the right things I have to put an accent on. On the other side, I apologize for not responding yesterday, but the Hannover Messe (+ travelling to there) took a lot from my time.<br>
<br></div><div>Anyhow, today I continue discovering more about dune and the dune-autobuild tests. I also looked at this presentation of yours [1], which gave me also some insight about autobuild. <br></div><div> <br></div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
We are currently using the automake test system to handle our<br>
tests. automake allows to specify applications to run as tests. These<br>
applications (and some further tests) are also run for our automated<br>
tests. Sadly the automated tests are currently in no good shape, but<br>
everybody can run the tests in his/her dune-src tree via the "make<br>
check" target.</blockquote><div> </div><div>I hope this will be the summer when the tests will be back into excellent shape ! <br></div><div> </div><div>Regarding automake, I am reading through this book to get more familiar with the tool [2].<br>
</div><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
We currently do several different kind of tests: </blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
- unit tests:<br>
test apps with hand-written unit test, no particular unit-test<br>
library is used<br>
(run via make check)<br>
- buildsystem tests:<br>
we have some minimal checks to ensure that all src files are<br>
handled in the tar-balls and in the installation<br>
(run via make sourcescheck)<br>
- src consitency check:<br>
headers should be self contained, thus we can test that every<br>
header is in a shape that allows to compile it, especially this<br>
means that all required headers are included. Some headers are not<br>
intended as "interface" headers, so we can exclude these from the<br>
test.<br>
(run via make headercheck)<br>
- system tests:<br>
System tests allow to check the interplay of all components. This<br>
is work in a relatively early stage. It is only available for<br>
dune-pdelab and requires to write bigger<br>
test-applications. Success/failure is detected by a fuzzy<br>
comparison with reference data or reference logs. </blockquote><div><br></div><div>Thank you for the detailed explanation of the way the tests are managed and divided into parts.<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<br>
The architecture of the autobuild system is shortly described in<br>
doc/overview.tex in the dune-autobuild repo <a href="https://svn.dune-project.org/svn/dune-autobuild/" target="_blank">https://svn.dune-project.org/svn/dune-autobuild/</a><br></blockquote><div> </div><div>After having some small issues because of my proxy, I
managed to cofigure my svn settings so that to be able to copy the
repository without any problem. Now everything is set up for trying out and discovering in more details how it functions. <br></div>I also am reading in this moment this manual about advanced bash Programming [3], because in the README file it is said that one should read about this topic. In addition, as you said, I went to the "overview.tex" file and saw the way it works. Plus, I saw the images from the presentation and knew I was on the right track :). <br>
<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
I hopy this gives some first starting points. Feel free to ask further<br>
questions. I'll try to update the project description soon and add<br>
more details. </blockquote><div> </div><div>I will work this weekend on all things I mentioned, and inform you about my progress as soon as the beginning of next week. I hope that is fine with you.<br><br></div><div>Thank you very much for your guidance.<br>
</div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<br>
> [*1*] <a href="https://live.gnome.org/GnomeWomen/OutreachProgram2012" target="_blank">https://live.gnome.org/GnomeWomen/OutreachProgram2012</a><br>
<br>
I remember having read some of your posts last year.<br></blockquote><div> </div><div>I was totally astonished when I read this last statement of yours ! It was definitely one BIG Überraschung ! :)<br><br></div><div>Thank you once again, <br>
<br></div><div>Respectfully, <br></div><div>Elena Petrevska<br><br></div><div><br>[1] <a href="http://www.dune-project.org/publications/dune_autobuild.pdf">http://www.dune-project.org/publications/dune_autobuild.pdf</a><br>
[2] <a href="http://www.gnu.org/software/automake/manual/automake.pdf" target="_blank">http://www.gnu.org/software/automake/manual/automake.pdf</a> <br></div><div>[3] <a href="http://tldp.org/LDP/abs/html/">http://tldp.org/LDP/abs/html/</a><br>
</div>
</div>