Skip to content

Inconsistencies in the API specification #19

@apicarve

Description

@apicarve

Hello, we are building a research tool to generate API test suites and API specification automatically using UI test suites. When we compared the API specification we generate for your web app with the specification provided along with the web application, we found a few inconsistencies. Would you consider this to be a problem with the API specification or with the application?

Here are the API endpoints for which the server provided a 2xx or a 3xx status but the specification does not include them. Some of these endpoints are actually used by the UI to communicate with the server but not documented in the specification.

			"/product-options",
			"/product/update/2-options",
			"/product/update/1-options",
			"/cart-options",
			"/category/create-options",
			"/category/update/1-options",
			"/cart/delete/2-options",
			"/product/add-options",
			"/category/update/2-options",
			"/cart/delete/1-options",
			"/user/signIn-options",
			"/wishlist/add-options",
			"/category-options" 

For example /category-options means that we tried the HTTP request OPTIONS on the API endpoint /category and received a status 200 from the server but there is no corresponding operation defined in the specification.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions