You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pkg:test provides the locations of tests in the JSON reporter. We use these in VS Code to provide navigation to tests (and VS Code also shows failure messages inline against those tests).
Those locations are computed by pkg:test by looking at the call stack when group() and test() are called, and then walking up to the first frame from the suite file. For test_reflective_loader this results in all tests being attributed to the calls to defineReflectiveSuite().
I've made a change to pkg:test to support passing custom locations to test/group. Once that's released, pkg:test_reflective_loader can be updated to provide those locations when it calls group/test.
I'm happy to make this change once pkg:test rolls out, I'm just recording the issue here in the meantime.
pkg:test
provides the locations of tests in the JSON reporter. We use these in VS Code to provide navigation to tests (and VS Code also shows failure messages inline against those tests).Those locations are computed by
pkg:test
by looking at the call stack whengroup()
andtest()
are called, and then walking up to the first frame from the suite file. Fortest_reflective_loader
this results in all tests being attributed to the calls todefineReflectiveSuite()
.I've made a change to
pkg:test
to support passing custom locations totest
/group
. Once that's released,pkg:test_reflective_loader
can be updated to provide those locations when it callsgroup
/test
.I'm happy to make this change once
pkg:test
rolls out, I'm just recording the issue here in the meantime.Related:
pkg:test
issuepkg:test
to support custom test locationsThe text was updated successfully, but these errors were encountered: