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

[FEATURE] show what response status codes are hit per endpoint #1414

Open
hoog1511 opened this issue Mar 29, 2022 · 1 comment
Open

[FEATURE] show what response status codes are hit per endpoint #1414

hoog1511 opened this issue Mar 29, 2022 · 1 comment
Assignees
Labels
Component: CLI Command line interface Status: Needs Design Issue requires more design work Type: Feature New functionalities or enhancements UX: Reporting Output readability

Comments

@hoog1511
Copy link

hoog1511 commented Mar 29, 2022

Describe the solution you'd like

I would like a feature that shows what response status codes are tested per endpoint when performing tests in the CLI. This would make it easier to confirm that all the defined responses in the OAS are validated against the application which is being tested. Currently, I have to manually check the debug output for this information, which can take some time to do depending on the application.

example:
/relations 40 tests performed, 10 200 results, 10 400 results, 10 401 results, 10 403 results
/arrangements 40 tests performed, 40 400 results

This would make it a lot easier for users to ascertain what example(s)/enum(s) need to be changed within the schema to make sure all responses are validated.

@hoog1511 hoog1511 added Status: Needs Triage Requires initial assessment to categorize and prioritize Type: Feature New functionalities or enhancements labels Mar 29, 2022
@Stranger6667 Stranger6667 added UX: Reporting Output readability Component: CLI Command line interface Status: Needs Design Issue requires more design work and removed Status: Needs Triage Requires initial assessment to categorize and prioritize labels Oct 11, 2023
@Stranger6667
Copy link
Member

I like the idea, it could be a separate "Statistic" section in the CLI output, will work on design in some of the next releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: CLI Command line interface Status: Needs Design Issue requires more design work Type: Feature New functionalities or enhancements UX: Reporting Output readability
Projects
None yet
Development

No branches or pull requests

2 participants