(Created page with '{|border="1" |-style="color: white; background-color: #3074c2; font-weight: bold" | DATE || TIME || WHERE |- | '''2010-04-01''' || From ''12:00'' to ''21:00'' UTC (8am -> 5pm ED...') |
|||
| Line 11: | Line 11: | ||
=== What to test? === | === What to test? === | ||
Today's installment of Fedora Test Day will focus on ''' | Today's installment of Fedora Test Day will focus on '''Automated Bug Reporting Tool ([https://fedorahosted.org/abrt/wiki ABRT])'''. This tool should help non-power users with bug reporting, making it as easy as a few mouse clicks. ABRT is a daemon that watches for application crashes. When a crash occurs, it collects the crash data (core file, application's command line etc.) and takes action according to the type of application that crashed and according to the configuration in the abrt.conf configuration file. | ||
''Bottom line'': do not hunt the bugs with a pitchforks, rather use bugzappers/big light source to draw them from the dark and [http://fedorapeople.org/~dpravec/AsciiArt/MyBugZappers.html kill them easily at close range]. | |||
ABRT should be easy for users and very useful for developers and admins. Ease of crash/bug reporting and quick response from maintainers based on info from ABRT should make Fedora more stable and thus more attractive for users. | |||
=== Who's available === | === Who's available === | ||
Revision as of 09:48, 31 March 2010
| DATE | TIME | WHERE |
| 2010-04-01 | From 12:00 to 21:00 UTC (8am -> 5pm EDT) | #fedora-test-day (webirc) |
DELETE-ME: Last test day page for inspiration.
What to test?
Today's installment of Fedora Test Day will focus on Automated Bug Reporting Tool (ABRT). This tool should help non-power users with bug reporting, making it as easy as a few mouse clicks. ABRT is a daemon that watches for application crashes. When a crash occurs, it collects the crash data (core file, application's command line etc.) and takes action according to the type of application that crashed and according to the configuration in the abrt.conf configuration file.
Bottom line: do not hunt the bugs with a pitchforks, rather use bugzappers/big light source to draw them from the dark and kill them easily at close range.
ABRT should be easy for users and very useful for developers and admins. Ease of crash/bug reporting and quick response from maintainers based on info from ABRT should make Fedora more stable and thus more attractive for users.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Jiří Moskovčák (IRC: jmoskovc)
- Quality Assurance - Kparal (IRC: kparal)
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?
- Usb key
- Usb externally connected HD IDE/SATA
- Empty HD IDE/SATA/SCSI
- Free space on HD
- Rawhide Fully updated
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
Test Cases
Provide a list of test areas or test cases that you'd like contributors to execute. See Category:ABRT 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 a link where to report bugs. For example:
Please report all bugs into Bugzilla against the abrt component.
| User | Smolt Profile | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
|---|---|---|---|---|---|---|
| User:FasUser | HW | PASS | PASS | FAIL [1] | PASS |