Skip to content

[CHA-2563] Add retention policy integration tests#45

Merged
itsmeadi merged 7 commits intomasterfrom
feature/cha-2563-retention-policy-endpoints
Mar 31, 2026
Merged

[CHA-2563] Add retention policy integration tests#45
itsmeadi merged 7 commits intomasterfrom
feature/cha-2563-retention-policy-endpoints

Conversation

@hifaizsk
Copy link
Copy Markdown
Contributor

@hifaizsk hifaizsk commented Mar 23, 2026

Ticket

Summary

  • Add integration tests for the 4 retention policy endpoints: SetRetentionPolicy, GetRetentionPolicy, GetRetentionPolicyRuns, DeleteRetentionPolicy
  • Tests cover the full CRUD lifecycle: create policy → get policy → get runs → delete policy
  • Graceful skip when retention feature is not enabled on the test app

Checklist

  • Integration tests for retention policy endpoints

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@hifaizsk hifaizsk force-pushed the feature/cha-2563-retention-policy-endpoints branch from 0cbb7f9 to a65ecee Compare March 23, 2026 16:01
@hifaizsk hifaizsk changed the title [CHA-2563] Add retention policy endpoints [CHA-2563] Add retention policy integration tests Mar 23, 2026
Restructure retention policy tests to remove set_retention_policy as a
primary assertion. Move it to before(:all) setup with after(:all)
cleanup. Keep separate it blocks for get, get_runs, and delete.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Regenerated SDK from latest serverside-api.yaml spec. Updated retention
policy integration test to only test get_retention_policy_runs endpoint.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@itsmeadi itsmeadi merged commit 43f19b6 into master Mar 31, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants