Skip to content

feat: allow users to set test set names - #8

Merged
harry-rhesis merged 1 commit into
mainfrom
feature/test-set-name
Aug 25, 2026
Merged

feat: allow users to set test set names#8
harry-rhesis merged 1 commit into
mainfrom
feature/test-set-name

Conversation

@harry-rhesis

Copy link
Copy Markdown
Contributor

Summary

  • Add testSetName and testSetDescription to GenerationConfig so users can name test sets at generation time, with backwards-compatible defaults
  • Add TestSetClient.update() and @Builder(toBuilder = true) on TestSet for renaming existing test sets via PUT /test_sets/{id}
  • Rewrite TestRunStatsExample, TestResultStatsExample, and TestRunWorkflowExample to use the Insights API (replacing deprecated stats methods)
  • Update top-level README.md with current code examples (record accessors, GenerationConfig, insights), fix stale "Analytics & Stats" references
  • Update examples README.md section names and descriptions to reflect insights

Test plan

  • Unit tests pass (63 tests) — 3 new for testSetName, 2 new for update/toBuilder via WireMock
  • Integration tests pass — 2 new: name round-trip and rename via update
  • Lint (spotless + PMD) clean
  • Verify examples compile and README code snippets are accurate

🤖 Generated with Claude Code

Add testSetName and testSetDescription to GenerationConfig so users can
name test sets at generation time. Add TestSetClient.update() and
TestSet.toBuilder() for renaming existing test sets. Rewrite stats
examples to use the Insights API and update README with current code
samples.

Signed-off-by: Harry Cruz <harry@rhesis.ai>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@harry-rhesis
harry-rhesis merged commit f6faf2a into main Aug 25, 2026
5 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.

1 participant