Create a simple E2E robot script to test agents sessions #1061

Open
opened 2026-03-19 01:02:02 +00:00 by brent.edwards · 1 comment
Member

Metadata

  • Commit Message: test(sessions): test against agents sessions
  • Branch: test/e2e-session-lifecycle

Background

This task will be my first Robot test. It will create a Robot test against the agents session scripts.

It will run at least one of each of the following commands in a happy path test:

agents session create [--actor <ACTOR>]
agents session list
agents session show <SESSION_ID>
agents session delete [--yes|-y] <SESSION_ID>
agents session export [(--output|-o) <FILE>] <SESSION_ID>
agents session import (--input|-i) <FILE>
agents session tell --session <SESSION_ID> [--actor <ACTOR>] [--stream] <PROMPT>

Subtasks

This task is done when:

  • A new robot test exists.
  • The test must have at least one of each of the agents session commands
  • It checks the output of every command.

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message
    matches the Commit Message in Metadata exactly, followed by a blank line,
    then additional lines providing relevant details about the implementation.
  • The commit is pushed to the remote on the branch matching the Branch in
    Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and
    merged before this issue is marked done.
## Metadata - **Commit Message**: test(sessions): test against `agents sessions` - **Branch**: `test/e2e-session-lifecycle` ## Background This task will be my first Robot test. It will create a Robot test against the `agents session` scripts. It will run at least one of each of the following commands in a happy path test: ``` agents session create [--actor <ACTOR>] agents session list agents session show <SESSION_ID> agents session delete [--yes|-y] <SESSION_ID> agents session export [(--output|-o) <FILE>] <SESSION_ID> agents session import (--input|-i) <FILE> agents session tell --session <SESSION_ID> [--actor <ACTOR>] [--stream] <PROMPT> ``` ## Subtasks This task is done when: - A new robot test exists. - The test must have at least one of each of the `agents session` commands - It checks the output of every command. ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done.
freemo added this to the v3.2.0 milestone 2026-03-19 05:28:25 +00:00
freemo self-assigned this 2026-04-02 06:13:48 +00:00
Owner

Thank you for filing this issue, @brent.edwards. I've reviewed it and it is well-formed with complete metadata, subtasks, and a Definition of Done.

Triage assessment:

  • Priority: Low — this is a testing improvement that adds E2E coverage for the agents session commands. Important for quality but not blocking any functionality.
  • Milestone: v3.2.0 — appropriate since session management is part of the core CLI.
  • Type: Testing — correctly classified.
  • Effort: Points/2 — reasonable for a single Robot Framework test file covering the session lifecycle commands.

Observations on scope:

The issue covers a comprehensive happy-path test for all agents session subcommands: create, list, show, delete, export, import, and tell. This is a good first Robot test as noted in the description. A few considerations:

  1. The tell command requires an LLM backend. The test should either use the Skip If No LLM Keys pattern used elsewhere in the Robot suite, or mock the LLM response.
  2. The export/import cycle is a good round-trip test — export a session, delete it, re-import it, and verify it matches.
  3. The test should clean up after itself (delete created sessions) to avoid polluting the test environment.

Parent Epic: This should be linked to a testing or session management epic. If no suitable parent exists, one should be identified.

Next step: This issue is ready for verification and implementation.


Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: ca-human-liaison

Thank you for filing this issue, @brent.edwards. I've reviewed it and it is well-formed with complete metadata, subtasks, and a Definition of Done. **Triage assessment:** - **Priority**: Low — this is a testing improvement that adds E2E coverage for the `agents session` commands. Important for quality but not blocking any functionality. - **Milestone**: v3.2.0 — appropriate since session management is part of the core CLI. - **Type**: Testing — correctly classified. - **Effort**: Points/2 — reasonable for a single Robot Framework test file covering the session lifecycle commands. **Observations on scope:** The issue covers a comprehensive happy-path test for all `agents session` subcommands: `create`, `list`, `show`, `delete`, `export`, `import`, and `tell`. This is a good first Robot test as noted in the description. A few considerations: 1. The `tell` command requires an LLM backend. The test should either use the `Skip If No LLM Keys` pattern used elsewhere in the Robot suite, or mock the LLM response. 2. The `export`/`import` cycle is a good round-trip test — export a session, delete it, re-import it, and verify it matches. 3. The test should clean up after itself (delete created sessions) to avoid polluting the test environment. **Parent Epic**: This should be linked to a testing or session management epic. If no suitable parent exists, one should be identified. **Next step**: This issue is ready for verification and implementation. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: ca-human-liaison
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#1061
No description provided.