From Fedora Project Wiki


This TestCase covers FirstAidKit plugin for Openscap library.


Please install everything needed for Openscap testing and all packages from the relevant directory at

How to test

  1. Start FirstAidKit from the Applications/System Tools or type "firstaidkit -g gtk" to get debug messages
  2. Select "Security Audit" in the combo box
  3. Press "Start" button

List of enabled tests should show up, you can change the values between 0 and 1 to enable or disable test - all other values should result in an error message. Don't try to enable currently disabled tests for now please, since openscap library is not complete and not all tests work.

  1. Try changing something to 2, letter, or so...
  2. Press "OK"

List of policy variables show up, you can read the detailed descriptions in tooltips when you put your mouse over lines. You can also change the values, most of them should also check for correct format according to their description.

  1. Try changing some variables to correct and incorrect values, use your imagination
  2. Press "OK"

The application switches to it's results tab and starts showing results as "Waiting for check" and then the result (color coded too). In some cases when the machine gets under heavy load (openscap file probes..) the GUI won't update, but it will show "INFO: Starting OpenSCAP evaluation" in it's status bar.

  1. After it finishes, repeat this without restarting application - switch to the first tab, start the audit as described, but try to stop it during it's run, by pressing "Stop" button on the results page. It may take a moment, but it will stop right after the running test finishes.
  2. Close the application

Expected Results

The following must be true to consider this a successful test run.

  1. All dialogs are diasplayed as described
  2. It is not possible to enter incorrect values
  3. All result lines (for implemented tests) are either green or red and the application disables it's "Stop" button
  4. It is possible to interrupt the Audit
  5. No crash or traceback occurs in the debug output