[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: Filter and tests
From: Robert JACOLIN <rjacolin () ifrance ! com>
Date: 2002-03-29 8:40:13
[Download RAW message or body]
Le Vendredi 29 Mars 2002 00:02, Enno Bartels a écrit :
[snip]
>
> Okay - You did mean !?
> +winword
> + winword95
> + winword98
> + winword2000
> + winwordxp
Yes :)
> > > Next I would prefer to add screenshots of each test file. I do so for
> > > the applix-filters at home -> because I have no running applix-version
> > > on my home pc - only at work I have one. So I can work at home at the
> > > filter (if I have time) and look if the import result displayed by an
> > > koffice application is correct.
> >
> > Yes, I did for my filter ! See http://elbobby.free.fr/kword/index-en.html
>
> Very good - that's the right way to make the filter work more visible
>
> > > If someone would start adding features to some existing filter he can
> > > see the missing part on the screenshots.
> > > f I look at the screenshots of the docs displayed with applixware and
> > > if I then use the import filter I can see whats badly missing.
> > >
> > > And of course I have about 40 testfiles for my applix filters
> > > (and about 260 for the windraw filter - but thats not jet ready for
> > > kontour) But I could one share the private files - not my files on work
> > > -sorry!
> >
> > Doc must be specific to test some features with several difficulty for
> > each feature.
> > Some document with several features can be interresting but they
> > are less important.
>
> For kspread and applixword I have tested all main cell values in one test
> document and it was okay - only missing doubble lined cell frames. ....
Let's see that later, ok ?
> > > > Now, if we have a common directory, we can automatise (don't know if
> > > > it's a good english word) tests by a command which open all the
> > > > documents for
> > > > all filters every week/month/... Also we will know always the filters
> > > > status for all features (each document will test a feature, several
> > > > document can test
> > > > One/several feature(s) ).
> > >
> > > I can be automaticly generated a status file - if the application did
> > > or
> >
> > You can ? Right now ? How do you make that ?
>
> No I can not - error in understanding that!!!!!
>
> I can only thing that it would possible to create a html page automatic
> by testing each feature maybe throught dcop etc.
> AND that html page would not look like the status page. That html page
> would have listed all features tested without crashing - and not if
> I looks right !!!
Ok, sorry.
> That would be nice if someone could create scripts for this.
> For this there must be a place to in the kofficetests module - maybe the
> subdir "scripts".
I want understand dcop :)) but I will need some help.
First stage :
- Script 1 : write the script to test one filter ;
- Script 2 : write the script to test all filters (I think we must define a
xml file) ;
- generate html page (how can we do that ?With which tools ?).
Second stage :
- the script 2 must be make screenshot (How can we do that ? With which
tools ?).
- rewite the part which generate html page.
Opinion ?
> > > did not crash - but it can not generate the information if the feature
> > > is good displayed -
> >
> > Yes the result is binary (yes or no).
>
> Did not understand !
The informations are it's work OR it's not working. There are not more
informations. Other informations are welcomed -> screenshot.
1. Directory tree
> > > > When a release will be done, the features status filters page(s)
> > > > would be
> > > > added in the released document.
> > > >
> > > > I think it's also possible to make that for koffice applications.
> > >
> > > -----
> > >
> > > koffice-test-docs
> > > + general
> > > + xsltfilter
> > > + kword
> > > + abiword
> > > + amipro
> > > + applixword
> > > + ascii
> > > + docbook
> > > + html
> > > + latex
> > > + mif
> > > + mswrite
> > > + palmdoc
> > > + rtf
> > > + winword95
> > > + winword97
> > > + winword2000
> > > + windordxp
> > > + wml
> > > + wordperfect
> > > + kspread
> > > + applixspread
> > > + cvs
> > > + excel95
> > > + excel97
> > > + excel2000
> > > + excelxp
> > > + gnumeric
> > > + html
> > > + qpro
> > > + kpresenter
> > > + powerpoint95
> > > + powerpoint97
> > > + powerpoint2000
> > > + powerpointxp
> > > + kontour
> > > + applixgraphics
> > > + latex
> > > + msod
> > > + svg
> > > + wmf
> > > + xfig
> > > + ...
> >
> > Yes and no : the directory can be :
> > koffice-test-docs
> > + input
> > + kword
> > + parag
> > + picture
> > + list
> > - simple list
> > - embeded list
> > - two lists following
> > + header
> > + footer
> > + Miscellaneous (here perhaps special doc.
> > for somes filters).
> > - A very complex document to test all features in
> > the application
> > + output
> > + see your architecture
>
> I do not understand to separed between in an output exactly -
No because all features are same for all filter. Perhaps there are special
features for some filters. But list must be tested for all filter.
> I mean we can put both I one subdir. I think the idear of one subsubdir
> for each feature is good, because of some more files in each test case.
> Here is the resulting structure :
>
> kofficetests
> + scripts
> + general
> + xsltfilter
> + feature1
> + feature2
> + ...
> + kword
> + abiword
> + parag
> + picture
> + list
> - simple list
> - embeded list
> - two lists following
> + header
> + footer
> + Miscellaneous (here perhaps special doc.
> for somes filters).
> + ...
> + amipro
> ....
The parag. test files (for example) will be duplicated for all filters !
2. Description of the input xml file
This file describe all filter to test with all files.
<rootInput>input/</rootInput>
<rootOutput>output/</rootOutput>
<filter name="Winword97">
<title></title>(1)
<description></description>(1)
<tests>
<test>
<input>parag/test-parag1.doc</input> (2)
<output>parag/test-parag1.kwd</input> (3)
<screenshots>
<input>doc.png</input> (3)
<output>kwd.png</output> (3)
</screenshots>
</test>
</tests>
</filter>
(1) See below.
(2) root is kofficetest/input/
(3) root is kofficetest/ouput/, perhaps keep only maindoc.xml, or destroy kwd
file ?
3. Description of the html file generated :
> What has/should be in each subsubdir:
> - the testfile:
> example :bla.aw
Ok
> - optional: a/some screenshots of the testfile I the original application
> example: bla01.png
Ok but the bla-input.png and bla-output.png. To compare.
> - optional: a description file of the feature test
> example: bla.txt
Yes for a description file. Why not in xml to put informations in the html
file :
...
---------------------------------------
|Test 1 |
|---------------------------------------
| picture 1 | picture 2 | description |
---------------------------------------
|Test 2 |
|---------------------------------------
| picture 1 | failed | description|
---------------------------------------
...
See http://elbobby.free.fr/kword/index-en.html
> - else???
>
> And of course information has to be added on the filter status page of
> http://koffice.kde.org to follow to this place (kofficetests).
I hope :) !
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic