[qmtest] getting started

[John Schmitt]

This is very cool, thank you.

Links does interesting things, once I can figure out how to invoke menu
items.  Not having used links before, it's a bit confusing, but
workeable.

Konqueror 2.2.1 also works but the menus are a little bit off - I have
to be careful to move the mouse pointer down near the right side of the
File popdown menu, otherwise the popdown menu disappears as if I've
moved the mouse pointer out of that menu's rectangle.

Anyway, now I seem to be up and running.  I edited my http.conf to add
the ~/tdb Directory, restarted httpd and then invoked:

qmtest gui --no-browser -A 10.42.69.69 &

Then, I went to my windows machine and pointed my browser to that
address and voila!  I saw what I expected and the menu bar does things
and I can run all those tests.  Very nice indeed.

Thanks for the pointer - I'll probably be back. Right now, I'm going
back to the tutorial...

John

-----Original Message-----
From: Ricardo Anguiano [mailto:anguiano at codesourcery.com] 
Sent: Thursday, February 13, 2003 12:12 PM
To: John Schmitt
Cc: qmtest at codesourcery.com
Subject: Re: [qmtest] getting started

"John Schmitt" <jschmitt at kealia.com> writes:

> Thanks for the response.
> 
> Judging by the buttons in Mozilla's Preferences dialog box, Javascript
> is indeed on.  
> 
> (The README doesn't say so, but I take it for granted that you have to
> login as root to run 'make install' when I install qmtest from
sources)
> I deleted qmtest, and then reinstalled from sources rather than the
RPM,
> but exactly the same behaviour.  Running 'make check' after compiling
> reports that 29 tests ran and all 29 passed.
> 
> This is a bit of a downer for me.  If I can't get this going today, I
> may be reduced to using dejagnu and then writing tcl scripts for the
> next few months.  I'm trying to avoid that.
> 
> What other things could I check?  Are there resource/lock files that
> aren't being freed?  Is there an error log generated somewhere?
Setting
> QM_PYTHON_FLAGS=-v doesn't reveal anything interesting.  I can only
quit
> qmtest by closing the mozilla browser window and then pressing
control-c
> in the console window that launched qmtest.
> 
> Thanks for the help.

Do you have any other browser lying around?  Try starting qmtest like
this:

        qmtest gui --no-browser

It will spit out a URL to point your (other) favorite browser at.  For
example, the text mode browser "links" seems to do ok with the
javascript.  KDE and GNOME also have their own browsers which are
worth a shot.

-- 
Ricardo Anguiano
http://www.codesourcery.com