karatelabs/karate

Unclear error logs

Open

#2,952 opened on Jul 1, 2026

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Java (1,893 forks)batch import
help wanted

Repository metrics

Stars
 (7,600 stars)
PR merge metrics
 (Avg merge 1d 20h) (11 merged PRs in 30d)

Description

Problem or Use Case

Error logs are no longer as accurate as in the previous release. Only the error and the feature's scenario name are displayed, with no reference to the feature line or the instruction that triggered the error. This information was present in previous versions. example: [ERROR] Tests run: 111, Failures: 0, Errors: 16, Skipped: 0, Time elapsed: 320.2 s <<< FAILURE! -- in it.$Test [ERROR] [src/test/java/.../test_accounts] Get Accounts bulk stress test.[1.6:37] Get Accounts bulk test - page 0 size 9999 -- Time elapsed: 0.006 s <<< ERROR! java.lang.RuntimeException: java.net.SocketTimeoutException: Read timed out

Proposed Solution

in previous release the log was like

classpath:it/.../flow.feature:107 src/test/java/it/.../test.feature:385 at com.intuit.karate.junit5.FeatureNode.lambda$next$1(FeatureNode.java:86)

Alternatives Considered

No response

Contributor guide

Research direction
Investigate recent commits that changed the error log format; trace the code path from test execution to log output to find where the line reference is omitted.
Tech stack
java
Domain
testing
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70