Implement extended tests for bindings and AsyncAPI v3.0.0 definitions

[Pakisan]

Why do we need this improvement?

I have already wrote basic tests for bindings and AsyncAPI v3.0.0 definitions

Now, it's time to tune them up

I expect next:

• basic scenarios for schema:
  • empty
  • example
  • without required fields
  • only required fields
  • extended
  • wrongly extended
• basic scenarios for property:
  • string
  • object
  • null
  • number
  • boolean
  • array
• All current misses are described in related discussion - [3.0.0] Json Schemas for bindings and definitions current state #546

Initial tests are here: #540
Related issue, witch schemas new format: #549

How will this change help?

We will be sure that after changes in our schemes nothing will be broken

Screenshots

No response

How could it be implemented/designed?

Tune up basic tests

🚧 Breaking changes

No

👀 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?

Yes I am willing to submit a PR!

[aeworxet]

Bounty Issue's service comment

Text labels: bounty/2024-Q3, bounty/advanced, bounty/coding
First assignment to third-party contributors: 2024-06-21 00:00:00 UTC+12:00
End Of Life after: 2024-07-31 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.

Third-party contributors should coherently articulate how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.

[aeworxet]

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	2024-06-15	2024-07-01	2024-08-25	2024-07-21	2024-08-11	2024-08-25

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.

[aeworxet]

@Pakisan, please provide the Draft PR.

[Pakisan]

@aeworxet #540

Few tests left

[Pakisan]

@aeworxet #540

Few tests left

Tagged folks in PR

[aeworxet]

Review for PR #540 was requested on 2024-07-26, and it is still in progress.

[aeworxet]

@Pakisan

Do you need more reviews of PR #540 or reviews

#540 (review)
#540 (comment)

have been enough and you already have an understanding of what to do next?

[aeworxet]

Responses, critical for technical resolution of this Bounty Issue (review of the PR) were delayed for three periods of three consecutive working days
#540 (comment)
#540 (comment)

so all remaining target dates of the Bounty Issue's Timeline are extended by four calendar weeks.

Bounty Issue's Timeline Extended

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	2024-06-15	2024-07-01	2024-09-22	2024-08-18	2024-09-08	2024-09-22

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.

[Pakisan]

#540 contains both double work result:

• initial tests for our schemes, like info, server, security - that’s how this MR appeared
• extended tests from 551 - by this I added common tests structure with declared requirements like extended, wrongly extended, properties checking and so on

Everything else is out of scope of this issue:

• schemas patching, based on collected typos and errors
• migration to new schema structure, from style: perform schema formatting with the new JSON Schema CLI #549

So this Bounty Issue is completed.

[aeworxet]

Bounty Issue Is Completed 🎉

@Pakisan, please go to the AsyncAPI page on Open Collective and submit an invoice for USD 400.00 with the expense title Bounty spec-json-schemas#551, tag bounty, and full URL of this Bounty Issue in the description.

[Pakisan]

Bounty Issue Is Completed 🎉

@Pakisan, please go to the AsyncAPI page on Open Collective and submit an invoice for USD 400.00 with the expense title Bounty spec-json-schemas#551, tag bounty, and full URL of this Bounty Issue in the description.

Done