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
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
|
PerfDocs
========
`PerfDocs`_ is a tool that checks to make sure all performance tests are documented in tree.
At the moment, it is only used for this documentation verification, but in the future it will also auto-generate documentation from these descriptions that will be displayed in the source-docs documentation page (rather than the wiki, which is where they currently reside).
Run Locally
-----------
The mozlint integration of PerfDocs can be run using mach:
.. parsed-literal::
$ mach lint --linter perfdocs .
Documentation can be regenerated for performance tests by including the ``--fix`` flag:
.. parsed-literal::
$ mach lint --linter perfdocs . --fix
Configuration
-------------
There are no configuration options available for this linter. It scans the full source tree under ``testing``, looking for folders named ``perfdocs``, validates their content, and regenerates the documentation (if ``--fix`` is provided). This has been implemented for all performance testing harnesses, and the documentation generated gets displayed in :ref:`Performance Testing`.
In the ``perfdocs`` folders, there needs to be an ``index.rst`` file and it needs to contain the string ``{documentation}`` in some location in the file which is where the test documentation will be placed. The folders must also have a ``config.yml`` file following this schema:
.. code-block:: python
CONFIG_SCHEMA = {
"definitions": {
"metrics_schema": {
"metric_name": {
"type": "object",
"properties": {
"aliases": {"type": "array", "items": {"type": "string"}},
"description": {"type": "string"},
"matcher": {"type": "string"},
},
"required": ["description", "aliases"],
},
},
},
"type": "object",
"properties": {
"name": {"type": "string"},
"manifest": {"type": "string"},
"static-only": {"type": "boolean"},
"metrics": {"$ref": "#/definitions/metrics_schema"},
"suites": {
"type": "object",
"properties": {
"suite_name": {
"type": "object",
"properties": {
"tests": {
"type": "object",
"properties": {
"test_name": {"type": "string"},
},
},
"description": {"type": "string"},
"owner": {"type": "string"},
},
"required": ["description"],
}
},
},
},
"required": ["name", "manifest", "static-only", "suites"],
}
Here is an example of a configuration file for the Raptor framework:
.. parsed-literal::
name: raptor
manifest: testing/raptor/raptor/raptor.toml
suites:
desktop:
description: "Desktop tests."
tests:
raptor-tp6: "Raptor TP6 tests."
mobile:
description: "Mobile tests"
benchmarks:
description: "Benchmark tests."
tests:
wasm: "All wasm tests."
Metrics that produce alerts can also be documented like so:
.. parsed-literal::
name: raptor
manifest: testing/raptor/raptor/raptor.toml
metrics:
"First Paint":
description: "The description of the metric."
aliases:
- fcp
- anAliasForFCP
# Optional regex to match the metrics found in the tests with this
# documented metric
matcher: f.*
suites:
desktop:
description: "Desktop tests."
tests:
raptor-tp6: "Raptor TP6 tests."
mobile:
description: "Mobile tests"
benchmarks:
description: "Benchmark tests."
tests:
wasm: "All wasm tests."
The documented metrics must exist in the tests for the suite. If they are not, then validation will fail. The same is true if a metric in a test is not documented. Also, if ``metrics`` are defined, then a ``metrics.rst`` file is expected to be found in the ``perfdocs`` folder for the given suite. It must contain the string ``{metrics_documentation}`` where the documentation should be added. The ``metrics.rst`` is renamed ``{suite-name}-metrics.rst`` in the generated folder, so if it needs to be linked to in the ``index.rst`` file, it should contain a ``{metrics_rst_name}`` string for where the link should be added - it's expected to be found in a toctree section.
Note that there needs to be a FrameworkGatherer implemented for the framework being documented since each of them may have different ways of parsing test manifests for the tests. See `RaptorGatherer <https://searchfox.org/mozilla-central/source/tools/lint/perfdocs/framework_gatherers.py>`_ for an example gatherer that was implemented for Raptor.
Sources
-------
* `Configuration <https://searchfox.org/mozilla-central/source/tools/lint/perfdocs.yml>`__
* `Source <https://searchfox.org/mozilla-central/source/tools/lint/perfdocs>`__
|
