Editing Test Day:2013-03-28 Shared System Certificates

{{Infobox_group
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]
| caption = Shared System Certificates
| date = 2012-03-28
| time = all day
| website = [[QA/Fedora_19_test_days]]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| fedora_mailing_list = test
}}

{{admon/warning | In construction | This Test Day page is still in construction. It shall be ready for the Test Day - when this message is removed :) .}}

{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}

== What to test? ==

Today's instalment of Fedora Test Day will focus on testing the [[SharedSystemCertificates|Shared System Certificates]] feature. The goal is to make NSS, GnuTLS, OpenSSL and Java share a default source for retrieving system certificate anchors and black list information. 

The work done in Fedora 19 is an initial step of a comprehensive solution. But none the less it makes the installation of anchors and blacklists standardized across the various crypto libraries. Currently an 'extract' step is required, but in the future we hope to make this unnecessary.

== Who's available ==

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:StefWalter|Stef Walter]] (stefw), [[User:KaiEngert|Key Engert]] (kaie)
* Quality Assurance - [[User:JiriJaburek|Jiri Jaburek]] (jjaburek), [[User:AlesMarecek|Ales Marecek]] (alich)

== Prerequisite for Test Day == 

To test this feature you need an updated Fedora 19 system, with at least the following software:

* p11-kit 0.17.4 (or later)
* p11-kit-trust 0.17.4 (or later)
* ca-certficates 2012.87-9 (or later)
* nss 3.14.3-10 (or later)

Some of the software used to test this feature in the test cases below:

* firefox
* gnutls-utils
* nss-tools
* openssl
* java-1.7.0-openjdk-devel
* epiphany
* wget

TODO: There will be a live image available for testing, which contains all of the above software.

All of the above is available on an updated Fedora 19 nightly. Unfortunately the nightlies have been somewhat unstable as of late. 

== How to test? ==

xxxxxxxxxxxxxxxx TODO xxxxxxxxxxxxxxxxxx

High level details on how a contributor can get involved.  This can include (but not limited to):

* Areas to target with exploratory testing
* A list of pre-defined test cases to execute
* How to report back results

Here's another common chunk (again, replace XX as above):

=== '''Update your machine''' ===

If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:

=== '''Live image''' ===

Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].

== Test Cases ==

Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].

== 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. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:

If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.

{|
! User
! [[QA:Testcase_sample_1|Sample test 1]]
! [[QA:Testcase_sample_2|Sample test 2]]
! [[QA:Testcase_sample_3|Sample test 3]]
! [[QA:Testcase_sample_4|Sample test 4]]
! References
|-
| [[User:SampleUser|Sample User]]
| {{result|none}} 
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|fail}} <ref>{{bz|12345}}</ref>
| <references/>
|-
|}

[[Category:Test Days]]
[[Category:QA Templates]]