os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Add an entry on the testing suite work to the 2013Q4 report

Browse source 
Submitted by:	jmmv
This commit is contained in:
Gabor Pali 2013-12-20 20:14:37 +00:00
parent deea5eec83
commit 032a3ca816
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=43359
1 changed files with 74 additions and 1 deletions

75
en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml
View file

@ -19,7 +19,7 @@
<!-- XXX: Keep updating the number of entries --> <!-- XXX: Keep updating the number of entries -->
<p>Thanks to all the reporters for the excellent work! This report <p>Thanks to all the reporters for the excellent work! This report
contains 1 entry and we hope you enjoy reading it.</p> contains 2 entries and we hope you enjoy reading it.</p>
<p>The deadline for submissions covering between January and <p>The deadline for submissions covering between January and
March 2014 is April 7th, 2014.</p> March 2014 is April 7th, 2014.</p>
@ -64,4 +64,77 @@
documentation.</task> documentation.</task>
</help> </help>
</project> </project>
<project cat='proj'>
<title>&os; Test Suite</title>
<contact>
<person>
<name>
<given>Julio</given>
<common>Merino</common>
</name>
<email>jmmv@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://wiki.FreeBSD.org/TestSuite">Project page</url>
</links>
<body>
<p>The &os; Test Suite project aims to equip &os; with a
comprehensive test suite that is easy to run out of the box and
during the development of the system. The test suite is
installed into <tt>/usr/tests/</tt> and the <tt>kyua(1)</tt>
command-line tool (<tt>devel/kyua</tt> in the Ports Collection)
is used to run them.</p>
<p>The benefits of having a test suite that is easy to use and
continuously run are obvious: regressions can be caught sooner
rather than later and the Release Engineering Team can better
assess the quality of the tree before deciding to cut a release.
Additionally, and because we choose to install the tests, we
also allow any end user to perform sanity checks on new
installations of the system on his or her particular hardware
configuration &mdash; a very attractive thing to do when
deploying production servers.</p>
<p>During the last few months, we have added the necessary pieces to
the build system to support building and installing test programs of
various kinds. To demonstrate the functionality of these, some test
programs were added and others were migrated from the old testing tree
in <tt>tools/regression/</tt> to the new layout for tests.</p>
<p>The current test suite should be seen as a proof of concept at this
point: it is only composed of a small set of test programs and the goal
is to get the infrastructure in place before mass-migrating existing
test code and/or importing external tests.</p>
<p>As part of this work, two new releases of Kyua were published.
Of special interest is the addition of a TAP-compliant backend so
that existing tests from <tt>tools/regression/</tt> can be
plugged into the test suite with minimum effort.</p>
</body>
<help>
<task>We have got three machines in which to set up a continuous
testing system. This work is in progress. Once done, periodic
test reports will be available online.</task>
<task>Related to the above, the Kyua reporting engine needs
significant tuning to make the reports nice and clean. These
changes will come after the basic infrastructure is in
place.</task>
<task>A tutorial on writing tests for &os; has been proposed for
AsiaBSDCon&nbsp;2014. The outcome of the proposal is still
unknown, but stay tuned!</task>
<task>Port, port, and port more tests to the new test suite. A
test suite is worthless if it does not validate stuff! Stay tuned
for a request for help when we have put all basic pieces in
place and have streamlined the migration process.</task>
</help>
</project>
</report> </report>