Debian Codegraph @

autotest/README

raw
1 ================================================================================
2 ENGLISH
3 ================================================================================
4
5 To launch the test software (you can edit this simple script to adapt
6 the classpath):
7 ./autotest.sh file
8 where file is an xml file containing the list of tests to perform.
9 You should redirect the output (html code) to a file so that you can
10 visualize the results through a browser.
11
12 Some xml examples files are giver in testsuite/xml.
13
14 Tests are grouped by type, so you can organize them better.
15 A test allows to check only one path/url.
16
17 For each test, you can specify a description and the expected result
18 (validity, errors and warnings count).
19
20 Some test examples:
21 - test from a URI:
22 <test>
23 <url>http://css.example.com/path/to/the/real/example.css</url>
24 <description>example website</description>
25 <result valid="false">
26 <errors>24</errors>
27 <warnings>0</warnings>
28 </result>
29 </test>
30 - test from a local file:
31 <test>
32 <file>testsuite/general/misc/sampleCSS1.css</file>
33 <description>
34 This style sheet is written according to the suggested rendering in the
35 HTML 2.0 specification. Some styles, e.g. colors, have been added for
36 completeness. It is suggested that a style sheet similar to this one
37 is used as the UA default.
38 </description>
39 </test>
40
41 the <test> element can take a number of parameters, with values equivalent to the optional
42 parameters in the web service (see user manual for values listing):
43 examples:
44
45 <test profile="css1"> ...</test>
46 <test medium="print,screen">...</test>
47 <test warning="2"> ...</test>
48
49 ================================================================================
50 FRENCH
51 ================================================================================
52
53 Pour lancer le programme (vous pouvez editer ce script pour adapter le
54 classpath):
55 ./autotest.sh file
56 ou file est le fichier xml contenant la liste des tests a effectuer.
57 Il est conseille de rediriger la sortie (du code html) vers un fichier
58 afin de pouvoir visualiser les resultats depuis un navigateur.
59
60 Des exemples de fichiers xml sont presents dans testsuite/xml.
61
62 Les tests sont groupes par types, ce qui permet de savoir ce que l'on teste.
63 Un test permet de verifier un unique chemin/url.
64 On peut preciser pour chaque test une description, ainsi que le
65 resultat attendu (validite, nombre d'erreurs et de warnings).
66
67 Exemples de tests:
68 - une url:
69 <test>
70 <url>http://forums.jeuxonline.info</url>
71 <description>Forum of a French online gaming website</description>
72 <result valid="false">
73 <errors>24</errors>
74 <warnings>0</warnings>
75 </result>
76 </test>
77 - un fichier local:
78 <test>
79 <file>testsuite/general/misc/sampleCSS1.css</file>
80 <description>
81 This style sheet is written according to the suggested rendering in the
82 HTML 2.0 specification. Some styles, e.g. colors, have been added for
83 completeness. It is suggested that a style sheet similar to this one
84 is used as the UA default.
85 </description>
86
87 L'element <test> peut prendre plusieurs parametres (profile, medium et warning)
88 dont les valeurs sont equivalentes a celles du service de validation (Cf. manuel
89 du validateur pour les valeurs acceptées).
90
91 exemples:
92
93 <test profile="css1"> ...</test>
94 <test medium="print,screen">...</test>
95 <test warning="2"> ...</test>
96
97 </test>