Nut upsdev - Apr 2015 - make environment for automated testcases

On 27/04/15 00:35, Charles Lepple wrote:
> autoreconf has to be run from the top level directory. 
I did that too.
> (Not related to this issue, but you might want to use the autogen.sh
> script to catch any other dependencies, then add
> --enable-maintainer-mode to the configure parameters so you don't need
> to manually re-run the auto-tools.) Do you have cppunit installed? 
I tried now:
%apt-get install libcppunit-dev
~/nut% ./autogen.sh
~/nut% ./configure --with-usb --with-dev --enable-maintainer-mode
~/nut% autoreconf -i
~/nut/tests% make clean;make
rm -f cppunittest
rm -rf .libs _libs
rm -f *.o
test -z "cppunittest.log" || rm -f cppunittest.log
test -z "cppunittest.trs" || rm -f cppunittest.trs
test -z "test-suite.log" || rm -f test-suite.log
rm -f *.lo
make: Nothing to be done for `all'.

But it still doesn't compile any executable: ~/nut/tests% ls
cpputest.cpp example.cpp  Makefile  Makefile.am  Makefile.in

Best

On Apr 27, 2015, at 2:48 AM, Nick Ma. <nick.mayerhofer at enchant.at>
wrote:
> But it still doesn't compile any executable: ~/nut/tests% ls
> cpputest.cpp example.cpp  Makefile  Makefile.am  Makefile.in
I think it is only intended to produce an executable when running "make
check" or the dist* targets.

-- 
Charles Lepple
clepple at gmail

2015-04-27 15:02 GMT+02:00 Charles Lepple <clepple at gmail.com>:
> On Apr 27, 2015, at 2:48 AM, Nick Ma. <nick.mayerhofer at enchant.at>
wrote:
>
> > But it still doesn't compile any executable: ~/nut/tests% ls
> > cpputest.cpp example.cpp  Makefile  Makefile.am  Makefile.in
>
> I think it is only intended to produce an executable when running
"make
> check" or the dist* targets.
>
confirmed. Note that this is just a base framework for unit testing that
Emilien has setup.
Emilien may be able to elaborate more on this topic...

A more comprehensive and system-oriented approach would be to use the tests
set available in Debian / Ubuntu:
http://anonscm.debian.org/cgit/collab-maint/nut.git/tree/debian/tests

It tests a wide number of things, from IPv4 and v6 reachability, to
commands and settings, including shutdown (simulation).

Note that I'm interested in having someone that could focus more on the QA
/ Testing dimension.
So if you're interested in Nick, feel free to contact me ;)

cheers,
Arno
-- 
Eaton Data Center Automation - Opensource Leader
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150428/a2b53115/attachment.html>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Charles,
that solved my problem, thanks!

Nick

On 27/04/15 15:02, Charles Lepple wrote:
> On Apr 27, 2015, at 2:48 AM, Nick Ma. <nick.mayerhofer at enchant.at>
wrote:
>
>> But it still doesn't compile any executable: ~/nut/tests% ls
>> cpputest.cpp example.cpp  Makefile  Makefile.am  Makefile.in
>
> I think it is only intended to produce an executable when running
"make check" or the dist* targets.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJVP4bYAAoJEDMnKdeJttQVUhYP+wbk1v4EGRWT8FGnG3K0O44d
J2h0dfa1vMY7IYTzFLz16fKPaqomnuhyLqaTug0F2+hf8A6BUnD0g80noFbwpJ1A
iEkFLAn6tV6i7rACxH3yJKa8R6nDMqITeVGZDw8Guag5I9cY18iWd16EMFTgn22L
6IAIPvyxWx3d5Tbzcn+RVQT81jPjnV1/NelZcXFedBdZ7zDI5GLXiWOs6vSK1kYo
NaO0fokEKfepOBniLiev//0TM+GYfeJfT/IUzY3ByYMyxG2mxzbAuZgFVqlnjxFW
QWT16Hc28WxwR2ZciDTFeMPeZyjbGvsYJFx+0eYOCuEHi3eB0Un0+qNtqxkVQlo2
X360IBV0DvPl4SLdpA6jkVdXZB7LdPIYN/eu6b22DgYl0hUW7GWBGrw5Qh0bCGih
AAe/2ealfV5y8Dw5tFTFrSA8uTGT2pvH5R9Hl40iRAozgyBb1qNBoXEC3IBSGXdW
OOG9dW4bfagbFuRGapjAjZlzY5a13i+i73bG5lAa/JE+6vgJGqcA66O1+5IvBJZi
4S0LRpJqmwOyymZAlStk5F+o6+7xeAHlvwAYSm7kLvAoEsk8SO40HYlDiQW0G8MS
6/U7UXsoTMvG91zhy+F16Bx6Wd2XtGEHB/zDQcq3rU4ScGQIX/oxoWU6+oql17LU
31g6gUxt/B6FVmVGgI7d
=5nmT
-----END PGP SIGNATURE-----