[FEATURE] <description>Add automated tests for the WebSocket server generated by the Node.js WS template

[sauraviiitk]

Why do we need this improvement?

The Node.js WebSocket template currently generates a functional WebSocket server, but there are no automated tests validating the generated output. This means that any change to the template can unintentionally break the generated server without being detected early.

Since this repository provides a code generation template, users rely on the generated code to work correctly out of the box. Without automated tests, regressions may only be discovered after users manually generate and run the project, leading to a poor developer experience and increased maintenance effort.

How will this change help?

This improvement will:

• Ensure the generated WebSocket server starts correctly
• Verify that WebSocket clients can successfully connect
• Validate that messages defined in the AsyncAPI document are handled as expected
• Ensure invalid or malformed messages are handled gracefully without crashing the server
  Overall, this will increase confidence in the template, reduce regressions, and improve reliability for both users and maintainers.

Screenshots

No response

How could it be implemented/designed?

A possible implementation approach:

• Create a minimal AsyncAPI document as a test fixture
• Generate a WebSocket server from the template using this document
• Start the generated server programmatically during tests
• Use a WebSocket client (e.g., ws) to simulate client connections
• Add tests for:

1. Server startup
2. Client connection success
3. Handling of valid messages
4. Graceful handling of invalid messages

• Integrate these tests into the existing test or CI workflow

This approach keeps the scope focused while providing meaningful coverage of the generated output.

🚧 Breaking changes

Yes

👀 Have you checked for similar open issues?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue?

None

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️