Test statements for stable APIs quality-on-demand and qos-profiles v1.0.0

[hdamker]

Problem description
To be able to create a public release we need to have test results for the stable APIs

• quality-on-demand v1.0.0
• qos-profiles v1.0.0

Expected action
We would like to have a feedback from different companies / API providers regarding ongoing implementation of the API or issues, which occur:

• during code-generation
• inside the specification
• during executing the feature-files

Additional context
Latest (Pre-)release: https://github.com/camaraproject/QualityOnDemand/releases/tag/r2.1

[hdamker]

@camaraproject/quality-on-demand_maintainers @camaraproject/quality-on-demand_codeowners This issue is intended to be put as reference to the test result statement within the API Readiness checklists.

[maxl2287]

Feedback from Deutsche Telekom AG (DTAG)

I am one of the developers, and my team is responsible for implementing Network APIs.

We have implemented the provider side of (pre-)release r2.1 on behalf of Deutsche Telekom
regarding the stable APIs:

• quality-on-demand v1.0.0-rc.1
• qos-profiles v1.0.0-rc.1

From our team's perspective, there are no issues.

The code generation process ran smoothly and the newly defined error codes in the specification were understood and successfully integrated into our implementation.

So far, we have only reviewed the feature files containing test cases in terms of structure and understanding. The implementation and execution of the tests based on the feature files will be carried out in the next steps.

[patrice-conil]

Feedback from Orange

We've successfully implemented the provider side of (pre-)release r2.1 (using OpenApi generator to generate models and API interfaces)

• quality-on-demand v1.0.0-rc.1
• qos-profiles v1.0.0-rc.1

We haven't implemented the "glue" to run the test features yet, but everything seems ok in terms of structure and understanding. We will try to implement this after MWC.