-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Test summary check filter #3852
Comments
Hey @Doomann 👋🏻 We're currently looking into improving the end of test summary, as well as stabilizing the json export format. Could you provide us an example (even half-baked and completely experimental) that demonstrates the user-experience you have in mind? That would be super useful to ensure we're aligned on the problem we're trying to solve, and the potential solution you're envisioning 🙇🏻 |
ExampleHi @oleiade Alright, let's say I have a big test, and there is a lot of checks, and lets say some scenario failed, like you can see here: And now I have to scroll up and look for the group where that check failed, and it's easier in the editor when I notice red color somewhere, but like in github actions it's very hard to find failed check. DemonstrationI want to be able to filter checks, like this maybe:
or even like this: And then in the test output I'd like to see only the checks, that i wanted to see, so now failed: Even better option would be is to being able show only failed checks when some of them fails, and show all succeded if all of them succeds. Or maybe sort them and failed ones should be at the bottom :) |
Hi, @oleiade any updates on this? Can I expect this being added in future? |
Hey @Doomann Thanks a lot for putting this whole example together. Much appreciated 🎉 My understanding now is that your goal would be to instruct k6 whether or not to display checks based on their result (passed/failed). Is that correct? We haven't considered it so far, but we will definitely explore it as we aim to revamp the end-of-test summary soon. In order to manage expectations, regardless of whether we decide to address this feature or not, I don't expect this is something that would land in k6 short-term 🙇♂️ |
Feature Description
I suggest an upgrade for summary, after test if you have hundreds of checks, you should be able to filter the failed ones, so you don't have to scroll all the way up and look up for the failed check.
Suggested Solution (optional)
flag when starting test or options that can be but in options object in the test, to filter checks after the tests, like:
checkFilter
:failed|success|all
all
- by defaultAlready existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered: