175 lines
4.1 KiB
Markdown
Raw Normal View History

2016-01-07 17:14:05 +01:00
Algorithm tests
===============
2016-03-13 11:14:06 +01:00
To test algorithms you can add entries into `testdata/qgis_algorithm_tests.yaml` or `testdata/gdal_algorithm_tests.yaml` as appropriate.
2016-01-07 17:14:05 +01:00
This file is structured with [yaml syntax](http://www.yaml.org/start.html).
A basic test appears under the toplevel key `tests` and looks like this:
```yaml
- name: centroid
algorithm: qgis:polygoncentroids
params:
- type: vector
name: polys.gml
results:
OUTPUT_LAYER:
type: vector
name: expected/polys_centroid.gml
```
2016-01-07 17:14:05 +01:00
How To
------
To add a new test you can follow these steps:
Run the algorithm you want to test in QGIS from the processing toolbox. If the
2016-02-23 13:23:12 +01:00
result is a vector layer prefer GML as output for its support of mixed
2016-01-07 17:14:05 +01:00
geometry types and good readability. Redirect output to
`python/plugins/processing/tests/testdata/expected`
When you have run the algorithm, go to "Processing" > "History" and find the
algorithm which you have just run. Right click the algorithm and click "Create test".
A new window will open with a text definition.
2016-01-07 17:14:05 +01:00
Open the file `python/plugins/processing/tests/testdata/algorithm_tests.yaml`,
copy the text definition there.
2016-01-07 17:14:05 +01:00
The first string from the command goes to the key `algorithm`, the subsequent
ones to params and the last one(s) to results.
The above translates to
```yaml
- name: densify
algorithm: qgis:densifygeometriesgivenaninterval
params:
- type: vector
name: polys.gml
- 2 # Interval
results:
OUTPUT:
type: vector
name: expected/polys_densify.gml
```
2016-01-07 17:14:05 +01:00
Params and results
------------------
### Trivial type parameters
Params and results are specified as lists or dictionaries:
2016-01-07 17:14:05 +01:00
```yaml
params:
INTERVAL: 5
INTERPOLATE: True
NAME: A processing test
```
or
2016-01-07 17:14:05 +01:00
```yaml
params:
- 2
- string
- another param
```
2016-01-07 17:14:05 +01:00
### Layer type parameters
2016-01-07 17:14:05 +01:00
You will often need to specify layers as parameters. To specify a layer you will need to specify:
2016-01-07 17:14:05 +01:00
* the type
* `vector` or `raster`
* a name
* relative path like `expected/polys_centroid.gml`
2016-01-07 17:14:05 +01:00
2016-02-29 21:25:47 +01:00
This is what it looks like in action:
```yaml
params:
PAR: 2
STR: string
LAYER:
type: vector
name: polys.gml
OTHER: another param
```
2016-01-07 17:14:05 +01:00
### Results
2016-01-07 17:14:05 +01:00
Results are specified very similar.
2016-01-07 17:14:05 +01:00
#### Basic vector files
It couldn't be more trivial
```yaml
OUTPUT:
name: expected/qgis_intersection.gml
type: vector
```
#### Vector with tolerance
2016-01-07 17:14:05 +01:00
Sometimes different platforms create slightly different results which are
still acceptable. In this case (but only then) you may also use additional
properties to define how exactly a layer is compared.
To deal with a certain tolerance for output values you can specify a
`compare` property for an output. The compare property can contain sub-properties
for `fields`. This contains information about how precisely a certain field is
compared (`precision`) or a field can even entirely be `skip`ed. There is a special
field name `__all__` which will apply a certain tolerance to all fields.
There is another property `geometry` which also accepts a `precision` which is
applied to each vertex.
2016-01-07 17:14:05 +01:00
```yaml
OUTPUT:
type: vector
name: expected/abcd.gml
compare:
fields:
__all__:
precision: 5 # compare to a precision of .00001 on all fields
A: skip # skip field A
geometry:
precision: 5 # compare coordinates with a precision of 5 digits
```
#### Raster files
Raster files are compared with a hash checksum. This is calculated when you create
a test from the processing history.
```yaml
OUTPUT:
type: rasterhash
hash: f1fedeb6782f9389cf43590d4c85ada9155ab61fef6dc285aaeb54d6
```
#### Files
You can compare the content of an ouptut file by an expected result reference file
```yaml
OUTPUT_HTML_FILE:
name: expected/basic_statistics_string.html
type: file
```
Or you can use one or more regular expressions that will be [matched](https://docs.python.org/2/library/re.html#re.search) against the file
content
```yaml
OUTPUT:
name: layer_info.html
type: regex
rules:
- 'Extent: \(-1.000000, -3.000000\) - \(11.000000, 5.000000\)'
- 'Geometry: Line String'
- 'Feature Count: 6'
```