From Fedora Project Wiki

(clean ups)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
 
|description=This test case tests [[Features/RetraceServer|Retrace Server]]'s integration into [[Features/ABRT|ABRT]] GUI.
 
|description=This test case tests [[Features/RetraceServer|Retrace Server]]'s integration into [[Features/ABRT|ABRT]] GUI.
 +
|setup=
 +
# Make sure you have ABRT crashes caught by CCpp (crashes in C and C++ applications) that need retrace (i.e. you haven't already retrieved the necessary debuginfo packages and generated the full backtrace) available. If you do not have any, run a C or C++ application and crash it using {{command|kill -SIGSEGV (pid)}} or {{command|pkill -SIGSEGV (processname)}}
 
|actions=
 
|actions=
# Run {{command|abrt-gui}} and select a binary crash.
+
# Run {{command|abrt-gui}} and select a binary crash
# On Analyze step select <tt>Retrace Server</tt>. If GUI shows reporting selector instead of analyze selector (this happens if you already have the backtrace), select any reporter and click "Regenerate backtrace" button in the next window. This will bring you to analyzer selector.
+
# On Analyze step select <tt>Retrace Server</tt>. If GUI shows reporting selector instead of analyze selector (this happens if you already have the backtrace), select any reporter and click "Regenerate backtrace" button in the next window. This will bring you to analyzer selector
# Wait until the job is finished.
+
# Wait until the job is finished
# Continue with reporting.
+
# Continue with reporting
# Not all distributions are supported. For example, trying to retrace from F13 gives the following message: "ERROR: Command failed: ... Could not open/read file:///var/cache/abrt-retrace/fedora-13-x86_64/repodata/repomd.xml". We expect that the following distros work: F14, F15, RHEL6.0
+
# Not all distributions are supported. For example, trying to retrace from Fedora 13 gives the following message: ''ERROR: Command failed: ... Could not open/read file:///var/cache/abrt-retrace/fedora-13-x86_64/repodata/repomd.xml''. We expect the following distributions to work: Fedora 14, Fedora 15, Red Hat Enterprise Linux 6.0
# If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut-n-pasted from GUI report window, or retrieved from event_log file in problem data directory (such as /var/spool/abrt/ccpp-2011-03-04-15:46:26-22496/event_log).
+
# If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from GUI report window, or retrieved from event_log file in problem data directory (e.g. {{filename|/var/spool/abrt/ccpp-2011-03-04-15:46:26-22496/event_log}})
 
 
 
|results=
 
|results=
# The backtrace should be generated and it should be in a good quality.
+
# The backtrace should be generated and it should good quality (all symbols should be present)
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 19:11, 29 March 2011

Description

This test case tests Retrace Server's integration into ABRT GUI.

Setup

  1. Make sure you have ABRT crashes caught by CCpp (crashes in C and C++ applications) that need retrace (i.e. you haven't already retrieved the necessary debuginfo packages and generated the full backtrace) available. If you do not have any, run a C or C++ application and crash it using kill -SIGSEGV (pid) or pkill -SIGSEGV (processname)

How to test

  1. Run abrt-gui and select a binary crash
  2. On Analyze step select Retrace Server. If GUI shows reporting selector instead of analyze selector (this happens if you already have the backtrace), select any reporter and click "Regenerate backtrace" button in the next window. This will bring you to analyzer selector
  3. Wait until the job is finished
  4. Continue with reporting
  5. Not all distributions are supported. For example, trying to retrace from Fedora 13 gives the following message: ERROR: Command failed: ... Could not open/read file:///var/cache/abrt-retrace/fedora-13-x86_64/repodata/repomd.xml. We expect the following distributions to work: Fedora 14, Fedora 15, Red Hat Enterprise Linux 6.0
  6. If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from GUI report window, or retrieved from event_log file in problem data directory (e.g. /var/spool/abrt/ccpp-2011-03-04-15:46:26-22496/event_log)

Expected Results

  1. The backtrace should be generated and it should good quality (all symbols should be present)