Story (Required)

Background and Approach (Required)

In the 'challenging cases Argo Agent must handle' document (https://docs.google.com/document/d/1NwQaYxmRva8irx_clPTqRu_YQ8MNeFNXSTJoOgv7ZRs/edit?tab=t.0), a set of use cases were identified that cause incorrect behaviour in the Argo Agent, at present.

We aim to fix those as part of GITOPS-5919.

It would be beneficial for us to:

• A) Verify that these have been solved
• B) Verify that we do not regress them.

The best way to do this is to implement E2E tests that reproduce the issue (where possible).

This will require significant updates to the E2E test framework: At present, the E2E test framework assumes that the agent/principal/autonomous agents are always running, and will never stop running. However, for these 'challenging cases', we need the ability to pause (stop, do some actions, then restart) each of the components. For example, challenging case A) can only occur while managed agent process is stopped, while the principal is still running.

As a starting point, we should implement E2E tests for challenging cases A and B.

(C, D and E, are tough to simulate, because they require the ability to temporarily block network traffic between two pods. Let's exclude from this story)

Acceptance Criteria (Mandatory)

• Make changes to the test framework to allow us to temporarily start/stop managed agent/autonomous agents, and principal, from within the E2E tests.
• Implement E2E tests that reproduce challenging case A and B from the challenge case doc.