[TEST]: Add unit tests for scripts/compose.ts

[codxbrexx]

What changes are you proposing?

Add automated unit tests for the blog post composition script (scripts/compose.ts) to cover its interactive CLI flow and file generation behavior.

Why do we need this improvement?

The compose script is frequently used by contributors to create new blog posts, but it currently has no automated coverage.

Problems now:

• No tests for the CLI flow.
• Manual validation required for any change.
• Risk of regressions in slug generation, front matter output, and file writing.

How will this change help?

• Safer refactoring of the script.
• Faster contributor feedback via npm test.
• Ensures consistent output (front matter + slug + file path).

How could it be implemented/designed?

Implementation plan:
Add tests/scripts/compose.test.ts using Jest (already configured with asyncapi/website).

Mock dependencies:

• inquirer for CLI answers.
• fs for file writes.
• moment for deterministic dates.

Test scenarios:

• Happy path: verify file path + front matter.
• Slug generation: ensure titles convert to kebab-case.
• Error handling: verify logging on file write failure.

Breaking changes

No.

Check Before Submitting

• I have looked for similar issues to avoid duplicates.
• I have read the Contributing Guidelines

Would you like to help fix this issue? (Not required, but appreciated!)

• Yes, I am interested in contributing to the fix.
• No, I am just reporting the issue.

cc @asyncapi/maintainers

[SHUBHANSHU602]

hey @codxbrexx this file compose.ts contains no logics which essentially needs testing so I believe there is no need to add test file for it . Please read the file again .

[codxbrexx]

Thanks @SHUBHANSHU602!

Actually, there is logic here that arguably needs regression testing, specifically the regex patterns for slug generation
(see screenshot) and tag parsing. We want to ensure these don't silently break during future refactors.

see This is the exact kind of logic that unit tests are designed to protect.

However, if the maintainers feel this is unnecessary overhead or not a priority, I am happy to drop it.

[anshgoyalevil]

Feel free to raise a PR @codxbrexx