From Fedora Project Wiki
(Created testcase) |
m (wrong file name (os_release -> package)) |
||
Line 12: | Line 12: | ||
# Run {{command|abrt-retrace-client backtrace -k -t task_id -p task_password}} after the job is finished by failure. | # Run {{command|abrt-retrace-client backtrace -k -t task_id -p task_password}} after the job is finished by failure. | ||
# Run {{command|abrt-retrace-client batch -k -d /path/ABRT_crash_directory}}. | # Run {{command|abrt-retrace-client batch -k -d /path/ABRT_crash_directory}}. | ||
# Run {{command|abrt-retrace-client create -d /path/ABRT_crash_directory}}, replacing coredump, executable or | # Run {{command|abrt-retrace-client create -d /path/ABRT_crash_directory}}, replacing coredump, executable or package file by some random content. | ||
# Run {{command|abrt-retrace-client create -d /path/ABRT_crash_directory --url URL}}, with URL different to {{command|retrace01.fedoraproject.org}}. | # Run {{command|abrt-retrace-client create -d /path/ABRT_crash_directory --url URL}}, with URL different to {{command|retrace01.fedoraproject.org}}. | ||
Revision as of 22:16, 16 March 2011
Description
This test case tests Retrace Server's command line interface.
How to test
You need ABRT crashes (whole directories) that need retrace - caught by CCpp.
- Run
abrt-retrace-client create -d /path/ABRT_crash_directory
- Run
abrt-retrace-client create -k -d /path/ABRT_crash_directory
, the-k
option disables HTTPS certificate check. - Run
abrt-retrace-client status -k -t task_id -p task_password
with task_id and task_password obtained fromcreate
action. - Run
abrt-retrace-client status -k -t task_id -p task_password
with a wrong combination of task_id and task_password. - Run
abrt-retrace-client log -k -t task_id -p task_password
while the job is stillPENDING
. - Run
abrt-retrace-client log -k -t task_id -p task_password
after the job is finished (by success or failure). - Run
abrt-retrace-client backtrace -k -t task_id -p task_password
after the job is finished successfully. - Run
abrt-retrace-client backtrace -k -t task_id -p task_password
after the job is finished by failure. - Run
abrt-retrace-client batch -k -d /path/ABRT_crash_directory
. - Run
abrt-retrace-client create -d /path/ABRT_crash_directory
, replacing coredump, executable or package file by some random content. - Run
abrt-retrace-client create -d /path/ABRT_crash_directory --url URL
, with URL different toretrace01.fedoraproject.org
.
Expected Results
- The command should fail because of untrusted HTTPS certificate.
- The job should be started, task_id and task_password returned on stdout.
- One of the values
PENDING
,FINISHED_SUCCESS
,FINISHED_FAILURE
should be returned on stdout. - HTTP
404 Not Found
or403 Forbidden
error code should be returned depending on whether task with task_id exists or not. Should be the same withlog
andbacktrace
actions. - HTTP
404 Not Found
error code should be returned. Should be the same withbacktrace
action. - Plaintext log should be returned on stdout.
- Plaintext backtrace should be returned on stdout.
- HTTP
404 Not Found
error code should be returned. - All actions should happen at once - create, periodically ask for status, download log / backtrace depending on whether the result was successful or not.
- The task should finish by failure.
- The upload should fail.