blob: a70adb0464899f9cb4183ebe85e8e47e9c48b18d (
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
|
Bug pipeline
============
For Firefox quality, Mozilla has different processes to report defects. In parallel, over the years, Mozilla developed many tools around bug management.
.. mermaid::
graph TD
classDef tool fill:#f96;
Community --> B(bugzilla.mozilla.org)
QA --> B
Foxfooding --> B
Fuzzing --> B
SA[Static/Dynamic analysis] --> B
P[Performance monitoring] --> B
Y[Test automation] --> B
Z[Crash detection] --> B
B --> C{Bug update}
C --> D[Metadata improvements]
C --> E[Component triage]
C --> F[Test case verification]
F --> BM{{Bugmon}}:::tool
F --> MR{{Mozregression}}:::tool
D --> AN{{Autonag}}:::tool
E --> BB{{bugbug}}:::tool
D --> BB
More details
------------
* :ref:`Fuzzing`
* `Autonag <https://wiki.mozilla.org/Release_Management/autonag#Introduction>`_ - `Source <https://github.com/mozilla/relman-auto-nag/>`_
* `Bugbug <https://github.com/mozilla/bugbug>`_ - `Blog post about triage <https://hacks.mozilla.org/2019/04/teaching-machines-to-triage-firefox-bugs/>`_ / `Blog post about CI <https://hacks.mozilla.org/2020/07/testing-firefox-more-efficiently-with-machine-learning/>`_
* `Bugmon <https://hacks.mozilla.org/2021/01/analyzing-bugzilla-testcases-with-bugmon/>`_ - `Source <https://github.com/MozillaSecurity/bugmon>`_
* `Mozregression <https://mozilla.github.io/mozregression/>`_ - `Source <https://github.com/mozilla/mozregression>`_
|
