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

Enhancement to console report - add skipped count, pass percentage #2483

Closed
codehackerr opened this issue Jan 22, 2024 · 7 comments
Closed
Assignees

Comments

@codehackerr
Copy link
Contributor

codehackerr commented Jan 22, 2024

Add skipped count, pass percentage to console reports.
This is to be consistent with the enhancement to karate summary report.

Console Report

Karate-Console-Report

Karate Summary HTML Report

Karate-report-screenshot
@codehackerr
Copy link
Contributor Author

codehackerr commented Jan 22, 2024

@ptrthomas Can you prioritize, approve and assign this issue to me please ? This will be a quick win.

@ptrthomas
Copy link
Member

@codehackerr sure, please try your best to align things to look good. do paste a screenshot of the results !

@codehackerr
Copy link
Contributor Author

codehackerr commented Jan 22, 2024

@ptrthomas Please merge: #2486

Screenshot of the fix:

karate-console-report-with-skipped-count-and-pass-percentage

@ptrthomas
Copy link
Member

I don't like it :( and skipped appears twice ? let us hold on this, because a small fraction of people requested this

@rc2201
Copy link

rc2201 commented Jan 23, 2024

Hi @ptrthomas will #2340 be included in 1.5.0 or will that also be on hold along with this?

@codehackerr
Copy link
Contributor Author

@ptrthomas onskipped appearing twice, one is features skipped other is scenarios skipped. Or am I missing something ? Anyway will get back to this, if and when you think this is required.

@ptrthomas
Copy link
Member

@codehackerr thanks for your work on this, I think the console should be kept simple with less clutter. for now let me close this and revisit when there is a strong case for making this change. as long as all the info is in the HTML reports, I think it is fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants