The Installation 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.
- Note: some (not that many, though) of these testcases require Bare-metal machine. Be sure to read the Description of the testcase carefully.
-
);
- break;
- case "Desktop":
- l1 = (
The Desktop testcases cover basic functionality of the desktop environment.
- You can either install Fedora onto clean Virtual or Bare-metal machine, or use a Live image instead.
-
);
- break;
- case "Base":
- l1 = (
The Base testcases cover the system's basic functionality just after a clean installation.
- Most times, you will be asked to perform a clean Fedora installation. You can use either Virtual or Bare-metal machine.
- Pro tip: using a snapshot of cleanly installed Virtual machine is just fine. No need to reinstall for every testcase.
-
);
- break;
- case "Server":
- l1 = (
The Server testcases usually require multiple machines to test the server-client behaviour, and might feel a bit advanced.
-
);
- break;
- case "Cloud":
- 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.
-
- Before a new version of a package is pushed to the Fedora's Updates repository, it needs to be tested and proved functional.{' '}
- Tell me more about the process!
-
- The updates are kept in Bodhi, which acts as a gatekeeper between new package releases and the stable repositories.{' '}
- Users (or automated systems) can then provide feedback in form of positive/negative Karma, marking the update as working (or not) within the scope of their expectations.{' '}
- An update can (and usually does) consist of several packages (rpms), that are going through the acceptance process together.
-
-
Sure, let me do it!
-
-
- Fedora Accounts System (FAS) account is required.{' '}
- Don't have one yet?
-
-
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 upgrades{' '}
- And choose a package you know.
-
-
-
- Install the package sudo dnf --enablerepo=updates-testing update PACKAGE_NAME, and test whether it works, as you would expect.
- Note: the package you have chosen might have some dependencies. Be sure to - or at least try to - test those too!{' '}
- Need some tips?
-
- Sometimes, the update associated with the package you just installed fixes some specific bugs, or has testcases associated with it.
- Run fedora-easy-karma PACKAGE_NAME, and look for Bugs, Test Cases, and/or Notes sections in the detailed output.
-
-
-
- Run fedora-easy-karma --fas-username=FAS_USERNAME and report what you found out.{' '}
- New to fedora-easy-karma?
-
- It identifies the packages installed from the updates-testing repository, and matches them to the updates in Bodhi.
- Then, you are presented with the relevant updates one-by-one, to submit Karma and a comment.
- Not sure what Karma means?
-
-
-
- Enter 1 to mark positive karma (the update works just fine, as far as you can tell), or -1{' '}
- to mark the package as broken.
- Not sure you can judge the package's state? Either just press Enter to skip it, or insert i (instead of 1 or -1) to also ignore the package in the future.
-
-
- Add a comment - this could be something as simple as Works for me, but make sure to provide reasonable amount of detail, when submitting negative karma (ideally, you should also create a bugreport, and refence it in the comment).
-
-
-
-
-
-
Restore the stable-packages on your system by running sudo dnf distro-sync
- 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.
-
-
-
-
-
-
- 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
-
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
-
-
-
-
-
- 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!
-
- The testcase structure is not making sense?
- Click here
-
-
- 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
- just enter a Nickname of your choice, #fedora-qa (including the hash sign) in the Channels field, and click Connect.
-
-
-
-
-
-
-
- Get your hands dirty, and test the hell out of it!
-
-
- Everything went well
-
- Great!
- Either use relval report-results on command line (make sure to install the relval package first),
- or modify the matrix directly by clicking on the Edit link next to the Matrice's header,
- and put {{result|pass|YOUR_NAME_HERE|}} in the appropriate spot.
-
-
- 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:
-
-
Brief description of what went wrong (e.g. "QA:Testcase_dualboot_with_windows - Bootloader does not show the Windows option")
-
The name of the ISO image you used (e.g. "Fedora-Server-netinst-i386-Rawhide-20181227.n.0.iso")
-
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?
-
- 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.
-
-
-
- Once you get the Bug reported, make sure to also submit the result into the testing matrix.
- Either use relval report-results on command line (make sure to install the relval package first),
- or modify the matrix directly by clicking on the Edit link next to the Matrice's header,
- and put {{result|fail|YOUR_NAME_HERE|BUG_NUMBER|}} in the appropriate spot.
-
-
+ Before a new version of a package is pushed to the Fedora's Updates repository, it needs to be tested and proved functional.{' '}
+ Tell me more about the process!
+
+ The updates are kept in Bodhi, which acts as a gatekeeper between new package releases and the stable repositories.{' '}
+ Users (or automated systems) can then provide feedback in form of positive/negative Karma, marking the update as working (or not) within the scope of their expectations.{' '}
+ An update can (and usually does) consist of several packages (rpms), that are going through the acceptance process together.
+
+
Sure, let me do it!
+
+
+ Fedora Accounts System (FAS) account is required.{' '}
+ Don't have one yet?
+
+
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 upgrades{' '}
+ And choose a package you know.
+
+
+
+ Install the package sudo dnf --enablerepo=updates-testing update PACKAGE_NAME, and test whether it works, as you would expect.
+ Note: the package you have chosen might have some dependencies. Be sure to - or at least try to - test those too!{' '}
+ Need some tips?
+
+ Sometimes, the update associated with the package you just installed fixes some specific bugs, or has testcases associated with it.
+ Run fedora-easy-karma PACKAGE_NAME, and look for Bugs, Test Cases, and/or Notes sections in the detailed output.
+
+
+
+ Run fedora-easy-karma --fas-username=FAS_USERNAME and report what you found out.{' '}
+ New to fedora-easy-karma?
+
+ It identifies the packages installed from the updates-testing repository, and matches them to the updates in Bodhi.
+ Then, you are presented with the relevant updates one-by-one, to submit Karma and a comment.
+ Not sure what Karma means?
+
+
+
+ Enter 1 to mark positive karma (the update works just fine, as far as you can tell), or -1{' '}
+ to mark the package as broken.
+ Not sure you can judge the package's state? Either just press Enter to skip it, or insert i (instead of 1 or -1) to also ignore the package in the future.
+
+
+ Add a comment - this could be something as simple as Works for me, but make sure to provide reasonable amount of detail, when submitting negative karma (ideally, you should also create a bugreport, and refence it in the comment).
+
+
+
+
+
+
Restore the stable-packages on your system by running sudo dnf distro-sync
+
+
+
+ )
+ }
+}
\ No newline at end of file
diff --git a/src/wizard/FedoraManualTesting.js b/src/wizard/FedoraManualTesting.js
new file mode 100644
index 0000000..c95f343
--- /dev/null
+++ b/src/wizard/FedoraManualTesting.js
@@ -0,0 +1,271 @@
+import React, { Component } from 'react';
+import { Card, CardHeader, CardBody, UncontrolledCollapse } from 'reactstrap';
+import { Modal, ModalHeader, ModalBody, ModalFooter } from 'reactstrap';
+
+export default class FedoraManualTesting extends Component {
+ render() {
+ let sections = Object.keys(this.props.data).map(k => ());
+ return(
The Installation 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.
+ Note: some (not that many, though) of these testcases require Bare-metal machine. Be sure to read the Description of the testcase carefully.
+
);
+ break;
+ case "Desktop":
+ l1 = (
The Desktop testcases cover basic functionality of the desktop environment.
+ You can either install Fedora onto clean Virtual or Bare-metal machine, or use a Live image instead.
+
);
+ break;
+ case "Base":
+ l1 = (
The Base testcases cover the system's basic functionality just after a clean installation.
+ Most times, you will be asked to perform a clean Fedora installation. You can use either Virtual or Bare-metal machine.
+ Pro tip: using a snapshot of cleanly installed Virtual machine is just fine. No need to reinstall for every testcase.
+
);
+ break;
+ case "Server":
+ l1 = (
The Server testcases usually require multiple machines to test the server-client behaviour, and might feel a bit advanced.
+
);
+ break;
+ case "Cloud":
+ 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.
+
+ 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.
+
+
+
+
+
+
+ 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
+
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
+
+
+
+
+
+ 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!
+
+ The testcase structure is not making sense?
+ Click here
+
+
+ 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
+ just enter a Nickname of your choice, #fedora-qa (including the hash sign) in the Channels field, and click Connect.
+
+
+
+
+
+
+
+ Get your hands dirty, and test the hell out of it!
+
+
+ Everything went well
+
+ Great!
+ Either use relval report-results on command line (make sure to install the relval package first),
+ or modify the matrix directly by clicking on the Edit link next to the Matrice's header,
+ and put {{result|pass|YOUR_NAME_HERE|}} in the appropriate spot.
+
+
+ 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:
+
+
Brief description of what went wrong (e.g. "QA:Testcase_dualboot_with_windows - Bootloader does not show the Windows option")
+
The name of the ISO image you used (e.g. "Fedora-Server-netinst-i386-Rawhide-20181227.n.0.iso")
+
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?
+
+ 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.
+
+
+
+ Once you get the Bug reported, make sure to also submit the result into the testing matrix.
+ Either use relval report-results on command line (make sure to install the relval package first),
+ or modify the matrix directly by clicking on the Edit link next to the Matrice's header,
+ and put {{result|fail|YOUR_NAME_HERE|BUG_NUMBER|}} in the appropriate spot.
+
+