Problems with first steps
David Chamont
chamont at llr.in2p3.fr
Tue Oct 16 14:53:22 UTC 2007
Hi,
I am a new user, so I apologize for the dummy questions, or the
feature request which will certainly not take into account the
history of the product. My single source of knowledge till now
is the 2.4 user guide.
I am trying to set up a first test suite.
My application is compiled with an external product which is
preparing a makefile, and then I type "make".
I tried to declare the compilation step as a resource :
qmtest create -i myProg -a 'command="cd ../build && make"'
resource command.ShellCommandTest
Unhappily, Qmtest does not accept a command.ShellCommandTest as
a resource. The user guide let me think that perhaps it would work,
and I would have liked, because the provided resources are quite limited
to basic compilation process.
Well, I then tried to declare my "make" command as a "test", which I
planned to declare as a prerequisite to the further execution tests :
qmtest create -i myProg -a 'command="cd ../build && make"'
test command.ShellCommandTest
Now, my problem is that this newly created test seems to
be invisible to qmtest. Qmtest does not list it, althought it is listing
correctly the fake python tests I have declared before.
The output of "qmtest ls -lr" :
directory dir1
test python.ExecTest dir1.one
test python.ExecTest dir1.two
directory dir2
directory dir2.dir3
test python.ExecTest dir2.dir3.one
test python.ExecTest dir2.dir3.two
test python.ExecTest dir2.one
test python.ExecTest python_fail
test python.ExecTest python_pass
The ouput of "ls" :
myProg.qmt
dir1.qms
dir2.qms
python_fail.qmt
python_pass.qmt
QMTest
results.qmr
Any idea ?
A detail : for consistency, "qmtest ls ." should work, just the same
as "qmtest run .", no ?
Cheers.
David.
--
David Chamont
(33)1.69.33.56.33
LLR - IN2P3 - CNRS - Ecole Polytechnique
More information about the qmtest
mailing list