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.

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

Test statement for device-roaming-status & device-reachability-status APIs #258

Open
akoshunyadi opened this issue Feb 13, 2025 · 1 comment
Labels

Comments

@akoshunyadi
Copy link
Collaborator

Problem description
To be able to create a public release we need to have test results for the stable APIs (see Readiness Checklists)

  • device-roaming-status 1.0.0
  • device-reachability-status 1.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:

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

This step should ensure the quality of the stable APIs. Ideally (if no issues were found) the feedback would be something like "Code generation and test execution with v1.0.0-rc.1 performed successfully."

Additional context

@maxl2287
Copy link
Contributor

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:

  • device-roaming-status v1.0.0-rc.1
  • device-reachability-status 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants