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] Live stats update #1471

Open
vkosuri opened this issue Apr 22, 2022 · 6 comments
Open

[FEATURE] Live stats update #1471

vkosuri opened this issue Apr 22, 2022 · 6 comments
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

@vkosuri
Copy link

vkosuri commented Apr 22, 2022

It would be great if we would have live test count increments

Verb --- Number tests performed for each verb

GET
PUT
PATH
DELETE

Test status --- Denotes the number of tests passed or failed

Pass:
Fail:

Stauts code: For each status code number of tests performed

1xx
2xx
3xx
4xx

@vkosuri vkosuri added Status: Needs Triage Requires initial assessment to categorize and prioritize Type: Feature New functionalities or enhancements labels Apr 22, 2022
@Stranger6667
Copy link
Member

These stats are definitely nice to see, but I don't have a complete vision of what the end result might look like. It is somehow incompatible with the current CLI style that follows pytest that outputs a line for each tested endpoint. I'd like to have some CLI redesign and such an idea is definitely something I want to consider - some folks already asked about certain statistics in the output (for example #1414).

I won't start working on this right now, but rather would like to gather more information first. If I'd share a questionnaire on the new output style, would you fill it in?

@vkosuri
Copy link
Author

vkosuri commented Apr 23, 2022

I won't start working on this right now, but rather would like to gather more information first

Our API requests are very time consuming around 20 to 30mins duration will take in the future may go beyond, and The end-use at least knows what exactly is failing or passing etc. By looking at these stats we can something happening

a questionnaire on the new output style, would you fill it in?

Sure

@hoog1511
Copy link

@Stranger6667 was this questionnaire sent out at some point? I am still interested in having this specific feature added to schemathesis.

@Stranger6667
Copy link
Member

Hey @hoog1511 !

Thanks for pinging! Unfortunately, I digressed on other stuff back in the day and didn't manage to get back to it.

I am open to collecting feedback on this still, but at this point, I'd like to focus on everything related to customizing checks, hooks, filters, etc.

Then, I plan to work on CLI output style indeed. Probably such a questionnaire could be written now and then we collect data, so when the time comes we have some input there.

@hoog1511
Copy link

@Stranger6667 if I could get a heads-up for when the questionnaire is ready to be shared, I would love to give my input for it.

@Stranger6667
Copy link
Member

@hoog1511 Sure, the questionnaire is here - https://forms.gle/gkhGHJPbgkCG7HcA8

There are also a few issues where I'd appreciate feedback:

@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
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

3 participants