blob: ed8d9947a91ba5431d501bbe12a64132b0f625df (
plain)
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
|
Running a performance test
==========================
You can run `perftest` locally or in Mozilla's CI
Running locally
---------------
Running a test is as simple as calling it using `mach perftest` in a mozilla-central source
checkout::
$ ./mach perftest
The `mach` command will bootstrap the installation of all required tools for the
framework to run, and display a selection screen to pick a test. Once the
selection is done, the performance test will run locally.
If you know what test you want to run, you can use its path explicitly::
$ ./mach perftest perftest_script.js
`mach perftest` comes with numerous options, and the test script should provide
decent defaults so you don't have to bother with them. If you need to tweak some
options, you can use `./mach perftest --help` to learn about them.
Running in the CI
-----------------
.. warning::
If you are looking for how to run performance tests in CI and ended up here, you might want to checkout :ref:`Mach Try Perf`.
.. warning::
If you plan to run tests often in the CI for android, you should contact the android
infra team to make sure there's availability in our pool of devices.
You can run in the CI directly from the `mach perftest` command by adding the `--push-to-try` option
to your locally working perftest call.
This call will run the fuzzy selector and then send the job into our CI::
$ ./mach perftest --push-to-try
We have phones on bitbar that can run your android tests. Tests are fairly fast
to run in the CI because they use sparse profiles. Depending on the
availability of workers, once the task starts, it takes around 15mn to start
the test.
|
