Task statuses ‐ testing scenarios

Task statuses ‐ testing scenarios

Each scenario starts with following steps:

• Run Requestor yagna daemon
• Run MockGUI application and start Golem
• Run Requestor script

1. Requestor gracefully finishes task -> expected state: Finished

Variants:

a) Requestor closes task

• Hit ctrl-c single time in Requestor script

2. Requestors breaks Agreement -> expected state: Interrupted

Variants:

a) Requestor yagna daemon disappears

• Kill yagna process

b) Requestor script destroys activity, but doesn't terminate Agreement

• Hit ctrl-c in Requestor script double time (in most cases he will manage to terminate activity)

c) Requestor script doesn't destroy activity and doesn't terminate Agreement

• Kill (Sigkill) Requestor script

3. Provider breaks Agreement -> expected state: Interrupted

Variants:

a) Provider gracefully shutdowns application (Agreement is terminated and he is able to send Invoice)

• Click Stop button in MockGUI app

b) Provider is killed (Provider is not able to terminate Agreement)

• Kill (Sigkill) ya-provider agent process

c) Provider's yagna daemon dies

• Kill (Sigkill) yagna process

d) ExeUnit dies (Depends how Requestor handles this. He could create new Agreement, terminate or abandon job)

• Kill (Sigkill or Sigterm) ya-runtime-ai

e) Provider is killed and restarted. Requestor terminates after restart

• Kill (Sigkill) ya-provider agent process
• Start again with start button
• Hit ctrl-c on Requestor application