QA:Testcase Retrace Server CLI

Description

This test case tests the Retrace Server's command line interface.

Setup

1. Ensure you have the plugin installed with the following command:
   • su -c 'yum install abrt-retrace-client'
2. 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)
3. The crash reports will be under /var/tmp/abrt; you can identify them by the date and time

How to test

1. Run abrt-retrace-client create -d /path/ABRT_crash_directory
2. Run abrt-retrace-client status -t task_id -p task_password with task_id and task_password obtained from create action
3. Run abrt-retrace-client status -t task_id -p task_password with a wrong combination of task_id and task_password
4. Run abrt-retrace-client log -t task_id -p task_password while the job is still PENDING
5. Run abrt-retrace-client log -t task_id -p task_password after the job is finished (by success or failure)
6. Run abrt-retrace-client backtrace -t task_id -p task_password after the job is finished successfully
7. Run abrt-retrace-client backtrace -t task_id -p task_password after the job is finished by failure
8. Run abrt-retrace-client batch -d /path/ABRT_crash_directory
9. Run abrt-retrace-client create -d /path/ABRT_crash_directory, replacing coredump, executable or package file by some random content
10. Try to upload a larger crash (eg. kill JVM).
11. Try to replace coderump, executable or package file by some special file (device, symlink)

Expected Results

In order
The expected results match the commands - the first expected result is for the first command, the second is for the second command, and so on

1. The job should be started, task_id and task_password returned on stdout
2. One of the values PENDING, FINISHED_SUCCESS, FINISHED_FAILURE should be returned on stdout together with a more detailed description
3. HTTP 404 Not Found or 403 Forbidden error code should be returned depending on whether task with task_id exists or not. Should be the same with log and backtrace actions
4. HTTP 404 Not Found error code should be returned. Should be the same with backtrace action
5. Plaintext log should be returned on stdout
6. Plaintext backtrace should be returned on stdout
7. HTTP 404 Not Found error code should be returned
8. All actions should happen at once - create, periodically ask for status, download log (print to stdout) / backtrace (save into crash directory) depending on whether the result was successful or not
9. The task should finish by failure
10. If the upload size is larger than 8 MB, you should be prompted to confirm
11. The request should be denied