Add QA test plan generation#3
Merged
Merged
Conversation
Ask the AI to generate a QA test plan and surface it in the UI. Server: updated the generation prompt to include a "test_plan" section, include per-item URLs in the items list, return a stub test_plan when Anthropic key is missing, and mark test_plan as a required field in the JSON schema. Client: added a "Test Plan" tab with an editable pre element and copy button, wired the testplan element into response handling and the copy helper. Overall: enables delivering a machine-generated test plan alongside store, github, and newsletter outputs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Ask the AI to generate a QA test plan and surface it in the UI. Server: updated the generation prompt to include a "test_plan" section, include per-item URLs in the items list, return a stub test_plan when Anthropic key is missing, and mark test_plan as a required field in the JSON schema. Client: added a "Test Plan" tab with an editable pre element and copy button, wired the testplan element into response handling and the copy helper. Overall: enables delivering a machine-generated test plan alongside store, github, and newsletter outputs.
Why?
Closes #2
Changes
How to test
Checklist
npm start.env.exampleupdated if new env vars were added