| |
@@ -1,6 +1,8 @@
|
| |
import React, { useState } from "react"
|
| |
+ import ReactDOMServer from "react-dom/server"
|
| |
import { Modal, ModalHeader, ModalBody, ModalFooter } from "reactstrap"
|
| |
import { CollapsableCard, ModalBadge } from "./components"
|
| |
+ import { Trans, useTranslation } from "react-i18next"
|
| |
|
| |
export default (props) => {
|
| |
let sections = Object.keys(props.data).map((k) => (
|
| |
@@ -22,6 +24,7 @@
|
| |
}
|
| |
|
| |
export function FedoraManualTestingItemsListSub1(props) {
|
| |
+ const { t } = useTranslation()
|
| |
var subsections = Object.keys(props.data).map((k) => (
|
| |
<li key={"li" + k}>
|
| |
<span>{k}</span>
|
| |
@@ -35,64 +38,72 @@
|
| |
case "Installation":
|
| |
l1 = (
|
| |
<div>
|
| |
- The <strong>Installation</strong> testcases generally deal with a part of the
|
| |
- installation procedure.
|
| |
- <br />
|
| |
- You will certainly need an installation ISO, and either a Virtual or Bare-metal machine
|
| |
- to run the test.
|
| |
- <br />
|
| |
- <i>Note:</i> some (not that many, though) of these testcases require Bare-metal machine.
|
| |
- Be sure to read the Description of the testcase carefully.
|
| |
+ <Trans i18nKey="Installation_text">
|
| |
+ The <strong>Installation</strong> testcases generally deal with a part of the
|
| |
+ installation procedure. You will certainly need an installation ISO, and either a
|
| |
+ Virtual or Bare-metal machine to run the test.
|
| |
+ <br />
|
| |
+ <i>Note:</i> some (not that many, though) of these testcases require Bare-metal
|
| |
+ machine. Be sure to read the Description of the testcase carefully.
|
| |
+ </Trans>
|
| |
</div>
|
| |
)
|
| |
break
|
| |
case "Desktop":
|
| |
l1 = (
|
| |
<div>
|
| |
- The <strong>Desktop</strong> testcases cover basic functionality of the desktop
|
| |
- environment.
|
| |
- <br />
|
| |
- You can either install Fedora onto clean Virtual or Bare-metal machine, or use a Live
|
| |
- image instead.
|
| |
+ <Trans i18nKey="Desktop_Text">
|
| |
+ The <strong>Desktop</strong> testcases cover basic functionality of the desktop
|
| |
+ environment.
|
| |
+ <br />
|
| |
+ You can either install Fedora onto clean Virtual or Bare-metal machine, or use a Live
|
| |
+ image instead.
|
| |
+ </Trans>
|
| |
</div>
|
| |
)
|
| |
break
|
| |
case "Base":
|
| |
l1 = (
|
| |
<div>
|
| |
- The <strong>Base</strong> testcases cover the system's basic functionality just
|
| |
- after a clean installation.
|
| |
- <br />
|
| |
- Most times, you will be asked to perform a clean Fedora installation. You can use either
|
| |
- Virtual or Bare-metal machine.
|
| |
- <br />
|
| |
- <i>Pro tip:</i> using a snapshot of cleanly installed Virtual machine is just fine. No
|
| |
- need to reinstall for every testcase.
|
| |
+ <Trans i18nKey="Base_Text">
|
| |
+ The <strong>Base</strong> testcases cover the system's basic functionality just
|
| |
+ after a clean installation.
|
| |
+ <br />
|
| |
+ Most times, you will be asked to perform a clean Fedora installation. You can use
|
| |
+ either Virtual or Bare-metal machine.
|
| |
+ <br />
|
| |
+ <i>Pro tip:</i> using a snapshot of cleanly installed Virtual machine is just fine. No
|
| |
+ need to reinstall for every testcase.
|
| |
+ </Trans>
|
| |
</div>
|
| |
)
|
| |
break
|
| |
case "Server":
|
| |
l1 = (
|
| |
<div>
|
| |
- The <strong>Server</strong> testcases usually require multiple machines to test the
|
| |
- server-client behaviour, and might feel a bit advanced.
|
| |
+ <Trans i18nKey="Server_Text">
|
| |
+ The <strong>Server</strong> testcases usually require multiple machines to test the
|
| |
+ server-client behaviour, and might feel a bit advanced.
|
| |
+ </Trans>
|
| |
</div>
|
| |
)
|
| |
break
|
| |
case "Cloud":
|
| |
l1 = (
|
| |
<div>
|
| |
- Even thought the <strong>Cloud</strong> testcases are best done in the specific
|
| |
- environments like EC2 or Openstack, you can also perform them locally using Testcloud.
|
| |
- <br />
|
| |
- Have a look at the{" "}
|
| |
- <a
|
| |
- target="_blank"
|
| |
- rel="noopener noreferrer"
|
| |
- href="https://fedoraproject.org/wiki/Test_Results:Fedora_Current_Cloud#Cloud_Provider_Setup">
|
| |
- Cloud provider setup
|
| |
- </a>{" "}
|
| |
- guides for more details.
|
| |
+ <Trans i18nKey="Cloud_Text">
|
| |
+ Even thought the <strong>Cloud</strong> testcases are best done in the specific
|
| |
+ environments like EC2 or Openstack, you can also perform them locally using Testcloud.
|
| |
+ <br />
|
| |
+ Have a look at the{" "}
|
| |
+ <a
|
| |
+ target="_blank"
|
| |
+ rel="noopener noreferrer"
|
| |
+ href="https://fedoraproject.org/wiki/Test_Results:Fedora_Current_Cloud#Cloud_Provider_Setup">
|
| |
+ Cloud provider setup
|
| |
+ </a>{" "}
|
| |
+ guides for more details.
|
| |
+ </Trans>
|
| |
</div>
|
| |
)
|
| |
break
|
| |
@@ -101,7 +112,7 @@
|
| |
}
|
| |
|
| |
return (
|
| |
- <CollapsableCard title={l1} expand_text="See" expand_class="primary">
|
| |
+ <CollapsableCard title={l1} expand_text={t("See")} expand_class="primary">
|
| |
{subsections}
|
| |
</CollapsableCard>
|
| |
)
|
| |
@@ -115,32 +126,34 @@
|
| |
|
| |
const matrix_url = extra_data.matrix_url
|
| |
var environment_examples = undefined
|
| |
+ const { t } = useTranslation()
|
| |
switch (extra_data.testtype) {
|
| |
case "Installation":
|
| |
environment_examples = (
|
| |
<span>
|
| |
- <code>x86_64</code> or <code>ARM</code>
|
| |
+ <code>x86_64</code> {t("or")} <code>ARM</code>
|
| |
</span>
|
| |
)
|
| |
break
|
| |
case "Base":
|
| |
environment_examples = (
|
| |
<span>
|
| |
- <code>Workstation</code>, <code>Server</code>, <code>Xfce</code> or <code>Minimal</code>
|
| |
+ <code>Workstation</code>, <code>Server</code>, <code>{t("or")}</code> or{" "}
|
| |
+ <code>Minimal</code>
|
| |
</span>
|
| |
)
|
| |
break
|
| |
case "Desktop":
|
| |
environment_examples = (
|
| |
<span>
|
| |
- <code>Workstation</code> or <code>KDE</code>
|
| |
+ <code>Workstation</code> {t("or")} <code>KDE</code>
|
| |
</span>
|
| |
)
|
| |
break
|
| |
case "Server":
|
| |
environment_examples = (
|
| |
<span>
|
| |
- <code>x86_64</code> or <code>aarch64</code>
|
| |
+ <code>x86_64</code> {t("or")} <code>aarch64</code>
|
| |
</span>
|
| |
)
|
| |
break
|
| |
@@ -149,62 +162,84 @@
|
| |
}
|
| |
|
| |
const testtype = extra_data.testtype
|
| |
-
|
| |
+ const length = extra_data.envs.length > 1 ? "environments are" : "environment is"
|
| |
+ const join = extra_data.envs.join(", ")
|
| |
+ const environment_variables = {__html: ReactDOMServer.renderToString(environment_examples)}
|
| |
+ const success_variables = {__html: ReactDOMServer.renderToString(<>{{result|pass|YOUR_NAME_HERE|}}</>) }
|
| |
+ const fail_variables = {__html: ReactDOMServer.renderToString(<>{{result|fail|YOUR_NAME_HERE|BUG_NUMBER|}}</>)}
|
| |
+
|
| |
return (
|
| |
<ModalInfo buttonLabel={name}>
|
| |
<ol className="steps">
|
| |
<li>
|
| |
- Identify the testcase and `environment` in our{" "}
|
| |
- <a target="_blank" rel="noopener noreferrer" href={matrix_url}>
|
| |
- Tescase matrix
|
| |
- </a>{" "}
|
| |
- <ModalBadge expand_text="Not sure what that means?">
|
| |
+ <Trans i18nKey="Identify_The_Testcase">
|
| |
+ Identify the testcase and `environment` in our{" "}
|
| |
+ <a target="_blank" rel="noopener noreferrer" href={matrix_url}>
|
| |
+ Tescase matrix{" "}
|
| |
+ </a>
|
| |
+ </Trans>
|
| |
+ <ModalBadge expand_text={t("Not_sure_what_that_means")}>
|
| |
<ul>
|
| |
<li>
|
| |
- Have a look at the matrix. The rows are the testcases, and the columns are the
|
| |
- environments. Most of the time, these are {environment_examples} for the {testtype}{" "}
|
| |
- testcases, but you can also encouter a generic <code>Result</code> column, which
|
| |
- usually means you can use any media/architecture available.
|
| |
+ <Trans i18nKey="Have_a_look_at_the_matrix">
|
| |
+ Have a look at the matrix. The rows are the testcases, and the columns are the
|
| |
+ environments. Most of the time, these are <span dangerouslySetInnerHTML={environment_variables}></span>
|
| |
+ for the {{ testtype }} testcases, but you can also encouter a generic{" "}
|
| |
+ <code>Result</code> column, which usually means you can use any
|
| |
+ media/architecture available.
|
| |
+ </Trans>
|
| |
</li>
|
| |
<li>
|
| |
- For this particular testcase, <code>{extra_data.envs.join(", ")}</code>{" "}
|
| |
- {extra_data.envs.length > 1 ? "environments are" : "environment is"} missing
|
| |
- results.
|
| |
+ <Trans i18nKey="for_this_particular">
|
| |
+ For this particular testcase, <code>{{ join }}</code> {{ length }} missing
|
| |
+ results.
|
| |
+ </Trans>
|
| |
</li>
|
| |
</ul>
|
| |
</ModalBadge>
|
| |
</li>
|
| |
|
| |
<li>
|
| |
- Read the{" "}
|
| |
- <a target="_blank" rel="noopener noreferrer" href={tc_url}>
|
| |
- Testcase
|
| |
- </a>{" "}
|
| |
- briefly, just to have a general idea of what you will be doing.{" "}
|
| |
- <ModalBadge expand_text="Not making much sense?">
|
| |
- The testcases are generally split into four sections:
|
| |
+ <Trans i18nKey="Read_the_TestCase">
|
| |
+ Read the{" "}
|
| |
+ <a target="_blank" rel="noopener noreferrer" href={tc_url}>
|
| |
+ Testcase
|
| |
+ </a>{" "}
|
| |
+ briefly, just to have a general idea of what you will be doing.
|
| |
+ </Trans>
|
| |
+ <ModalBadge expand_text={t("Not_making_much_sense")}>
|
| |
+ {t("The_testcases_are_generally_split_into_four_sections")}
|
| |
<ul>
|
| |
<li>
|
| |
- <strong>Description</strong> should give you a general idea of what is being tested
|
| |
+ <Trans i18nKey="Description_Text">
|
| |
+ <strong>Description</strong> should give you a general idea of what is being
|
| |
+ tested
|
| |
+ </Trans>
|
| |
</li>
|
| |
<li>
|
| |
- <strong>Setup</strong> describes the steps to take before you begin working on the
|
| |
- testcase
|
| |
+ <Trans i18nKey="Setup_Text">
|
| |
+ <strong>Setup</strong> describes the steps to take before you begin working on
|
| |
+ the testcase
|
| |
+ </Trans>
|
| |
</li>
|
| |
<li>
|
| |
- <strong>How to test</strong> contains the individual steps to take in order to
|
| |
- perform the testcase
|
| |
+ <Trans i18nKey="How_to_Test">
|
| |
+ <strong>How to test</strong> contains the individual steps to take in order to
|
| |
+ perform the testcase
|
| |
+ </Trans>
|
| |
</li>
|
| |
<li>
|
| |
- <strong>Expected results</strong> describe what you should check while testing in
|
| |
- order to decide whether it Passed of Failed
|
| |
+ <Trans i18nKey="Expected_Results">
|
| |
+ <strong>Expected results</strong> describe what you should check while testing in
|
| |
+ order to decide whether it Passed of Failed
|
| |
+ </Trans>
|
| |
</li>
|
| |
</ul>
|
| |
</ModalBadge>
|
| |
</li>
|
| |
|
| |
<li>
|
| |
- Based on the enviromnent, select and download and appropriate ISO{" "}
|
| |
+ {t("based_on_the")}{" "}
|
| |
<a
|
| |
target="_blank"
|
| |
rel="noopener noreferrer"
|
| |
@@ -212,26 +247,27 @@
|
| |
here
|
| |
</a>
|
| |
.{" "}
|
| |
- <ModalBadge expand_text="Not sure how?">
|
| |
+ <ModalBadge expand_text={t("Not_sure_how")}>
|
| |
<ul>
|
| |
+ <li>{t("Most_of_the_time")}</li>
|
| |
<li>
|
| |
- Most of the time Workstation Live, or Server DVD are fine, but sometimes there are
|
| |
- specific products (e.g. Xfce) to be tested
|
| |
- </li>
|
| |
- <li>
|
| |
- Make sure to read about identifying the environment above.{" "}
|
| |
- <ModalBadge expand_text="See">
|
| |
+ {t("Make_sure_to")}{" "}
|
| |
+ <ModalBadge expand_text={t("See")}>
|
| |
<ul>
|
| |
<li>
|
| |
- Have a look at the matrix. The rows are the testcases, and the columns are
|
| |
- the environments. Most of the time, these are {environment_examples} for the{" "}
|
| |
- {testtype} testcases, but you can also encouter a generic <code>Result</code>{" "}
|
| |
- column, which usually means you can use any media/architecture available.
|
| |
+ <Trans i18nKey="Have_a_look_at_the_matrix">
|
| |
+ Have a look at the matrix. The rows are the testcases, and the columns are the
|
| |
+ environments. Most of the time, these are <span dangerouslySetInnerHTML={environment_variables}></span>
|
| |
+ for the {{ testtype }} testcases, but you can also encouter a generic{" "}
|
| |
+ <code>Result</code> column, which usually means you can use any
|
| |
+ media/architecture available.
|
| |
+ </Trans>
|
| |
</li>
|
| |
<li>
|
| |
- For this particular testcase, <code>{extra_data.envs.join(", ")}</code>{" "}
|
| |
- {extra_data.envs.length > 1 ? "environments are" : "environment is"} missing
|
| |
- results.
|
| |
+ <Trans i18nKey="for_this_particular">
|
| |
+ For this particular testcase, <code>{{ join }}</code> {{ length }} missing
|
| |
+ results.
|
| |
+ </Trans>
|
| |
</li>
|
| |
</ul>
|
| |
</ModalBadge>
|
| |
@@ -241,107 +277,122 @@
|
| |
</li>
|
| |
|
| |
<li>
|
| |
- Study the{" "}
|
| |
- <a target="_blank" rel="noopener noreferrer" href={tc_url}>
|
| |
- Testcase
|
| |
- </a>{" "}
|
| |
- thoroughly, to be sure you know what to do.{" "}
|
| |
- <ModalBadge expand_text="Feeling a bit lost?">
|
| |
+ <Trans i18nKey="study_the_testcase">
|
| |
+ Study the{" "}
|
| |
+ <a target="_blank" rel="noopener noreferrer" href={tc_url}>
|
| |
+ Testcase
|
| |
+ </a>{" "}
|
| |
+ thoroughly, to be sure you know what to do.{" "}
|
| |
+ </Trans>
|
| |
+ <ModalBadge expand_text={t("Feeling_a_bit_lost")}>
|
| |
<ul>
|
| |
<li>
|
| |
- The testcase structure is not making sense?{" "}
|
| |
- <ModalBadge expand_text="Click here">
|
| |
- The testcases are generally split into four sections:
|
| |
+ {t("The_testcase_structure_is_not_making_sense")}{" "}
|
| |
+ <ModalBadge expand_text={t("See")}>
|
| |
+ {t("The_testcases_are_generally_split_into_four_sections")}
|
| |
<ul>
|
| |
<li>
|
| |
- <strong>Description</strong> should give you a general idea of what is being
|
| |
- tested
|
| |
+ <Trans i18nKey="Description_Text">
|
| |
+ <strong>Description</strong> should give you a general idea of what is
|
| |
+ being tested
|
| |
+ </Trans>
|
| |
</li>
|
| |
<li>
|
| |
- <strong>Setup</strong> describes the steps to take before you begin working
|
| |
- on the testcase
|
| |
+ <Trans i18nKey="Setup_Text">
|
| |
+ <strong>Setup</strong> describes the steps to take before you begin working
|
| |
+ on the testcase
|
| |
+ </Trans>
|
| |
</li>
|
| |
<li>
|
| |
- <strong>How to test</strong> contains the individual steps to take in order
|
| |
- to perform the testcase
|
| |
+ <Trans i18nKey="How_to_Test">
|
| |
+ <strong>How to test</strong> contains the individual steps to take in order
|
| |
+ to perform the testcase
|
| |
+ </Trans>
|
| |
</li>
|
| |
<li>
|
| |
- <strong>Expected results</strong> describe what you should check while
|
| |
- testing in order to decide whether it Passed of Failed
|
| |
+ <Trans i18nKey="Expected_Results">
|
| |
+ <strong>Expected results</strong> describe what you should check while
|
| |
+ testing in order to decide whether it Passed of Failed
|
| |
+ </Trans>
|
| |
</li>
|
| |
</ul>
|
| |
</ModalBadge>
|
| |
</li>
|
| |
<li>
|
| |
- Maybe you are stuck, or just do not understand something? Feel free to ask on our
|
| |
- IRC channel #fedora-qa at freenode.net{" "}
|
| |
- <ModalBadge expand_text="Don't have an IRC client?">
|
| |
- If you are not that familiar with IRC, you can use the{" "}
|
| |
- <a target="_blank" rel="noopener noreferrer" href="http://webchat.freenode.net">
|
| |
- web-interface
|
| |
- </a>{" "}
|
| |
- just enter a Nickname of your choice, #fedora-qa (including the hash sign) in the
|
| |
- Channels field, and click Connect.
|
| |
+ {t("Maybe_you_are_stuck")}{" "}
|
| |
+ <ModalBadge expand_text={t("dont_have_an")}>
|
| |
+ <Trans i18nKey="Have_a_look_at_the_matrix">
|
| |
+ Have a look at the matrix. The rows are the testcases, and the columns are the
|
| |
+ environments. Most of the time, these are <span dangerouslySetInnerHTML={environment_variables}></span>
|
| |
+ for the {{ testtype }} testcases, but you can also encouter a generic{" "}
|
| |
+ <code>Result</code> column, which usually means you can use any
|
| |
+ media/architecture available.
|
| |
+ </Trans>
|
| |
</ModalBadge>
|
| |
</li>
|
| |
</ul>
|
| |
</ModalBadge>
|
| |
</li>
|
| |
|
| |
- <li>Get your hands dirty, and test the hell out of it!</li>
|
| |
+ <li>{t("Get_your_hands")}</li>
|
| |
<li>
|
| |
- <ModalBadge expand_class="success" expand_text="Everything went well" type="btn">
|
| |
- Great! Either use <code>relval report-results</code> on command line (make sure to
|
| |
- install the <code>relval</code> package first), or modify the{" "}
|
| |
- <a target="_blank" rel="noopener noreferrer" href={matrix_url}>
|
| |
- matrix
|
| |
- </a>{" "}
|
| |
- directly by clicking on the <code>Edit</code> link next to the Matrice's header, and
|
| |
- put <code>{{result|pass|YOUR_NAME_HERE|}}</code> in the appropriate
|
| |
- spot.
|
| |
+ <ModalBadge
|
| |
+ expand_class="success"
|
| |
+ expand_text={t("Everything_went_well")}
|
| |
+ type="btn">
|
| |
+ <Trans
|
| |
+ i18nKey="Great_either_use"
|
| |
+ >
|
| |
+ Great! Either use <code>relval report-results</code> on command line (make sure to
|
| |
+ install the <code>relval</code> package first), or modify the{" "}
|
| |
+ <a target="_blank" rel="noopener noreferrer" href={matrix_url}>
|
| |
+ matrix
|
| |
+ </a>{" "}
|
| |
+ directly by clicking on the <code>Edit</code> link next to the Matrice's header, and
|
| |
+ put <code dangerouslySetInnerHTML={success_variables}></code> in the
|
| |
+ appropriate spot.
|
| |
+ </Trans>
|
| |
</ModalBadge>
|
| |
|
| |
- <ModalBadge expand_class="danger" expand_text="I found a bug!" type="btn">
|
| |
- Awesome! Ideally read up on https://fedoraproject.org/wiki/How_to_file_a_bug_report
|
| |
- <br />
|
| |
- If you don't feel like reading a wall of text, at least pot together a small document
|
| |
- containing:
|
| |
+ <ModalBadge expand_class="danger" expand_text={t("I_found_a_bug")} type="btn">
|
| |
+ <Trans i18nKey="Awesome_ideally_read">
|
| |
+ Awesome! Ideally read up on <a target="_blank" rel="noopener noreferrer" href="https://fedoraproject.org/wiki/How_to_file_a_bug_report">How_to_file_a_bug_report</a>
|
| |
+ <br />
|
| |
+ If you don't feel like reading a wall of text, at least pot together a small document
|
| |
+ containing:
|
| |
+ </Trans>
|
| |
<ul>
|
| |
+ <li>{t("brief_description_of_what")}</li>
|
| |
<li>
|
| |
- Brief description of what went wrong (e.g. "QA:Testcase_dualboot_with_windows -
|
| |
- Bootloader does not show the Windows option")
|
| |
+ {t("the_name_of")} (e.g. "Fedora-Server-netinst-i386-Rawhide-20181227.n.0.iso")
|
| |
</li>
|
| |
+ <li>{t("note_what_you_did")}</li>
|
| |
+ <li>{t("try_to_reproduce_the")}</li>
|
| |
<li>
|
| |
- The name of the ISO image you used (e.g.
|
| |
- "Fedora-Server-netinst-i386-Rawhide-20181227.n.0.iso")
|
| |
- </li>
|
| |
- <li>
|
| |
- Note what you did, as precisely as possible, in a step-by-step fashion. Even
|
| |
- details like "Chose Polish as the languae for the installation process" can matter.
|
| |
- </li>
|
| |
- <li>
|
| |
- Try to reproduce the same state again based on the steps above (you can also
|
| |
- experiment a bit, and try to come up with just the critical steps)
|
| |
- </li>
|
| |
- <li>
|
| |
- Share your notes on the internet (you can use fpaste), and ask for help with filing
|
| |
- the bug report on our IRC channel #fedora-qa at freenode.net{" "}
|
| |
- <ModalBadge expand_text="Don't have an IRC client?">
|
| |
- If you are not that familiar with IRC, you can use the web-interface[link] just
|
| |
- enter a Nickname of your choice, #fedora-qa (including the hash sign) in the
|
| |
- Channels field, and click Connect.
|
| |
- </ModalBadge>
|
| |
+ <Trans i18nKey="Share_your_notes">
|
| |
+ Share your notes on the internet (you can use fpaste), and ask for help with
|
| |
+ filing the bug report on our IRC channel #fedora-qa at freenode.net{" "}
|
| |
+ </Trans>
|
| |
+ <ModalBadge expand_text={t("dont_have_an")}>
|
| |
+ <Trans i18nKey="If_you_are_not_familiar">
|
| |
+ If you are not that familiar with IRC, you can use the <a target="_blank" rel="noopener noreferrer" noreferrer href="http://webchat.freenode.net">web-interface </a>
|
| |
+ just enter a Nickname of your choice, #fedora-qa (including the hash sign) in the Channels field, and click Connect
|
| |
+ </Trans>
|
| |
+ </ModalBadge>
|
| |
</li>
|
| |
</ul>
|
| |
- Once you get the Bug reported, make sure to also submit the result into the testing
|
| |
- matrix. Either use <code>relval report-results</code> on command line (make sure to
|
| |
- install the <code>relval</code> package first), or modify the{" "}
|
| |
- <a target="_blank" rel="noopener noreferrer" href={matrix_url}>
|
| |
- matrix
|
| |
- </a>{" "}
|
| |
- directly by clicking on the <code>Edit</code> link next to the Matrice's header, and
|
| |
- put <code>{{result|fail|YOUR_NAME_HERE|BUG_NUMBER|}}</code> in the
|
| |
- appropriate spot.
|
| |
+ <Trans
|
| |
+ i18nKey="Once_you_get_the_bug">
|
| |
+ Once you get the Bug reported, make sure to also submit the result into the testing
|
| |
+ matrix. Either use <code>relval report-results</code> on command line (make sure to
|
| |
+ install the <code>relval</code> package first), or modify the{" "}
|
| |
+ <a target="_blank" rel="noopener noreferrer" href={matrix_url}>
|
| |
+ matrix
|
| |
+ </a>{" "}
|
| |
+ directly by clicking on the <code>Edit</code> link next to the Matrice's header, and
|
| |
+ put <code dangerouslySetInnerHTML={fail_variables}></code> in
|
| |
+ the appropriate spot.
|
| |
+ </Trans>
|
| |
</ModalBadge>
|
| |
</li>
|
| |
</ol>
|
| |
@@ -362,7 +413,7 @@
|
| |
}
|
| |
|
| |
const project = props.buttonLabel.split(":")[0]
|
| |
- const ticket = props.buttonLabel.split(":")[1] //strip whitespace?
|
| |
+ const ticket = props.buttonLabel.split(":")[1]
|
| |
|
| |
return (
|
| |
<div>
|
| |
manishakanyal
commented 2 years ago
@lbrabec, the project is now translatable please have a look!