Skip to content

πŸ§ͺ Add tests for stringToColor utility#12

Open
Ap-0007 wants to merge 1 commit into
mainfrom
add-tests-string-to-color-2079846489635909088
Open

πŸ§ͺ Add tests for stringToColor utility#12
Ap-0007 wants to merge 1 commit into
mainfrom
add-tests-string-to-color-2079846489635909088

Conversation

@Ap-0007

@Ap-0007 Ap-0007 commented May 18, 2026

Copy link
Copy Markdown
Owner

🎯 What: This PR adds unit tests for the stringToColor utility function in lib/utils.ts. The implementation uses the native node:test runner and node:assert/strict which were missing from the project, while keeping the toolset light by utilizing --experimental-strip-types to avoid adding complex external test frameworks.

πŸ“Š Coverage:
The tests cover several important scenarios:

  • Determinism (ensuring the same string yields the same color).
  • Variation (ensuring different strings yield different colors).
  • Empty string handling (correctly resolving to a 0 hue).
  • Valid HSL format output, specifically guarding against negative modulo results natively generated by JavaScript.
  • Specific known input/output pairs.

✨ Result: Test coverage improved for the utility file. The codebase now has a npm run test script running a small but solid suite for string to color conversion, increasing reliability and serving as a blueprint for future utility tests.


PR created automatically by Jules for task 2079846489635909088 started by @Ap-0007

Add a test suite using Node.js native test runner to cover stringToColor
utility function behavior including determinism, handling empty strings,
negative modulo outcomes, and specific expected outputs. Added `test`
script to package.json.

Co-authored-by: Ap-0007 <200978133+Ap-0007@users.noreply.github.com>
@vercel

vercel Bot commented May 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
side_pro Ready Ready Preview, Comment May 18, 2026 1:11pm

@google-labs-jules

Copy link
Copy Markdown
Contributor

πŸ‘‹ Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a πŸ‘€ emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

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