re: Direct3D Game test framework

[Dan Kegel]

Michal Okresa wrote:
> We (people around CxTest) think that extending CxTest is better approach
> to achieve your goals rather than writing new application or modifying
> existing. It could be done with smaller effort (in opposite of
> AutoHotkey, AutoIt, ...) because CxTest is  specialised for testing Wine
> and CrossOver and it can deal with wine's specifics.

I agree that CxTest has many good features, and that
any tests we write should run under CxTest.

However, I think it's useful and important for us to
write tests that can easily be run with no
complicated CxTest installation.  I also think
it's useful and important for us to be able to
run our tests on Windows.
That's why I started yawt; it's a single python
source file that runs automated tests written
in AutoHotkey (and a little python).
It runs perfectly well on both Windows and Wine,
and my goal is to make yawt plug in to CxTest so
yawt tests can still easily be run on Windows
or Linux standalone, *or* be run from inside the
CxTest machinery.

I'm sure there will always be some tests that are
better written directly in CxTest, but I'm going to
try to push yawt forward, too.  With
luck we'll have the two test systems working
well together in a month or two.
- Dan

Direct3D Game test framework

[martin pilka]

Hello Dan!
> I'm sure there will always be some tests that are
> better written directly in CxTest, but I'm going to
> try to push yawt forward, too.  With
> luck we'll have the two test systems working
> well together in a month or two.

YAWT looks interesting, I also had a look to AutoHotKey, and its language
seems to solve some of the problems we have with CxTest scripts (double click,
better support for menus, better conditioning). It also introduces hard
dependency on Windows and Wine (CxTest can test also X11 apps), which is
problematic in case of i.e. CrossOver installation (X11 based app).

We try to write some tests in YAWT and see how it works. Regarding Direct3D
testing framework, we try both YAWT and CxTest and use whatever is easier to
use for that purpose. Important thing is that Stefan does not create new
server side (PHP code and some things around), we should just extend current
implementation with ability to generate 2D graphs, then we have everything in
one place (Wine make test results, Direct3d performance results) instead of
several web pages with pieces of information.

Martin

Direct3D Game test framework

[Dan Kegel]

Martin wrote:
> YAWT looks interesting

Thanks!  If you need any changes in it, ask Lei (or ask me to ask Lei).
> I also had a look to AutoHotKey, and its language
> seems to solve some of the problems we have with
> CxTest scripts (double click, better support for menus, better conditioning).

It is also popular and under active development,
so lots of Windows people who know it already
might be coaxed into writing tests for us.
> It also introduces hard dependency on Windows and Wine

That should be Windows *or* Wine :-)
> CxTest can test also X11 apps ... e.g. CrossOver installation

Yeah, I don't think the CxTest scripting should go away,
I suspect it's going to be useful for testing mixed windows / X
situations.

- Dan