From Fedora Project Wiki

 
(34 intermediate revisions by 8 users not shown)
Line 10: Line 10:
  
 
Today's installment of Fedora Test Day / Fit & Finish will focus on '''Sectool'''.
 
Today's installment of Fedora Test Day / Fit & Finish will focus on '''Sectool'''.
 +
 +
[https://fedorahosted.org/sectool/ Sectool] is a security tool that can be used both as a security audit as well as a part of an intrusion detection system. It consists of set of tests, library and textual/graphical frontend. Tests are sorted into groups and security levels. Administrators can run selected tests, groups or whole security levels.
  
 
=== Who's available ===  
 
=== Who's available ===  
  
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:Mbarabas]], [[User:Jhrozek]]?
+
* Development - Maros Barabas (nick xBarry), Jakub Hrozek (nick jhrozek)
* Quality Assurance - [[User:Ebenes]], [[User:Hondra]]
+
* Quality Assurance - Eduard Benes (nick ebenes), Miroslav Vadkerty (nick mvadkert)
  
 
=== Prerequisite for Test Day ===  
 
=== Prerequisite for Test Day ===  
 
* Any sectool version >= 0.9.4 on Fedora 11 or Rawhide system. (the more different testing environment we get, the better)
 
* Any sectool version >= 0.9.4 on Fedora 11 or Rawhide system. (the more different testing environment we get, the better)
 
* Install sectool by running following commands:
 
* Install sectool by running following commands:
   rpm -Uvh http://mbarabas.fedorapeople.org/sectool-0.9.4-1.fc11.i586.rpm
+
   rpm -Uvh http://mbarabas.fedorapeople.org/sectool-0.9.4-2.fc11.i586.rpm
   rpm -Uvh http://mbarabas.fedorapeople.org/sectool-gui-0.9.4-1.fc11.i586.rpm
+
   rpm -Uvh http://mbarabas.fedorapeople.org/sectool-gui-0.9.4-2.fc11.i586.rpm
  
 
<!--
 
<!--
Line 35: Line 37:
 
=== How to test? ===
 
=== How to test? ===
  
High level details on how a contributor can get involved. This can include (but not limited to):
+
* We would like to focus on following areas to be targeted with exploratory testing: GUI, DBus, individual Sectool tests under different test env.
 +
* Individual test cases we want to execute: are in section 'Test Cases'. Additonally you can follow links in the 'Tests Results' table header.
 +
* Test results should be reported into table in section 'Test Results' and any issues filed into bugzilla.
 +
* Detailed list of tests with instructions is available [https://fedoraproject.org/wiki/Features/Sectool#How_To_Test here]
 +
* For additional info see: https://fedoraproject.org/wiki/Features/Sectool
  
* Areas to target with exploratory testing: GUI, DBus, Sectool Tests under different test env.
 
* A list of pre-defined test cases to execute: see section 'Test Cases'. Additonally you can follow links in the 'Tests Results' table header.
 
* How to report back results: bugzilla, table in section 'Test Results'
 
 
For additional info see: https://fedoraproject.org/wiki/Features/Sectool
 
Sectool homepage: https://fedorahosted.org/sectool/
 
  
 
=== Knonwn Issues===
 
=== Knonwn Issues===
Line 50: Line 50:
  
 
See 'How To Test' section on the Feature page: https://fedoraproject.org/wiki/Features/Sectool#How_To_Test
 
See 'How To Test' section on the Feature page: https://fedoraproject.org/wiki/Features/Sectool#How_To_Test
Additonal ideas:  
+
 
 +
Additionally one can do a little scripting exercise and create his own hello-world sectool test:  
 
* [https://fedorahosted.org/sectool/wiki/BashTestTutorial Create your own sectool test in bash]
 
* [https://fedorahosted.org/sectool/wiki/BashTestTutorial Create your own sectool test in bash]
 
* [https://fedorahosted.org/sectool/wiki/PythonTestTutorial Create your own sectool test in python]
 
* [https://fedorahosted.org/sectool/wiki/PythonTestTutorial Create your own sectool test in python]
  
 
=== Test Results ===
 
=== Test Results ===
<!--
 
Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results.  For example:
 
-->
 
  
 
Test results table for individual test cases (direct links in the first row).
 
Test results table for individual test cases (direct links in the first row).
Line 74: Line 72:
 
! [https://fedoraproject.org/wiki/Features/Sectool#DBus_testing DBus testing]
 
! [https://fedoraproject.org/wiki/Features/Sectool#DBus_testing DBus testing]
 
! [https://fedoraproject.org/wiki/Features/Sectool#GUI_testing GUI testing]
 
! [https://fedoraproject.org/wiki/Features/Sectool#GUI_testing GUI testing]
 
+
! [[http://www.creationdesiteweb.ca conception site web]]
 
! References
 
! References
 
|-
 
|-
| [[User:FasUser]]  
+
| [[User:Liam]]  
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
+
| f12 rawhide
| FAIL <ref>See {{bz|12345}}</ref>
 
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 +
| FAIL <ref>See {{bz|520557}}</ref>
 
| PASS
 
| PASS
 
| PASS
 
| PASS
Line 91: Line 89:
 
| <references/>
 
| <references/>
 
|-
 
|-
 +
| [[User:Rhe]]
 +
| f12 rawhide
 +
| PASS
 +
| PASS
 +
| FAIL <ref>See {{bz|520557}}</ref>
 +
| PASS
 +
| PASS
 +
| PASS
 +
| PASS
 +
| PASS
 +
| FAIL <ref>See {{bz|520579}}</ref>
 +
| PASS
 +
| <references/>
 
|-
 
|-
| [[User:AnotherTestUser]]  
+
| [[User:mvadkert]]  
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
+
| [http://www.smolts.org/client/show/pub_90d9ce85-ee31-49ad-9729-69b2f02bffb7 HW]
| FAIL <ref>See {{bz|12345}}</ref>
+
| FAIL <ref>See {{bz|520588}}</ref>
 +
| FAIL <ref>See {{bz|520592}}</ref>
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 +
| FAIL <ref>See {{bz|520649}}</ref>
 
| PASS
 
| PASS
 +
| PASS
 +
| FAIL <ref>See {{bz|520616}}</ref>
 +
| FAIL <ref>See {{bz|520658}}</ref>
 +
| <references/>
 +
|-
 +
| [[User:ebenes]]
 +
| [http://www.smolts.org/client/show/pub_18d36eee-f6c4-4379-bc00-02729923dc66 HW]
 +
| FAIL <ref>See {{bz|520588}}</ref>
 +
| FAIL <ref>See {{bz|520592}}</ref>
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 +
| FAIL <ref>See {{bz|520664}}</ref>
 
| PASS
 
| PASS
 +
| FAIL <ref>See {{bz|520591}}</ref>
 +
| FAIL <ref>See {{bz|520638}}</ref>  <ref>See {{bz|520662}}</ref>
 
| <references/>
 
| <references/>
 
|-
 
|-
| [[User:Liam]]  
+
| [[User:jkoten|jkoten]]  
| f12 rawhide
+
| [http://www.smolts.org/client/show/pub_5eef7c88-4bef-4197-8f96-f003f0cccea6 HW]
 +
| FAIL <ref> See {{bz|520591}}</ref>
 +
| FAIL <ref> See {{bz|520645}}</ref>
 
| PASS
 
| PASS
 
| PASS
 
| PASS
| FAIL <ref>See {{bz|520557}}</ref>
 
 
| PASS
 
| PASS
 +
| IN PROGRESS
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 +
| FAIL <ref>See {{bz|520591}}</ref>
 +
| IN PROGRESS
 +
| Tested with sectool-0.9.4-2.fc11.i586
 +
 +
<references/>
 +
|-
 +
| [[User:psss|psss]]
 +
| [http://www.smolts.org/client/show/pub_8219d7df-f286-473f-9ea9-e4db0b4068af HW]
 +
| FAIL <ref> See {{bz|520639}}</ref>
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 +
| FAIL <ref> See {{bz|520768}} </ref>
 
| PASS
 
| PASS
 +
| PASS
 +
| PASS
 +
| FAIL <ref> See {{bz|520591}}</ref>
 +
| FAIL <ref> See {{bz|520644}}</ref>
 
| <references/>
 
| <references/>
 
|-
 
|-
| [[User:Rhe]]  
+
| [[User:hdong]]  
| f12 rawhide
+
| VirtualBox f12 rawhide i386
 +
| FAIL <ref> See {{bz|520588}}</ref>
 
| PASS
 
| PASS
 
| PASS
 
| PASS
| FAIL <ref>See {{bz|520557}}</ref>
 
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 
| PASS
 +
| N/A
 
| PASS
 
| PASS
| PASS
+
| FAIL <ref> See {{bz|520591}}</ref>
| FAIL <ref>See {{bz|520579}}</ref>
 
 
| PASS
 
| PASS
 
| <references/>
 
| <references/>
|-
 
 
|}
 
|}
  
 
+
[[http://realforexbroker.com/mission/ forex broker reviews]]
[[Category:Test Days]]
+
[[Category:Fedora 12 Test Days]]
[[Category:Proposed_Test_Days]]
 

Latest revision as of 21:17, 2 December 2012

DATE TIME WHERE
Sectool Fit&Finish From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-test-day (webirc)

What to test?[edit]

Today's installment of Fedora Test Day / Fit & Finish will focus on Sectool.

Sectool is a security tool that can be used both as a security audit as well as a part of an intrusion detection system. It consists of set of tests, library and textual/graphical frontend. Tests are sorted into groups and security levels. Administrators can run selected tests, groups or whole security levels.

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

  • Development - Maros Barabas (nick xBarry), Jakub Hrozek (nick jhrozek)
  • Quality Assurance - Eduard Benes (nick ebenes), Miroslav Vadkerty (nick mvadkert)

Prerequisite for Test Day[edit]

  • Any sectool version >= 0.9.4 on Fedora 11 or Rawhide system. (the more different testing environment we get, the better)
  • Install sectool by running following commands:
 rpm -Uvh http://mbarabas.fedorapeople.org/sectool-0.9.4-2.fc11.i586.rpm
 rpm -Uvh http://mbarabas.fedorapeople.org/sectool-gui-0.9.4-2.fc11.i586.rpm


How to test?[edit]

  • We would like to focus on following areas to be targeted with exploratory testing: GUI, DBus, individual Sectool tests under different test env.
  • Individual test cases we want to execute: are in section 'Test Cases'. Additonally you can follow links in the 'Tests Results' table header.
  • Test results should be reported into table in section 'Test Results' and any issues filed into bugzilla.
  • Detailed list of tests with instructions is available here
  • For additional info see: https://fedoraproject.org/wiki/Features/Sectool


Knonwn Issues[edit]

Sectool has missing SELinux policy - See RHBZ #520577

Test Cases[edit]

See 'How To Test' section on the Feature page: https://fedoraproject.org/wiki/Features/Sectool#How_To_Test

Additionally one can do a little scripting exercise and create his own hello-world sectool test:

Test Results[edit]

Test results table for individual test cases (direct links in the first row).

User Smolt Profile Sanity testing Running the tests Running a level Display filters Test auto action Diff and sending a mail Overriding levels Logging DBus testing GUI testing [conception site web] References
User:Liam f12 rawhide PASS PASS FAIL [1] PASS PASS PASS PASS PASS PASS PASS
  1. See RHBZ #520557
User:Rhe f12 rawhide PASS PASS FAIL [1] PASS PASS PASS PASS PASS FAIL [2] PASS
  1. See RHBZ #520557
  2. See RHBZ #520579
User:mvadkert HW FAIL [1] FAIL [2] PASS PASS PASS FAIL [3] PASS PASS FAIL [4] FAIL [5]
  1. See RHBZ #520588
  2. See RHBZ #520592
  3. See RHBZ #520649
  4. See RHBZ #520616
  5. See RHBZ #520658
User:ebenes HW FAIL [1] FAIL [2] PASS PASS PASS PASS FAIL [3] PASS FAIL [4] FAIL [5] [6]
  1. See RHBZ #520588
  2. See RHBZ #520592
  3. See RHBZ #520664
  4. See RHBZ #520591
  5. See RHBZ #520638
  6. See RHBZ #520662
jkoten HW FAIL [1] FAIL [2] PASS PASS PASS IN PROGRESS PASS PASS FAIL [3] IN PROGRESS Tested with sectool-0.9.4-2.fc11.i586
  1. See RHBZ #520591
  2. See RHBZ #520645
  3. See RHBZ #520591
psss HW FAIL [1] PASS PASS PASS FAIL [2] PASS PASS PASS FAIL [3] FAIL [4]
  1. See RHBZ #520639
  2. See RHBZ #520768
  3. See RHBZ #520591
  4. See RHBZ #520644
User:hdong VirtualBox f12 rawhide i386 FAIL [1] PASS PASS PASS PASS PASS N/A PASS FAIL [2] PASS
  1. See RHBZ #520588
  2. See RHBZ #520591

[forex broker reviews]