Skip to content
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.

Sign up for GitHub

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

Jump to bottom

MVP for better testing of the templates -> contract testing with mocks #1417

Open
derberg opened this issue Mar 15, 2025 · 9 comments · May be fixed by #1467
Open

MVP for better testing of the templates -> contract testing with mocks #1417

derberg opened this issue Mar 15, 2025 · 9 comments · May be fixed by #1467
Assignees
@derberg
Labels
area/javascript Specify what technical area given issue relates to. Its goal is to ease filtering good first issues. bounty AsyncAPI Bounty program related label enhancement New feature or request javascript Pull requests that update javascript code

Comments

@derberg
Copy link
Member

derberg commented Mar 15, 2025

Goal: have MVP for #752

What needs to be done:

We already have 2 templates (JS Websocket and Python Websocket - almost merged). So ideally we have a library/solution that integrates with development of templates, and we have automated from that performs contract testing of these templates - using existing fixtures (hoppscotch and postman echo services)
@derberg derberg added area/javascript Specify what technical area given issue relates to. Its goal is to ease filtering good first issues. bounty AsyncAPI Bounty program related label enhancement New feature or request javascript Pull requests that update javascript code labels Mar 15, 2025
@derberg
Copy link
Member Author

derberg commented Mar 15, 2025

I'll be working on that

@mattzinstagib

This comment has been minimized.

Sign in to view
@aeworxet
Copy link

Bounty Issue's service comment

Text labels: bounty/2025-Q2, bounty/advanced, bounty/coding
First assignment to regular contributors: 2025-03-21 00:00:00 UTC+12:00
End Of Life after: 2025-04-30 23:59:59 UTC-12:00

@asyncapi/bounty_team

The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.
Regular contributors should explain in meaningful words how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.

@derberg derberg self-assigned this Mar 18, 2025
@aeworxet
Copy link

@derberg (githubID: 6995927) is an AsyncAPI Maintainer specified in https://github.com/asyncapi/community/blob/master/MAINTAINERS.yaml, so they fall under the first category in the prioritization list.

@aeworxet
Copy link

Bounty Issue's Timeline

Complexity Level Assignment Date (by GitHub) Start Date (by BP Rules) End Date (by BP Rules) Draft PR Submission Final PR Merge Start Final PR Merge End
Advanced 2025-03-18 2025-04-07 2025-06-01 2025-04-27 2025-05-18 2025-06-01
Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.
Keep in mind the responsibility for violations of the Timeline.

Assignee: @derberg (githubID: 6995927)

@aeworxet aeworxet moved this to In Progress in Bounty Program Mar 19, 2025
@derberg
Copy link
Member Author

derberg commented Apr 1, 2025

research in progress, got in touch with Microcks folks to get some help and understanding of websocket support.

luckily podman is there, as docker is killing my mac

This was referenced Apr 2, 2025
Closed
Open
@derberg
Copy link
Member Author

derberg commented Apr 2, 2025

opened a draft pr

#1467

@derberg derberg mentioned this issue Apr 3, 2025
Merged
@derberg
Copy link
Member Author

derberg commented Apr 7, 2025

Microcks - we select it
Draft is ready for review - https://github.com/asyncapi/generator/pull/1329/files

Just waiting for https://github.com/orgs/microcks/discussions/1566

Thing is that for now Microcks works well for testing incoming messages. It is not clear how to test outgoing messages, if the mock receives it.

@derberg
Copy link
Member Author

derberg commented Apr 9, 2025

Just waiting for https://github.com/orgs/microcks/discussions/1566
Thing is that for now Microcks works well for testing incoming messages. It is not clear how to test outgoing messages, if the mock receives it.

clue solved, js test for sending from client in place. Only left python

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@derberg derberg

Labels
area/javascript Specify what technical area given issue relates to. Its goal is to ease filtering good first issues. bounty AsyncAPI Bounty program related label enhancement New feature or request javascript Pull requests that update javascript code
Projects
Bounty Program
Status: In Progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: add acceptance testing with microcks mocks derberg/generator
3 participants
@derberg @aeworxet @mattzinstagib