1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
Regression Testing
==================
To build a test utility configure libass with the `--enable-compare` flag.
The utility works with `png` image files so there is external dependency of libpng.
Test program command line:
`compare ([-i] <input-dir>)+ [-o <output-dir>] [-s <scale:1-8>]`
* `<input-dir>` is a test input directory, can be several of them;
* `<output-dir>` if present sets directory to store the rendering results;
* `<scale>` sets an oversampling factor (positive integer up to 8, default 1).
An input directory consists of font files (`*.ttf`, `*.otf` and `*.pfb`), subtitle files (`*.ass`), and image files (`*.png`).
All the fonts required for rendering should be present in the input directories as
libass is configured to not use anything external outside of it (`ASS_FONTPROVIDER_NONE`).
After loading all the fonts in the directories, the test program scans for subtitle files (`<sub_name>.ass`)
and their corresponding image files in the form of `<sub_name>-NNNN.png`,
where `NNNN` is an arbitrary number of decimal digits.
The subtitle file then would be rendered at the time of `NNNN` milliseconds and compared with the loaded image file.
For example, an input directory can have the following structure:
```
test/
font1.ttf
font2.otf
sub1.ass
sub1-0500.png
sub1-1500.png
sub1-2500.png
sub2.ass
sub2-153000.png
```
More precisely, the test program (`compare`) would scan all input directories and do the following:
1) load all the fonts found (`*.ttf`, `*.otf`, `*.pfb`);
2) search for subtitle files (`*.ass`);
3) for every file found (`<sub_name>.ass`) scan for the files with names of `<sub_name>-NNNN.png`;
4) interpret `NNNN` as a time in milliseconds and render the subtitle file at that time with a transparent background;
5) fuzzy compare the rendering result with the corresponding png file;
6) save the rendering result in the output directory if requested.
Target images should be transparent RGBA png files with 8 or 16 bits per channel.
A subtitle rendering resolution is determined by the extents of the target image files multiplied by an optional scale factor (`-s` switch).
In the case of nontrivial scale factor, the result would be downsampled using 16-bit precision before comparison.
Downsampling is done assuming a linear color space which is physically incorrect but commonly used in computer rendering.
It's possible to save rendering results by using `-o` switch.
Saved files would have the same names as the target image files.
That functionality can be used for an initial generation of target images
by supplying arbitrary source images with correct names and extents.
Test program output can look like the following:
```
Loading font 'font1.ttf'.
Loading font 'font2.otf'.
Processing 'sub1.ass':
Time 0:00:00.500 - 2.464 BAD
Time 0:00:01.500 - 1.412 OK
Time 0:00:02.500 - 4.919 FAIL
Processing 'sub2.ass':
Time 0:02:33.000 - 0.728 OK
Only 3 of 4 images have passed test
```
For each target image file the program reports a maximal ratio of the per pixel comparison error to the baseline error scale.
The baseline error scale tries to take account of neighboring pixels to estimate visibility of an error in that specific pixel location.
Currently the range of [0–2.0] is marked as `OK`, the range of [2.0–4.0] as `BAD` and more than 4.0 as `FAIL`.
At the end there is a summary of how many images don't fail tests.
If all images pass that test the program returns 0 otherwise 1.
Note that almost any type of a rendering error can be greatly exaggerated by the specially tailored test cases.
Therefore test cases should be chosen to represent generic real world scenarios only.
|
