-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TestGru] Add unit test for app/lib/common/prompts/optimized.ts #4
[TestGru] Add unit test for app/lib/common/prompts/optimized.ts #4
Conversation
|
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Trigger Info
Summary
This PR introduces unit tests for the
optimizedPrompt
function to ensure its correctness and reliability. The tests cover the following scenarios:Verifying that the prompt is generated correctly with provided options, including
cwd
,allowedHtmlElements
, andmodificationTagName
.Handling cases where the
allowedHtmlElements
array is empty.Ensuring all required sections (
<system_constraints>
,<code_formatting_info>
,<message_formatting_info>
,<diff_spec>
,<chain_of_thought_instructions>
,<artifact_info>
,<examples>
) are included in the generated prompt.Validating the inclusion of the "CRITICAL RULES" section and its subsections (
File and Command Handling
,Response Format
,Development Process
,Coding Standards
,Artifact Usage
).These tests improve the robustness of the
optimizedPrompt
function by verifying its behavior under different input conditions.Coverage
The change in coverage value, such as:
0% -> 50%
, indicates that the coverage was 0% before writing the tests and 50% after writing them.https://web.dev/articles/ta-code-coverage
Test Statuses
Tip
You can
@gru-agent
and leave your feedback. TestGru will make adjustments based on your inputTip
You can
@gru-agent rebase
to rebase the PR.Tip
You can
@gru-agent redo
to reset or rebase before redoing the PR.Tip
To modify the test code yourself, click here Edit Test Code