QA:Testcase Retrace Server CLI

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.

1. Run abrt-retrace-client create -d /path/ABRT_crash_directory
2. Run abrt-retrace-client create -k -d /path/ABRT_crash_directory, the -k option disables HTTPS certificate check.
3. Run abrt-retrace-client status -k -t task_id -p task_password with task_id and task_password obtained from create action.
4. Run abrt-retrace-client status -k -t task_id -p task_password with a wrong combination of task_id and task_password.
5. Run abrt-retrace-client log -k -t task_id -p task_password while the job is still PENDING.
6. Run abrt-retrace-client log -k -t task_id -p task_password after the job is finished (by success or failure).
7. Run abrt-retrace-client backtrace -k -t task_id -p task_password after the job is finished successfully.
8. Run abrt-retrace-client backtrace -k -t task_id -p task_password after the job is finished by failure.
9. Run abrt-retrace-client batch -k -d /path/ABRT_crash_directory.
10. Run abrt-retrace-client create -d /path/ABRT_crash_directory, replacing coredump, executable or package file by some random content.
11. Run abrt-retrace-client create -d /path/ABRT_crash_directory --url URL, with URL different to retrace01.fedoraproject.org.

Expected Results

1. The command should fail because of untrusted HTTPS certificate.
2. The job should be started, task_id and task_password returned on stdout.
3. One of the values PENDING, FINISHED_SUCCESS, FINISHED_FAILURE should be returned on stdout.
4. 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.
5. HTTP 404 Not Found error code should be returned. Should be the same with backtrace action.
6. Plaintext log should be returned on stdout.
7. Plaintext backtrace should be returned on stdout.
8. HTTP 404 Not Found error code should be returned.
9. All actions should happen at once - create, periodically ask for status, download log / backtrace depending on whether the result was successful or not.
10. The task should finish by failure.
11. The upload should fail.