From Fedora Project Wiki
No edit summary |
No edit summary |
||
(3 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This test case tests the basic functionality of the gnome-abrt. | |description=This test case tests the basic functionality of the gnome-abrt. | ||
|setup=Create few crashes to populate gnome-abrt with some data. Please, create | |setup=Create few crashes to populate gnome-abrt with some data. Please, create | ||
<ol> | |||
<li>crash for an applications having a desktop entry (gnome-abrt is one of these applications)</li> | |||
<li>not reportable problem (an oops from [[QA:Testcase ABRT kernel]])</li> | |||
<li>known crash (all will-crash crashes should be known)</li> | |||
</ol> | |||
|actions= | |actions= | ||
# run {{command|gnome-abrt}} in terminal | # run {{command|gnome-abrt}} in terminal | ||
Line 10: | Line 15: | ||
# Select more problems and click on the Delete button again | # Select more problems and click on the Delete button again | ||
# Keep gnome-abrt running and crash an application | # Keep gnome-abrt running and crash an application | ||
# Try to | # Try to start an another instance of ''gnome-abrt'': run {{command|gnome-abrt}} in terminal | ||
# Right click a problem in the list of problems | # Right click a problem in the list of problems | ||
# Click ''Open problem's data directory'' from the context menu. | # Click ''Open problem's data directory'' from the context menu. | ||
# Click ''Copy problem's ID to clipboard'' from the context menu. | # Click ''Copy problem's ID to clipboard'' from the context menu. | ||
# Find and select the not reportable problem | |||
# Find and select the known problem | |||
|results= | |results= | ||
# In the main window you should see a list of previously detected problems. | # In the main window you should see a list of previously detected problems. | ||
Line 21: | Line 28: | ||
# Step #6 all selected problems were deleted | # Step #6 all selected problems were deleted | ||
# Step #7 a problem for a newly created crashed appeared in the list of problems | # Step #7 a problem for a newly created crashed appeared in the list of problems | ||
# Step #8 the second instance didn't | # Step #8 the second instance didn't start and the first got focus | ||
# Step #10 the default file system browser should appear | # Step #10 the default file system browser should appear | ||
# Step #11 clipboard should contain the path to problem's data directory | # Step #11 clipboard should contain the path to problem's data directory | ||
# Step #12 ''Report'' button is disabled and the not reportable text is visible in the main window | |||
# Step #13 links to FAF server and Bugzilla should be visible below ''Reported to'' label | |||
}} | }} | ||
[[Category:Package_abrt_test_cases]] | [[Category:Package_abrt_test_cases]] | ||
[[Category:GNOME default application test cases]] |
Latest revision as of 10:36, 12 August 2022
Description
This test case tests the basic functionality of the gnome-abrt.
Setup
Create few crashes to populate gnome-abrt with some data. Please, create
- crash for an applications having a desktop entry (gnome-abrt is one of these applications)
- not reportable problem (an oops from QA:Testcase ABRT kernel)
- known crash (all will-crash crashes should be known)
How to test
- run
gnome-abrt
in terminal - wait until the main window is visible
- Go through the list of all problems and select one by one
- Single out any problem and click on the Report button
- Single out another problem and click on the Delete button
- Select more problems and click on the Delete button again
- Keep gnome-abrt running and crash an application
- Try to start an another instance of gnome-abrt: run
gnome-abrt
in terminal - Right click a problem in the list of problems
- Click Open problem's data directory from the context menu.
- Click Copy problem's ID to clipboard from the context menu.
- Find and select the not reportable problem
- Find and select the known problem
Expected Results
- In the main window you should see a list of previously detected problems.
- Step #3 an icon for an application with a desktop entry is shown
- Step #4 the reporting application started successfully
- Step #5 a selected problem was deleted
- Step #6 all selected problems were deleted
- Step #7 a problem for a newly created crashed appeared in the list of problems
- Step #8 the second instance didn't start and the first got focus
- Step #10 the default file system browser should appear
- Step #11 clipboard should contain the path to problem's data directory
- Step #12 Report button is disabled and the not reportable text is visible in the main window
- Step #13 links to FAF server and Bugzilla should be visible below Reported to label