Bug 1903593 - Add a location for a performance testing guide. r=aglavic,perftest-reviewers DONTBUILD

This patch adds a new location for a performance testing guide called "Performance Testing in a Nutshell". It'll contain an overview of all the information needed for understanding performance testing at Mozilla.

Differential Revision: https://phabricator.services.mozilla.com/D214282
This commit is contained in:
Greg Mierzwinski 2024-07-03 15:37:25 +00:00
Родитель c030ceea65
Коммит b8709790fc
4 изменённых файлов: 108 добавлений и 0 удалений

Просмотреть файл

@ -15,6 +15,7 @@ Performance Testing
mozperftest
perf-sheriffing
performance-infrastructure
perftest-in-a-nutshell
raptor
talos
@ -32,6 +33,7 @@ For more detailed information about each test suite and project, see their docum
* :doc:`mozperftest`
* :doc:`perf-sheriffing`
* :doc:`performance-infrastructure`
* :doc:`perftest-in-a-nutshell`
* :doc:`raptor`
* :doc:`talos`

Просмотреть файл

@ -0,0 +1,49 @@
=================================
Performance Testing in a Nutshell
=================================
.. contents::
:depth: 3
.. note::
This page is still under construction, and is missing the videos.
In this document, you'll find all the information needed regarding the basics of performance testing our products. A set of videos, and instructions can be found to guide you across the various subjects related to performance testing. If you're new to performance testing, starting from the first section would be the most helpful for you.
Help! I have a regression. What do I do?
----------------------------------------
Most people will first be introduced to performance testing at Mozilla through an alert like so:
# Add image of alert summary here
This alert summary provides all the info required to understand what regressed, and provides info on the next steps for debugging it.
Running Performance Tests
-------------------------
Placeholder.
Performance Comparisons
-----------------------
Placeholder.
Using the Firefox Profiler
--------------------------
The Firefox Profiler can be used to help with debugging performance issues in your code. `See here for documentation <https://profiler.firefox.com/docs/#/>`_ on how it can be used to better understand where the regressing code is, and what might be causing the regression. Profiles are provided on each alert summary bug from before, and after the regression (add more info).
Adding Performance Tests
------------------------
Placeholder.
Additional Help
---------------
Reach out to the Performance Testing, and Tooling team in the `#perftest channel on Matrix <https://matrix.to/#/#perftest:mozilla.org>`_, or the #perf-help channel on Slack.

Просмотреть файл

@ -0,0 +1,8 @@
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
---
name: perftest-in-a-nutshell
manifest: None
static-only: True
suites: {}

Просмотреть файл

@ -0,0 +1,49 @@
=================================
Performance Testing in a Nutshell
=================================
.. contents::
:depth: 3
.. note::
This page is still under construction, and is missing the videos.
In this document, you'll find all the information needed regarding the basics of performance testing our products. A set of videos, and instructions can be found to guide you across the various subjects related to performance testing. If you're new to performance testing, starting from the first section would be the most helpful for you.
Help! I have a regression. What do I do?
----------------------------------------
Most people will first be introduced to performance testing at Mozilla through an alert like so:
# Add image of alert summary here
This alert summary provides all the info required to understand what regressed, and provides info on the next steps for debugging it.
Running Performance Tests
-------------------------
Placeholder.
Performance Comparisons
-----------------------
Placeholder.
Using the Firefox Profiler
--------------------------
The Firefox Profiler can be used to help with debugging performance issues in your code. `See here for documentation <https://profiler.firefox.com/docs/#/>`_ on how it can be used to better understand where the regressing code is, and what might be causing the regression. Profiles are provided on each alert summary bug from before, and after the regression (add more info).
Adding Performance Tests
------------------------
Placeholder.
Additional Help
---------------
Reach out to the Performance Testing, and Tooling team in the `#perftest channel on Matrix <https://matrix.to/#/#perftest:mozilla.org>`_, or the #perf-help channel on Slack.