re: no test structure in place for wine programs

[Dan Kegel]

Darren wrote:
> Should I try to take the dll test structure (mainly just the
> dlls/Maketest.rules.in file) and port this into the programs area?
>
> or is that overboard for that area?

It's something we need eventually, but for now it would
probably be enough to just attach a standalone test
that invoked msiexec.exe and printed out PASS or FAIL
to http://bugs.winehq.org/show_bug.cgi?id=9628

It's not worth the effort to create the generic app
test framework inside the wine tree at the moment.

no test structure in place for wine programs

[Thomas Kho]

On Wed, Apr 23, 2008 at 3:11 PM, Dan Kegel <dank(a)kegel.com> wrote:
> Darren wrote:
> > Should I try to take the dll test structure (mainly just the
> > dlls/Maketest.rules.in file) and port this into the programs area?
> >
> > or is that overboard for that area?
>
> It's something we need eventually, but for now it would
>  probably be enough to just attach a standalone test
>  that invoked msiexec.exe and printed out PASS or FAIL
>  to http://bugs.winehq.org/show_bug.cgi?id=9628
>
> It's not worth the effort to create the generic app
>  test framework inside the wine tree at the moment.

For what it's worth, I filed a feature request for something like this
some time ago. At the time, the suggestion was to use cxtest.

See http://bugs.winehq.org/show_bug.cgi?id=5616

-Tom