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

Artifact for test plan scenarios for device/phoneNumber errors #323

Open
jlurien opened this issue Oct 22, 2024 · 2 comments · May be fixed by #325
Open

Artifact for test plan scenarios for device/phoneNumber errors #323

jlurien opened this issue Oct 22, 2024 · 2 comments · May be fixed by #325
Labels
enhancement New feature or request

Comments

@jlurien
Copy link
Contributor

jlurien commented Oct 22, 2024

Problem description
In CAMARA we have guidelines for errors related to the management of device/phoneNumber inputs, and test plans should include scenarios to test that those guidelines are applied for APIs with such an input.

Test guidelines give high level recommendations but they do not define specific scenarios, so different test definitions may end up with different scenarios for the same use case.

Possible evolution
Create a common artifact for these scenarios, here in Commonalities, that can be directly applied, or with some minor adaptation, to test plans. This would ease the creation of test plans and assure coherence.

Additional context
This would be a first artifact but we may create additional artifacts for the testing of other functionalities that are shared by several APIs and have also common guidelines, such as:

  • Subcriptions
  • Events
  • Common errors dealing with authentication/authorization
@jlurien jlurien added the enhancement New feature or request label Oct 22, 2024
@jlurien
Copy link
Contributor Author

jlurien commented Oct 22, 2024

I can submit a PR as an example, as it will be better understood

@bigludo7
Copy link
Collaborator

Fully aligned with the proposal objectives.

I've raised issue #293 some time ago for same topic but for the subscriptions.

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

Successfully merging a pull request may close this issue.

2 participants