Improve testing approach for new spec versions

[derberg]

Reason/Context

At the moment, with every new release, we just add model tests + adjust generic tests (so we for example update generic tests to test 2.5 instead of 2.4 - not test in addition, but just test latest). Example #627

I think it is not the best approach. I feel that we should preserve some dedicated acceptance tests per version. Unit test but not a test that checks just a model, but actually parses entire AsyncAPI document, because it depends on @asyncapi/spec for example, where some breaking changes can be introduced.

Description

so what I suggest is a dedicated test per release, with dedicated sample spec, that showcases new features
In such release tests we parse entire example, and also test model functions for a given new feature.

[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 ❤️