[qmtest] Newbie help with QMTest

[Gary Oberbrunner]

Stefan wrote:
> Hi Gary, ...
> This is due to me publishing an online tutorial that doesn't correspond to the
> last official release, but instead the current version from the repository.
> I'm sorry for the confusion. (I'll try hard to wrap up all the current work to
> get ready for another release.)
> 
> Meanwhile, you can use the '--output' option instead. Noting that with the XMLDatabase
> there is a 1-1 correspondence between test file (.qmt) names and test ids, you can
> write the above command as
> 
> qmtest create --output=python_pass.qmt -a expression='True' test python.ExecTest
> 
> having the exact same effect.
> 
> Let me know what your current expectations are, i.e. what features you are
> particularly interested in. Depending on that you may continue using the 2.3
> release, or try a current snapshot instead.

Hi -- thanks for the info, and sorry for the delay in replying!  Turns out I
wasn't subscribed, and missed your response until I stumbled over it in the
archives... totally my fault :-(

What I'm hoping for is to use QMTest just like SCons does for testing cmd line
programs, basing success/failure on exit status and stdout/err.  I expect to
have some things like QMTest/TestCmd.py, QMTest/TestCommon.py, and so on (just
like SCons).  Then I want to put a bunch of test-foo.py files into a dir, and
have "qmtest run" run them!

As for the tutorial, I used your change above, and that works.  But then the
next command 'qmtest ls' also fails.  But "qmtest gui" works!  Very nice!
Also qmtest run now works.  I notice that creating a test as above only
creates a .qmt file in the current dir; it doesn't change anything in the
QMTest subdir.  Is that expected?

So if I wanted to use TestCmd.py (and/or TestCommon.py) from SCons, and define
a test based on it so I could add my test_foo.py files, what would my next
steps be?  Sorry to be such a newbie on this.

Thanks!

-- 
Gary