From Fedora Project Wiki

(Created page with "{{Infobox_group | name = Fedora Test Days | image = link=QA/Fedora_19_test_days | caption = FIXME | date = <<FIXME>> | time = all day ...")
 
No edit summary
Line 2: Line 2:
| name = Fedora Test Days
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]
| caption = [[FIXME|FIXME]]
| caption = Provide users from trusted Active directory domain to legacy clients
| date = <<FIXME>>
| date = 2013-07-25
| time = all day
| time = all day
| website = [[QA/Fedora_19_test_days]]
| website = [[QA/Fedora_19_test_days]]
Line 14: Line 14:
== What to test? ==
== What to test? ==


Today's instalment of Fedora Test Day will focus on '''<<FIXME>>'''
Today's instalment of Fedora Test Day will focus on making the support for users coming from a trusted Active Directory domain available to legacy (non-SSSD) clients as well as providing support for using POSIX attributes from AD.


== Who's available ==
== Who's available ==
* Development: [[User:abbra|Alexander Bokovoy]] (ab), [[User:jhrozek|Jakub Hrozek]]
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)


The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
== Feedback ==
* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
We need your feedback!
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
* Talk to us on [irc://irc.freenode.net/#freeipa #freeipa] on Freenode
* Send as an [mailto:freeipa-users@redhat.com e-mail].
* Log issues and enhancements in [https://fedorahosted.org/freeipa FreeIPA Trac] or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=freeipa&version=19 Bugzilla].


== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  


List any prerequisite needs for the test event. A fresh system, virtualized guest, a blank DVD ... a desire to break software?
* A live image. Tips on using a live image are available at [[FedoraLiveCD]].
 
{|
* Usb key
! Architecture !! SHA256SUM
* Usb externally connected HD IDE/SATA
|-
* Empty HD IDE/SATA/SCSI
| [http://fedorapeople.org/groups/qa/testday-TBD-x86_64.iso x86_64] || checksum-tbd
* Free space on HD
|-
 
| [http://fedorapeople.org/groups/qa/testday-TBD-i686.iso i686] || checksum-tbd
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
|}
{{admon/note | Memory | Please make sure that the LiveCD has enough memory to operate. We recommend:
* At minimum 2.5 GB of memory for non-graphical run
* At minimum 3 GB memory for graphical (GNOME) run
}}


* An updated [http://fedoraproject.org/get-prerelease Fedora XX pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
* An updated [http://fedoraproject.org/get-prerelease Fedora XX pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]

Revision as of 16:58, 12 July 2013

Fedora Test Days
Echo-testing-48px.png
Provide users from trusted Active directory domain to legacy clients

Date 2013-07-25
Time all day

Website QA/Fedora_19_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
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 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 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 making the support for users coming from a trusted Active Directory domain available to legacy (non-SSSD) clients as well as providing support for using POSIX attributes from AD.

Who's available

Feedback

We need your feedback!

Prerequisite for Test Day

  • A live image. Tips on using a live image are available at FedoraLiveCD.
Architecture SHA256SUM
x86_64 checksum-tbd
i686 checksum-tbd
Note.png
Memory
Please make sure that the LiveCD has enough memory to operate. We recommend:
  • At minimum 2.5 GB of memory for non-graphical run
  • At minimum 3 GB memory for graphical (GNOME) run

How to test?

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 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 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 Bugzilla usually for the component udisks, or 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 result template to enter your result, as shown in the example result line.

User Sample test 1 Sample test 2 Sample test 3 Sample test 4 References
Sample User
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345