initial commit

2 files changed, 504 insertions, 0 deletions

diff --git a/files/it/mozilla/qa/bug_writing_lineeguida/index.html b/files/it/mozilla/qa/bug_writing_lineeguida/index.html
new file mode 100644
index 0000000000..31eca62c6d
--- /dev/null
+++ b/files/it/mozilla/qa/bug_writing_lineeguida/index.html
@@ -0,0 +1,253 @@
+---
+title: Linee guida per la segnalazione dei Bug
+slug: Mozilla/QA/Bug_writing_lineeguida
+translation_of: Mozilla/QA/Bug_writing_guidelines
+---
+<div class="note">
+<p><strong>Se avete bisogno di aiuto con i software Mozilla (per esempio con Firefox, Seamonkey o Thunderbird), usate una delle <a href="http://www.mozilla.org/support/">support options</a> disponibili.</strong> Non modifcate questa pagina!</p>
+</div>
+
+<p><span class="seoSummary">Questa pagina da per scontato che vogliate contribuire al progetto Mozilla raccogliendo abbastanza informazioni per poter caricare un bug report utile, nel sistema di bug tracking di Mozilla.</span> Grazie!</p>
+
+<p>Se siete nuovi nella segnalazione dei bug, potreste voler provare ad ottenere aiuto da i contributori di maggior esperienza. Controllate la sezione Community nella pagina  <a href="/en-US/docs/QA">QA</a> (Question and Answers - Domande e risposte) per avere indicazioni. Se vi accingete a segnalare un bug  Firefox, potete anche ottenere assistenza nel canale <span style="font-family: monospace;">#firefox</span> su <a href="irc://irc.mozilla.org/firefox">irc.mozilla.org</a>. Per altri progetti (es., Thunderbird, SeaMonkey) potete trovare  il canale appropriato su <a href="https://wiki.mozilla.org/IRC">IRC</a>.</p>
+
+<h2 id="Come_segnalare_un_bug">Come segnalare un bug</h2>
+
+<h3 id="Aprite_un_nuovo_bug_report_per_ogni_problema!">Aprite un nuovo bug report per ogni problema!</h3>
+
+<p>Così verrà completato un flusso di correzione bug (bugfix) efficace per ogni  problema.</p>
+
+<h3 id="Altri_dettagli_cui_prestare_attenzione">Altri dettagli cui prestare attenzione</h3>
+
+<ol>
+ <li>Descrivere i <strong>passi per riprodurre il bug</strong>:
+
+  <ul>
+   <li>Se avete <a href="#Writing_precise_steps_to_reproduce">precisi passi per riprodurre </a>— ottimo! — siete sulla buona strada per segnalare un bug report utile.</li>
+   <li>Se riuscite a riprodurre occasionalmente, ma non a seguito di specifici passi, dovete  fornire <a href="#specific-types">ulteriori informazioni</a> perchè il bug report sia utile.</li>
+   <li>Se non riuscite a riprodurre il problema, probabilmente non è utile riportarlo, a meno che non riusciate a fornire informazioni univoche circa il suo verificarsi.</li>
+  </ul>
+ </li>
+ <li>assicuratevi che il vs software sia aggiornato. L'ideale sarebbe, testare il problema conuna versione in fase di sviluppo per vedere se il bug è stato già corretto (e.g. <a href="http://www.mozilla.com/en-US/firefox/channel/">Firefox Beta, Aurora</a>, o l'avanzatissima <a class="link-https" href="https://nightly.mozilla.org/">Nightly</a>).</li>
+ <li>Quando riportate un bug di Firefox, prima verificate se potete riprodurlo in un <a href="https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles">nuovo profilo Firefox</a>. Se il bug si verifica solo nel vostro profilo esistente, provate a identificare quali <a href="https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems">settings, extensions</a>, o <a href="https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data">files nel vostro profilo</a> sono necessari per riprodurre il bug.
+  <ul>
+   <li>Se il bug sembra "eclatante" (cioè ovviamente che affligge una larga porzione di utenti), <span id="result_box" lang="it"><span title="If the bug seems egregious (i.e. obviously affecting a large portion of users), there's probably something unusual about your setup that's a necessary part of the steps to reproduce the bug."> probabilmente c'è qualcosa di insolito nella configurazione che è una parte necessaria dei passaggi per riprodurre il bug. </span><span title="You have much better chances of figuring it out than a developer who does not have access to your system.
+    ">Hai molte più possibilità di capirlo rispetto a uno sviluppatore che non ha accesso al tuo sistema.</span></span></li>
+   <li><span lang="it"><span title="If the bug falls into one of specific types of bugs listed in a section below, it may still be useful even if you can't reproduce it in a new Firefox profile.
+
+">Se il bug rientra in uno dei<a href="https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines$translate?tolocale=it#specific-types"> tipi specifici di bug elencati in una sezione sottostante</a>, potrebbe comunque essere utile anche se non potete riprodurlo in un nuovo profilo Firefox.</span></span><br>
+     </li>
+  </ul>
+ </li>
+ <li><span lang="it"><span title="Open the Enter a new bug form, which will guide you through most of the bug reporting process:
+
+    ">Apri il modulo <a href="https://bugzilla.mozilla.org/enter_bug.cgi?format=guided">Inserisci un nuovo bug</a> </span></span> (<a class="link-https" href="https://bugzilla.mozilla.org/enter_bug.cgi?format=guided">Enter a new bug</a><span lang="it"><span title="Open the Enter a new bug form, which will guide you through most of the bug reporting process:
+
+    ">) che ti guiderà nella maggior parte del processo di segnalazione dei bug:</span></span>
+  <ul>
+   <li><span lang="it"><span title="Create a Bugzilla account if you don't have one already, select the product having the bug.
+    ">Crea un account Bugzilla se non ne hai già uno, seleziona il prodotto con il bug.</span></span></li>
+   <li><span lang="it"><span title="Enter a clear unique summary as described below;">Inserite un <strong>riassunto univoco chiaro</strong> (</span></span><strong>clear unique summary</strong>) come <a href="https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines$translate?tolocale=it#Writing_a_clear_summary">descritto nel seguito</a><span lang="it"><span title="Enter a clear unique summary as described below;">; </span><span title="check if the bug has already been reported (if you want to be more thorough, there's an advanced guide on screening duplicate bugs).
+    ">controlla se il bug è già stato segnalato (se vuoi essere più completo, c'è una guida avanzata sullo</span></span> <a href="https://developer.mozilla.org/en-US/docs/Screening_duplicate_bugs">screening dei bug duplicati</a><span lang="it"><span title="check if the bug has already been reported (if you want to be more thorough, there's an advanced guide on screening duplicate bugs).
+    ">).</span></span></li>
+   <li><span lang="it"><span title="Provide precise steps to reproduce, expected results and actual results as described in the following section.
+    ">Fornite <strong>passaggi precisi per riprodurre, risultati attesi</strong> e <strong>risultati effettivi</strong> come <a href="https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines$translate?tolocale=it#Writing_precise_steps_to_reproduce">descritto nella sezione seguente</a>.</span></span></li>
+   <li><span lang="it"><span title="Provide additional information (also described below), especially if you can't reproduce the bug in a new profile;">Fornite ulteriori informazioni (anche<a href="https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines$translate?tolocale=it#Providing_additional_information"> descritte di seguito</a>), soprattutto se non è possibile riprodurre il bug in un nuovo profilo; </span><span title="and/or by reporting a crash, memory usage, performance, regression bug;">e / o segnalando<strong> crash, utilizzo della memoria, prestazioni, bug di regressione</strong>; </span><span title="or if the problem is with a specific web site.
+
+">o se il problema è con un sito web specifico.</span></span></li>
+  </ul>
+ </li>
+ <li><span lang="it"><span title="If you have multiple issues, please file separate bug reports.">In caso di problemi multipli, si prega di presentare segnalazioni di bug separate.</span></span></li>
+</ol>
+
+<h2 id="Scrivere_un_riassunto_chiaro">Scrivere un riassunto chiaro</h2>
+
+<p>Come descrivereste il bug usando approssimativamente 10 parole? Questa è la prima parte del vostro bug report che un<span class="short_text" id="result_box" lang="it"><span> triager o uno sviluppatore vedrà.</span></span></p>
+
+<p>Un buon riassunto deve identificare il bug report in maniera rapida e chiara. Esso deve spiegare il problema, non suggerire la soluzione.</p>
+
+<ul>
+ <li>Bene: " <span class="short_text" id="result_box" lang="it"><span>L'annullamento di una finestra di dialogo Copia file provoca l'arresto anomalo di File Manager</span></span> "</li>
+ <li>Male: "Il Software va in crash"</li>
+</ul>
+
+<ul>
+ <li><span id="result_box" lang="it"><span>Bene: "Lo scorrimento della freccia giù non funziona in &lt;textarea&gt; in stile con overflow: nascosto"</span></span></li>
+ <li><span lang="it"><span>Male: "Il browser dovrebbe funzionare con il mio sito web"</span></span></li>
+</ul>
+
+<h2 id="Scrivere_passi_precisi_per_riprodurre">Scrivere passi precisi per riprodurre</h2>
+
+<p><span id="result_box" lang="it"><span>Come può uno sviluppatore riprodurre il bug sul proprio computer?</span><br>
+ <br>
+ <span>I passaggi per la riproduzione sono la parte più importante di qualsiasi segnalazione di bug.</span> <span>Se uno sviluppatore è in grado di riprodurre il bug, è molto probabile che il bug sia corretto.</span> <span>Se i passaggi non sono chiari, potrebbe non essere nemmeno possibile sapere se il bug è stato corretto.</span></span></p>
+
+<table class="standard-table">
+ <tbody>
+  <tr>
+   <th>Cosa includere in un bug report?</th>
+   <th>Bene (preciso) esempio</th>
+   <th>
+    <p>Cattivo (inpreciso)</p>
+   </th>
+  </tr>
+  <tr>
+   <td><span id="result_box" lang="it"><span>Indicare se è possibile riprodurre il bug a volontà, occasionalmente o per niente.</span></span></td>
+   <td>Posso riprodurlo eseguendo i passi seguenti:</td>
+   <td> </td>
+  </tr>
+  <tr>
+   <td>
+    <p><span id="result_box" lang="it"><span>Descrivi il tuo metodo di interazione con Firefox oltre all'intento di ogni passaggio.</span></span></p>
+   </td>
+   <td>
+    <p><span id="result_box" lang="it"><span>1. Avvia Firefox facendo clic sull'icona del desktop</span><br>
+     <span>2. Premere Cmd + N (o Ctrl + N per utenti Windows) per aprire una nuova finestra del browser</span><br>
+     <span>3. Incolla </span></span><a class="link-https" href="https://mail.google.com/" rel="freelink">https://mail.google.com/</a> nella barra degli indirizzi e premere Invio</p>
+   </td>
+   <td>Apri Gmail in un'altra finestra</td>
+  </tr>
+  <tr>
+   <td>
+    <p><span id="result_box" lang="it"><span>Dopo i passaggi, descrivere con precisione il <strong>risultato</strong> (<strong>effettivo) osservato</strong> e il <strong>risultato atteso</strong>.</span> <span>Separare chiaramente i fatti (osservazioni) dalle speculazioni.</span></span></p>
+   </td>
+   <td><span id="result_box" lang="it"><span><strong>Risultati previsti</strong>: la mia Posta in arrivo viene visualizzata correttamente.</span><br>
+    <span><strong>Risultati effettivi</strong>: nella mia Posta in arrivo viene visualizzato il messaggio "Il browser non supporta i cookie (errore -91)".</span></span></td>
+   <td>
+    <p>"Non funziona"</p>
+
+    <p>"La pagina è mostrata non correttamente"</p>
+   </td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Providing_additional_information">Providing additional information</h2>
+
+<p>The following information is requested for most bug reports. You can save time by providing this information below the Expected results. If you need to attach multiple files, you can do so after submitting the report.</p>
+
+<h3 id="For_specific_types_of_bugs"><a name="specific-types">For specific types of bugs</a></h3>
+
+<p>If you are reporting a <strong>crash bug</strong>, please <a href="/en-US/docs/How_to_get_a_stacktrace_for_a_bug_report">include a Breakpad ID or attach stack trace</a>, and include the crash signature in the bug summary as well as in the <strong>Crash Signature</strong> field.</p>
+
+<p>If you are reporting a <strong>memory use or leak bug</strong>, please <a href="/en-US/docs/Mozilla/Performance/about:memory">attach the output of about:memory</a>. Ideally, find steps to reproduce an increase in what is shown in about:memory (even after clicking the "Minimize memory usage" button at the bottom). If you have trouble finding steps to reproduce, try the Firefox Support page titled <a href="https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram">Firefox Uses Too Much Memory (Ram) - How to Fix</a>. If you are a C++ developer, <a class="link-https" href="https://developer.mozilla.org/en-US/docs/Mozilla/Performance">more precise tools are available</a>.</p>
+
+<p>If you are reporting a <strong>bug about slowness or high CPU usage</strong>, please <a href="/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem">provide a link to the performance profile in the bug</a>.</p>
+
+<p>If you are reporting a <strong>hang</strong> (beachball on OS X or "not responding" on Windows), please follow the instructions in <a href="/en-US/docs/How_to_Report_a_Hung_Firefox">How to Report a Hung Firefox</a>.</p>
+
+<p>If you are reporting a bug involving a <strong>Flash hang</strong>, please visit <a href="https://wiki.mozilla.org/Flash/Hang_Debugging">https://wiki.mozilla.org/Flash/Hang_Debugging</a> to learn how to provide useful information for developers.</p>
+
+<p>If you are reporting a <strong>bug involving a specific web page</strong>, please try to make a <a href="/en-US/docs/Reducing_testcases">reduced testcase</a> and attach it to the bug report. If you don't have time or expertise, please report the issue to <a href="https://webcompat.com/">webcompat.com</a> instead, where our volunteers will do this for you.</p>
+
+<p>If the bug was <strong>recently introduced</strong>, finding a <a href="http://mozilla.github.io/mozregression/quickstart.html">regression window</a> can help identify the cause of the bug.</p>
+
+<p><a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html#intermittent">What if my bug seems "random" or "intermittent"?</a></p>
+
+<h3 id="For_most_Firefox_bugs">For most Firefox bugs</h3>
+
+<p>You should provide the following information for most Firefox bugs.</p>
+
+<table class="standard-table">
+ <tbody>
+  <tr>
+   <th>What should you include in a bug report?</th>
+   <th>Example</th>
+  </tr>
+  <tr>
+   <td>Indicate if the problem can be reproduced using a <a href="https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles">new Firefox profile</a> and any changes you need to make in order to reproduce.</td>
+   <td>The problem can be reproduced in a new profile, but only if Preferences -&gt; Privacy &amp; Security -&gt; Tracking Protection is selected.</td>
+  </tr>
+  <tr>
+   <td>If you can only reproduce with an existing profile try to figure out what <a href="https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems">settings, extensions</a>, or <a href="https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data">files in your profile</a> are needed to reproduce the bug. If you skip the step, <a href="https://support.mozilla.org/en-US/kb/use-troubleshooting-information-page-fix-firefox">save the troubleshooting information from about:support</a> to a file and attach it to the bug report.</td>
+   <td>I can't reproduce in a new profile, about:support information from the offending profile is attached.</td>
+  </tr>
+  <tr>
+   <td>
+    <p>Indicate if the problem can be reproduced using the <a href="https://nightly.mozilla.org/">latest Nightly build</a>. Include the <strong>Build ID</strong> from <a href="https://support.mozilla.org/en-US/kb/use-troubleshooting-information-page-fix-firefox">about:support</a>.</p>
+
+    <p>If possible, test using the new Firefox profile you created. If you need to test the Nightly build with your regular profile, you might want to <a href="https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles">back up the profile</a> first, since the pre-release build may corrupt your data.</p>
+   </td>
+   <td>The problem can be reproduced on the latest Nightly (Build ID 20170416100136).</td>
+  </tr>
+ </tbody>
+</table>
+
+<p> </p>
+
+<div class="originaldocinfo">
+<h2 id="Original_document_information">Original document information</h2>
+
+<ul>
+ <li>Author(s): Jesse Ruderman, Gervase Markham</li>
+ <li>Other Contributors: Eli Goldberg, Claudius Gayle, Jan Leger, Felix Miata, Peter Mock, Chris Pratt, Chris Yeh, and others.</li>
+</ul>
+</div>
+
+<p> </p>
+
+<hr>
+<h2 id="Advanced">Advanced</h2>
+
+<h3 id="Finding_the_correct_product_and_component" name="Finding_the_correct_product_and_component"><strong style="font-weight: bold;">Finding the correct product and component</strong></h3>
+
+<p>You will be asked to categorize your bug into a "product" and a "component" within that product, in order to direct your report to the correct developers.</p>
+
+<p>If you're using Firefox, the bug is most likely in "Firefox", "Toolkit", or "Core".</p>
+
+<ul>
+ <li><a class="link-https" href="https://bugzilla.mozilla.org/describecomponents.cgi?product=Firefox">List of components in the "Firefox" product</a> - Most parts of Firefox that you interact with directly</li>
+ <li><a class="link-https" href="https://bugzilla.mozilla.org/describecomponents.cgi?product=Toolkit">List of components in the "Toolkit" product</a> - Interface widgets and some frontend features</li>
+ <li><a class="link-https" href="https://bugzilla.mozilla.org/describecomponents.cgi?product=Core">List of components in the "Core" product</a> - Web page rendering, networking, etc.</li>
+</ul>
+
+<p>When in doubt, search for similar bugs and see which component they are in.</p>
+
+<p>If none of the components seem appropriate, look for a "General" component in the most appropriate product.</p>
+
+<h3 id="General_Outline_of_a_Bug_Report">General Outline of a Bug Report</h3>
+
+<div class="note">
+<p>Most of the following article has been merged into this page from QMO: How to write a proper bug</p>
+</div>
+
+<ul>
+ <li><strong>Summary</strong>: How would you describe the bug in less than 60 characters? It should quickly and uniquely identify a bug report as well as explain the problem, not your suggested solution. Good: "Canceling a File Copy dialog crashes File Manager" Bad: "Software crashes" Bad: "Browser should work with my web site"</li>
+ <li><strong>Component</strong>: In which sub-part of the software does it exist? This field is a requirement to submit any bug report. Click the word "Component" to see a description of each component. If none seems appropriate, highlight the "General" component.</li>
+ <li><a name="version"> </a><strong>Version</strong>: select the earliest Version with what the problem can be reproduced:
+  <ul>
+   <li>Developers will use that information to narrow down the commit what introduced a regression</li>
+   <li>QA staff needs that information to distinguish bugs with similar symptoms, but different roots.
+    <ul>
+     <li>Bugs that definitively appeared in different <em>Product</em> <em>Versions</em> probably will have different roots</li>
+     <li>But Bugs that started with the same <em>Product</em> <em>Version</em> probably are DUPLICATEs</li>
+    </ul>
+   </li>
+   <li><em>Trunk</em> does not allow any useful query. We have <em>Trunk</em> version bugs from beginning of the project until today, no common characteristics at all what can be tagged with this version. Avoid Trunk, replace it by precise information with what version the problem appeared if you can.</li>
+  </ul>
+ </li>
+ <li><strong>OS</strong>: On which operating system (OS) did you find it? (E.g. Linux, Windows, and Mac.) Example: "<em>If you know the bug happens on more than one type of operating system, choose "All". If your OS isn't listed, choose Other".</em></li>
+ <li><strong>Description</strong>: The details of your problem report, including:
+  <ul>
+   <li><u>Overview</u>: This is a larger detailed restatement of the summary. An example would be: <em>"Drag-selecting any page crashes Mac builds in the NSGetFactory function"</em>.</li>
+   <li><u>Build Id</u>: To find this either go to the "about:support" page via the location bar or, if you have MozQA's <a href="https://addons.mozilla.org/en-US/firefox/addon/nightly-tester-tools/">Nightly Tester Tools</a> extension, then go to Tools | Nightly Tester Tools and select the option that contains the output of the build Id. It should look something like this: <em>"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Firefox/38.0 ID:20150330004006 CSet: 9e57e9776571"</em>.</li>
+   <li><u>Additional Builds and Platforms</u>: Whether or not the bug takes place on other platforms (or browsers, if applicable). It should look something like this: <em>"Doesn't Occur On Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Firefox/38.0 ID:20150330004006 CSet: 9e57e9776571"</em>.</li>
+  </ul>
+ </li>
+ <li><strong>Steps to Reproduce</strong>: Minimized, easy-to-follow steps that will trigger the bug. If they're necessary, make sure to include any special setup steps. A good example of this would look like the following:<br>
+  1) View any web page. (I used the default sample page, http://www.google.com/).<br>
+  2) Drag-select the page. Specifically, while holding down the mouse button, drag the mouse pointer downwards from any point in the browser's content region to the bottom of the browser's content region.</li>
+ <li><strong>Actual Results</strong>: What the application did after performing the above steps. An example would be: <em>The application crashed.</em></li>
+ <li><strong>Expected Results</strong>: What the application should have done, were the bug not present. An example would be: <em>The window should scroll downwards. Scrolled content should be selected. Or, at least, the application should not crash.</em></li>
+</ul>
+
+<p> </p>
+
+<div class="originaldocinfo">
+<h4 id="Original_document_information_2">Original document information</h4>
+
+<ul>
+ <li>Author(s): Aakash Desai</li>
+ <li>Date last modified: June 3, 2013 at 2:41 am PST</li>
+</ul>
+</div>
diff --git a/files/it/mozilla/qa/index.html b/files/it/mozilla/qa/index.html
new file mode 100644
index 0000000000..99a8a38dd2
--- /dev/null
+++ b/files/it/mozilla/qa/index.html
@@ -0,0 +1,251 @@
+---
+title: 'QA: Quality assurance at Mozilla'
+slug: Mozilla/QA
+tags:
+  - Landing
+  - NeedsTranslation
+  - QA
+  - Testing
+  - TopicStub
+translation_of: Mozilla/QA
+---
+<p>The Mozilla Quality Assurance (QA) team drives software quality assurance activities across Mozilla and plays a key role in releasing a diverse range of software products on schedule. Within each project in Mozilla, we work to explore new features, write and execute tests, uncover and file bugs, build and maintain tools, collect and analyze metrics, and support the release world-class products that promote the open Web.</p>
+
+<p><span class="seoSummary">Here you'll find articles and tools to help you gear up to join the QA team testing Firefox to ensure that each release is as good as it can be.</span></p>
+
+<h2 id="Get_started">Get started</h2>
+
+<ul class="card-grid">
+ <li><span>How can I help test?</span>
+
+  <p>There are lots of ways for you to become a <a href="/en-US/docs/Mozilla/QA/How_can_I_help_test_">community contributor</a> to the Mozilla quality team.</p>
+ </li>
+ <li><span>Bugs</span>
+  <p>All Mozilla projects use <a href="https://bugzilla.mozilla.org/">Bugzilla</a> to track bugs. Learn how to <a href="/en-US/docs/Mozilla/QA/Bug_writing_guidelines" title="/en-US/docs/Mozilla/QA/Bug_writing_guidelines">report a bug</a> and get familiar with <a href="/en-US/docs/What_to_do_and_what_not_to_do_in_Bugzilla">what to do in Bugzilla</a>.</p>
+ </li>
+ <li><span>Events</span>
+  <p>Get involved in our weekly <a href="/en-US/docs/Mozilla/QA/Bug_Verification_Day">Bug Verification Day</a> or <a href="/en-US/docs/Mozilla/QA/Bug_Triage_Day">Bug Triage Day</a>. You may even <a href="/en-US/docs/Mozilla/QA/Organizing_a_Testday">organize a testday</a> for your local community!</p>
+ </li>
+ <li><span>IRC</span>
+  <p><a href="/en-US/docs/Mozilla/QA/Getting_Started_with_IRC">Get started with IRC</a>, the primary form of communication for members of the Mozilla community.</p>
+ </li>
+</ul>
+
+<h2 id="Bugs">Bugs</h2>
+
+<div class="row topicpage-table">
+<div class="section">
+<h3 id="Reporting_bugs">Reporting bugs</h3>
+
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/Bugzilla">Bugzilla</a></dt>
+ <dd>All Mozilla projects use <a href="https://bugzilla.mozilla.org/">Bugzilla</a> to track bugs. You will need to <a href="https://bugzilla.mozilla.org/createaccount.cgi">create an account with Bugzilla</a> in order to report bugs and triage them.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Bug_writing_guidelines" title="/en-US/docs/Mozilla/QA/Bug_writing_guidelines">Bug writing guidelines</a></dt>
+ <dd>The more effectively a bug is reported, the more likely that an engineer will actually fix it. By following these guidelines, you can help ensure that your bugs stay at the top of the Mozilla engineers' heap, and get fixed.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/A_Bugs_Life" title="/en-US/docs/Mozilla/QA/A_Bugs_Life">A Bug's Life</a></dt>
+ <dd>This tutorial will give an overview of what happens in the states that a bug will go through as well as how it will go from one to the next within its total life. It also explains the meaning of flags/keywords used in QA.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Filing_Crash_Bugs">Filing Crash Bugs</a></dt>
+ <dd>This document lists guidelines and tips on how to file bug reports for crashes in a way that helps in debugging and fixing the reported issue.</dd>
+</dl>
+</div>
+
+<div class="section">
+<h3 id="Triaging_bugs">Triaging bugs</h3>
+
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/QA/Confirming_unconfirmed_bugs" title="en-US/docs/Confirming unconfirmed bugs">Confirming unconfirmed bugs</a></dt>
+ <dd>Identify useful bug reports and close the rest.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox" title="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox">Triaging Bugs for Firefox</a></dt>
+ <dd>Information about the entire bug triaging process – from processing incoming bugs to narrowing down the steps to reproducing bugs.</dd>
+ <dt><a href="/en-US/docs/Screening_duplicate_bugs">Screening duplicate bugs</a></dt>
+ <dd>Help get bugs fixed faster by screening incoming reports for duplicates.</dd>
+ <dt><a href="/en-US/docs/What_to_do_and_what_not_to_do_in_Bugzilla">General Guidelines</a></dt>
+ <dd>What to do and what not to do in Bugzilla.</dd>
+</dl>
+</div>
+</div>
+
+<hr>
+<h2 id="Manual_testing">Manual testing</h2>
+
+<div class="row topicpage-table">
+<div class="section">
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/QA/Test_Case_Writing_Primer">Manual Test Case Writing Primer</a></dt>
+ <dd>How to write proper manual test cases</dd>
+</dl>
+</div>
+
+<div class="section">
+<dl>
+ <dt><a href="https://testrail.stage.mozaws.net/">TestRail</a></dt>
+ <dd>Mozilla QA's manual test cases reside in TestRail. You will need an LDAP account in order to login and execute test cases. Learn more on the <a href="https://wiki.mozilla.org/TestEngineering/Testrail">TestRail wiki page</a>.</dd>
+</dl>
+</div>
+</div>
+
+<hr>
+<h2 id="Automated_testing">Automated testing</h2>
+
+<div class="row topicpage-table">
+<div class="section">
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/QA/Automated_testing" title="/en-US/docs/Mozilla/QA/Automated_testing">Automated testing at Mozilla</a></dt>
+ <dd>Documentation about creating and using automated tests for Mozilla code.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Running_automated_tests">Running automated tests</a></dt>
+ <dd>
+ <p>This page lists the steps required to run Mozilla's automated test suites.</p>
+ </dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Developing_tests" title="en-US/docs/Developing_Tests">Developing tests</a></dt>
+ <dd>Ensure that future changes to Mozilla don't break things that currently work correctly.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Avoiding_intermittent_oranges" title="en-US/docs/QA/Avoiding intermittent oranges">Avoiding intermittent test failures</a></dt>
+ <dd>Suggestions for ways to make your tests more reliable, thereby helping to avoid random, intermittent test failures.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Test_Verification">Test Verification</a></dt>
+ <dd>When a changeset adds a new test, or modifies an existing test, the test verification (TV) test suite performs additional testing to help find intermittent failures in the modified test as quickly as possible.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Mozharness_FAQ">Mozharness FAQ</a></dt>
+ <dd>Answers to common questions about Mozharness.</dd>
+</dl>
+</div>
+
+<div class="section">
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/QA/Robocop" title="/en-US/docs/Mozilla/QA/Robocop">Robocop</a></dt>
+ <dd>Robocop is the automated testing system used for Firefox for Android. Learn its <a href="/en-US/docs/Mozilla/QA/Robocop/Code_style_guidelines">code style guidelines</a></dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Marionette">Marionette</a></dt>
+ <dd>Get started with Marionette UI testing.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/web-platform-tests">web-platform-tests</a></dt>
+ <dd>Learn how to use the industry standard, cross-browser, cross-platform <a href="http://testthewebforward.org/docs/">Web runtime testing system</a> from the <a href="https://www.w3.org/">W3C</a> used by Mozilla and others to ensure browser interoperability.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/external-media-tests">External Media Tests</a></dt>
+ <dd>Get started testing HTML5-based video elements using VideoPuppeteer, a <a href="/en-US/docs/Mozilla/QA/Marionette">Marionette</a>- -based test suite used to test sites like YouTube and Netflix.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Chrome_tests">Chrome tests</a></dt>
+ <dd>A chrome test is basically a <a href="https://developer.mozilla.org/en-US/docs/Mochitest" title="en/Mochitest">Mochitest</a> running with chrome privileges.</dd>
+</dl>
+</div>
+</div>
+
+<hr>
+<h2 id="Firefox_QE">Firefox QE</h2>
+
+<div class="row topicpage-table">
+<div class="section">
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox" title="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox">Triaging Bugs for Firefox</a></dt>
+ <dd>Information about the entire bug triaging process – from processing incoming bugs to narrowing down the steps to reproduce a bug.</dd>
+</dl>
+
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/QA/Tips_and_Tricks">Tips and Tricks</a></dt>
+ <dd>These tips and tricks will make your life easier when you are testing.</dd>
+</dl>
+<a href="/en-US/docs/Downloading_Nightly_or_Trunk_Builds">Downloading Nightly or Trunk Builds</a>
+
+<dl>
+ <dd>Every 24 hours, a "nightly" build is created that testers all over the world download and test, reporting as they go along on any bugs that hit them. </dd>
+</dl>
+</div>
+
+<div class="section">
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/Command_Line_Options">Command Line Options</a></dt>
+ <dd>Command line options are used to specify various startup options for Firefox.</dd>
+ <dt><a href="/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem">Reporting a Performance Problem</a></dt>
+ <dd>This article will guide you in reporting a performance problem using the <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler">Gecko Profiler extension</a>.</dd>
+ <dt><a href="/en-US/docs/Mozilla/Projects/Crash_reporting">Crash reporting</a></dt>
+ <dd>Firefox ships with an open-source crash reporting system.</dd>
+</dl>
+</div>
+</div>
+
+<hr>
+<h2 id="Firefox_for_Android">Firefox for Android</h2>
+
+<div class="row topicpage-table">
+<div class="section">
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/QA/Mobile_Firefox">Mobile Firefox</a></dt>
+ <dd>Firefox for Android is the mobile version of Firefox with a native Android look and feel.</dd>
+ <dt><a href="/en-US/Firefox_for_Android/Compatibility_Testing">Compatibility Testing</a></dt>
+ <dd>Help us identify websites that do not work well in Firefox by reporting the specific issues that you find in your investigation.</dd>
+</dl>
+</div>
+
+<div class="section">
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/QA/Fennec_Android:_Logging_with_the_Android_Debug_and_Logcat">Logging with the Android Debug Bridge and Logcat</a></dt>
+ <dd>This article will provide a walkthrough in downloading and setting up an environment to which one can gain access to and view Android system logs.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Firefox_Mobile:_Enabling_the_Error_Console">Enabling the Error Console</a></dt>
+ <dd>See the Mozilla Hacks article on <a class="external external-icon" href="https://hacks.mozilla.org/2012/08/remote-debugging-on-firefox-for-android/">Remote Debugging on Firefox for Android</a> for web content. If you need to debug the Firefox browser itself use Android's <a class="external external-icon" href="http://developer.android.com/tools/help/logcat.html">adb logcat</a>.</dd>
+</dl>
+</div>
+</div>
+
+<hr>
+<h2 id="Firefox_OS">Firefox OS</h2>
+
+<div class="row topicpage-table">
+<div class="section">
+<h3 id="Manual_testing_2">Manual testing</h3>
+
+<dl>
+ <dt><a href="/en-US/Firefox_OS/Simulator_vs_Emulator_vs_Device">Simulator vs Emulator vs Device</a></dt>
+ <dd>These are three basic options when it comes to getting a Firefox OS environment in order to work on, or developing for, Firefox OS.</dd>
+ <dt><a href="/en-US/Firefox_OS/Debugging">Debugging</a></dt>
+ <dd>Discover the different tools at your disposal to debug your Firefox OS code.</dd>
+ <dt><a href="/en-US/Firefox_OS/Developing_Firefox_OS/Filing_bugs_against_Firefox_OS">Reporting Bugs</a></dt>
+ <dd>This article provides a guide to filing bugs against the Firefox OS project, including Gaia and B2G.</dd>
+</dl>
+</div>
+
+<div class="section">
+<h3 id="Platform_(Gecko)">Platform (Gecko)</h3>
+
+<dl>
+ <dt><a href="/en-US/Firefox_OS/Platform/Automated_testing">Automated Testing</a></dt>
+ <dd>Learn various aspects of testing Firefox OS, including running different tests, automation, and result reporting and tracking.</dd>
+ <dt><a href="/en-US/Firefox_OS/Platform/Automated_testing/Gaia_performance_tests">Gaia Performance Tests</a></dt>
+ <dd>This article provides information about running performance tests on Gaia, as well as how to create new tests.</dd>
+ <dt><a href="/en-US/Firefox_OS/Platform/Feature_support_chart">Feature Support Chart</a></dt>
+ <dd>There are several different builds of Firefox OS you can download or build for yourself, and there are some differences between the types of features available on each device.</dd>
+</dl>
+</div>
+</div>
+
+<hr>
+<h2 id="Web_QA">Web QA</h2>
+
+<div class="row topicpage-table">
+<div class="section">
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/QA/Reducing_testcases" title="en-US/docs/Reducing testcases">Reducing testcases</a></dt>
+ <dd>Improve bug reports by turning broken web pages into simple testcases, which can help developers understand the bug and can also be used for creating automated tests.</dd>
+ <dt><a href="/en-US/docs/Mozilla/QA/Managing_Web_QA_XFails">Managing XFails</a></dt>
+ <dd>One of the ongoing tasks of the Web QA department is managing xfails. This document will explain what xfails are, and describe the steps one can take to investigate and update them.</dd>
+</dl>
+</div>
+
+<div class="section">
+<dl>
+ <dt><a href="/en-US/docs/Mozilla/QA/Running_Web_QA_automated_tests">Running Automated Tests</a></dt>
+ <dd>So you’re interested in contributing to Mozilla Web QA automation projects but don’t know where to start? This doc will help you get up and running a set of tests locally.</dd>
+</dl>
+</div>
+</div>
+
+<hr>
+<h2 id="Glossary">Glossary</h2>
+
+<div class="section">
+<dl>
+ <dt><a href="/en-US/docs/Glossary/Smoke_Test">Smoke Test</a></dt>
+ <dd></dd>
+</dl>
+</div>
+
+<h2 id="See_also">See also</h2>
+
+<ul>
+ <li><a href="https://lists.mozilla.org/listinfo/dev-quality">Mailing list</a></li>
+ <li><a href="https://quality.mozilla.org/">Blog</a></li>
+ <li><a href="/en-US/docs/tag/QA" title="en-US/docs/tag/QA">View all documents tagged QA</a></li>
+ <li><a href="/en-US/docs/tag/QA:Tools" title="en-US/docs/tag/QA:Tools">View all documents tagged QA:Tools</a></li>
+</ul>