[qmtest] The state of GUI

Vladimir Prus ghost at cs.msu.su
Mon Apr 18 14:27:01 UTC 2005


On Monday 18 April 2005 17:19, Stefan Seefeld wrote:
> Vladimir Prus wrote:
> > On Thursday 07 April 2005 13:57, Stefan Seefeld wrote:
> >>I don't think it's QMTest's job to keep track of a toolchain taxonomy.
> >
> > No, but ideally there should be a an extension mechanism I can use to
> > define expectation in any way I like.
>
> The simplest approach would provide the python API to manipulate results
> (result files), and users would write their own python scripts using
> qmtest's python modules, instead of using the 'qmtest' CLI.
> In any way, that's the first step to any solution.

Sure.

> >>>Yea, but if people decide that editing 15 files for 15 versions of "yfc"
> >>>is not too nice (even with GUI), they should be able to do something.
> >>>Like using custom file format.
> >>
> >>I don't think a custom file format is a good idea, as I don't believe
> >>QMTest itself should care about these things. However, once we have an
> >> API to manipulate expectation files it should be easy for you to define
> >> some aliasing mechanism that lets you make modifications that get
> >> propagated to all instances that are in your alias list. But again, that
> >> would be on top of such a 'QMTest API'.
> >
> > If fact, if there's "qmtest report" that takes N test results and N
> > expected result and produces a report, then I can write a script that
> > takes N toolset names and a expectation file in Boost format and produces
> > N separate expected result files, which can be used by "qmtest report".
> >
> > Seems workable.
>
> I think qmtest should store the expectation within the result file as
> annotation, so 'qmtest report' would only have to load N result files.

So, the procedure would be:

   qmtest run -O expected1.qmr -o results1.qmr
   qmtest run -O expected2.qmr -o results2.qmr
   qmtest report results1.qmr results2.qmr -o report.html

And the "qmtest run" invocation will use the expectedN.qmr files to add 
annotations to test results? I think that's fine.
   
- Volodya



More information about the qmtest mailing list