mNo edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{Admon/note|Associated release criterion|This test case is associated with the {{#switch: {{{1}}} | Beta =[[Beta_Release_Criteria#{{{2| | {{Admon/note|Associated release criterion|This test case is associated with the {{#switch: {{{1}}} | Beta =[[Beta_Release_Criteria#{{{2|Remote_logging}}}]]| Basic =[[Basic_Release_Criteria#{{{2|Remote logging}}}]]|[[Fedora_{{FedoraVersionNumber|next}}_{{{1|MILESTONE}}}_Release_Criteria#{{{2|Remote_logging}}}]]}} release criterion. If you are doing [[QA:Release_validation_test_plan|release validation testing]], a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the [https://qa.fedoraproject.org/blockerbugs/propose_bug blocker bug nomination page].}} | ||
{{QA/Test_Case | {{QA/Test_Case |
Revision as of 14:16, 29 May 2018
Description
This article is incomplete. Remote logging happens when the operating system logs events and errors to a different machine (server) over the network. This test case shows whether remote logging can be set up in a Fedora Server environment using system packages available after the installation.
How to test
Be as specific as required for the target audience.
- Start here ...
- Next do this ...
- Finally click that
Expected Results
The following must be true to consider this a successful test run. Be brief ... but explicit.
- Step #1 completes without error
- The system boots into runlevel 5
- Program completes with exit code 0
Optional
Optionally provide hints for exploratory testing.