From c0f4022d7059b126b7aac1dbd752dd24069cfa7e Mon Sep 17 00:00:00 2001 From: Josef Skladanka Date: Jan 24 2019 16:56:39 +0000 Subject: fixed some wordings --- diff --git a/src/wizard/FedoraEasyKarma.js b/src/wizard/FedoraEasyKarma.js index e6b4a7a..844d18d 100644 --- a/src/wizard/FedoraEasyKarma.js +++ b/src/wizard/FedoraEasyKarma.js @@ -29,7 +29,8 @@ export default class FedoraEasyKarmaItemsList extends Component {
  • Make sure your system is up-to-date: sudo dnf update --refresh
  • Install fedora-easy-karma tool: sudo dnf install fedora-easy-karma
  • -
  • Choose an update to test{' '} +
  • + Choose an update to test{' '} Not sure how? Have a look at the available packages in updates-testing repo, by running dnf --enablerepo=updates-testing list --refresh --upgrades and choose a package you know. @@ -55,7 +56,7 @@ export default class FedoraEasyKarmaItemsList extends Component { New to fedora-easy-karma? It identifies the packages installed from the updates-testing repository, and matches them to the updates in Bodhi.
    - You are then presented with the relevant updates one-by-one, to submit Karma and a comment. + You are then presented with the relevant updates one-by-one, to submit Karma and a comment.{' '} Not sure what Karma means?
      @@ -66,7 +67,7 @@ export default class FedoraEasyKarmaItemsList extends Component { Still not sure? Just press Enter to skip it.
    1. - Add a comment - even if it works, try to describe what you tested. It can be as easy as I tried openning and editing a document, and it worked. when you test a text-editor, or I opened a couple of tabs, and browsed random pages for a web-browser.
      + Add a comment - even if it works, try to describe what you tested. It can be as easy as I tried openning and editing a document, and it worked. when you test a text-editor, or I opened a couple of tabs, and browsed random pages. for a web-browser.
      Absolutely make sure to provide reasonable amount of detail, when submitting negative karma - ideally, you should also create a bugreport, and reference it in the comment.
    diff --git a/src/wizard/FedoraManualTesting.js b/src/wizard/FedoraManualTesting.js index 5ee9630..6f25081 100644 --- a/src/wizard/FedoraManualTesting.js +++ b/src/wizard/FedoraManualTesting.js @@ -51,7 +51,7 @@ class FedoraManualTestingItemsListSub1 extends Component { ); break; case "Cloud": - l1 = (
    Even thought the Cloud testcases are best done in the specific environments like EC2 or Openstack, you can also perform + l1 = (
    Even thought the Cloud testcases are best done in the specific environments like EC2 or Openstack, you can also perform{' '} them locally using Testcloud.
    Have a look at the Cloud provider setup guides for more details.
    ); @@ -71,7 +71,7 @@ class FedoraManualTestingItemsListSub1 extends Component { {l1}
    @@ -119,12 +119,12 @@ class FedoraManualTestingItem extends Component {
    1. - Identify the testcase and `environment` in our Tescase matrix  - Not sure what that means? - + Identify the testcase and `environment` in our Tescase matrix{' '} + Not sure what that means? +
      • - 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, + 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 Result column.
      • @@ -135,9 +135,9 @@ class FedoraManualTestingItem extends Component {
      • - Read the Testcase briefly, just to have a general idea of what you will be doing.  - Not making much sense? - + Read the Testcase briefly, just to have a general idea of what you will be doing.{' '} + Not making much sense? + The testcases are generally split into four sections:
        • Description should give you a general idea of what is being tested
        • @@ -149,14 +149,25 @@ class FedoraManualTestingItem extends Component {
        • - Based on the enviromnent, select and download and appropriate ISO here.  - Not sure how? + Based on the enviromnent, select and download and appropriate ISO here.{' '} + Not sure how?
          • Most of the time Workstation Live, or Server DVD are fine, but sometimes there are specific products (e.g. Xfce) to be tested
          • - Make sure to read about identifying the environment above. - Show me! + Make sure to read about identifying the environment above.{' '} + Show me! + +
              +
            • + 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 Result column. +
            • +
            • + Find the row with the {tc_rawname} value, and note which of the environments still has no results filled in. +
            • +
            +
          @@ -164,19 +175,28 @@ class FedoraManualTestingItem extends Component {
        • - Study the Testcase thoroughly, to be sure you know what to do.  - Feeling a bit lost? + Study the Testcase thoroughly, to be sure you know what to do.{' '} + Feeling a bit lost?
          • - The testcase structure is not making sense? - Click here + The testcase structure is not making sense?{' '} + Click here + + The testcases are generally split into four sections: +
              +
            • Description should give you a general idea of what is being tested
            • +
            • Setup describes the steps to take before you begin working on the testcase
            • +
            • How to test contains the individual steps to take in order to perform the testcase
            • +
            • Expected results describe what you should check while testing in order to decide whether it Passed of Failed
            • +
            +
          • - Maybe you are stuck, or just do not understand something? Feel free to ask on our IRC channel #fedora-qa at freenode.net - Don't have an IRC client? + Maybe you are stuck, or just do not understand something? Feel free to ask on our IRC channel #fedora-qa at freenode.net{' '} + Don't have an IRC client? - If you are not that familiar with IRC, you can use the web-interface + If you are not that familiar with IRC, you can use the web-interface{' '} just enter a Nickname of your choice, #fedora-qa (including the hash sign) in the Channels field, and click Connect.
          • @@ -188,7 +208,7 @@ class FedoraManualTestingItem extends Component { Get your hands dirty, and test the hell out of it!
          • - Everything went well  + Everything went well{' '} Great! Either use relval report-results on command line (make sure to install the relval package first), @@ -196,7 +216,7 @@ class FedoraManualTestingItem extends Component { and put {{result|pass|YOUR_NAME_HERE|}} in the appropriate spot. - I found a bug! + I found a bug! Awesome! Ideally read up on https://fedoraproject.org/wiki/How_to_file_a_bug_report
            If you don't feel like reading a wall of text, at least pot together a small document containing: @@ -206,8 +226,8 @@ class FedoraManualTestingItem extends Component {
          • 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.
          • 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)
          • - 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 - Don't have an IRC client? + 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{' '} + 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. @@ -250,7 +270,7 @@ class ModalInfo extends Component { return (