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.

Sign up for GitHub

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

Jump to bottom

Issue with PostAssetAdministrationShell in API Validation #37

Open
juileetikekar opened this issue Jul 18, 2024 · 0 comments
Open

Issue with PostAssetAdministrationShell in API Validation #37

juileetikekar opened this issue Jul 18, 2024 · 0 comments
Labels
API Issue related to API validation

Comments

@juileetikekar
Copy link
Collaborator

juileetikekar commented Jul 18, 2024 •
edited
Loading

In case of API validation "Asset Administration Shell Repository API", the test-engine triggers POST "/shells" API call with a request body. However, the request body consists of multiple shells, submodels and concept-descriptions. However, as per the specifications (Part-2) as well as SwaggerHub definition, the request body should only consists of serialization of single AAS only.

The request body received from test-engine in case of POST "/shells"
CurrentRequestBody.json

Additionally with this request, the test-engine expects the response code "201 (Created)", which is unexpected. The expected response code here should be "400 (BadRequest)"

image
@juileetikekar juileetikekar added the API Issue related to API validation label Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API Issue related to API validation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@juileetikekar