No test case output

[akwodkiewicz]

Is it possible to provide output per test case, so that this vscode feature is utilized?

I saw that in #1051 you focused on how to see test results at all, which is to click on this "terminal" icon

But since the extension shows each test individually and is able to tell which of the tests failed and which passed, it would be awesome to include this particular piece of info per test case.

Do you know if there's some particular vscode API we would need to be using? Do we have some limitation due to how the extension runs the tests? I'd be happy to try implementing this, but I'd like to ask first if there was already some work done on this topic.

---

search terms: "The test case did not report any output.", test case, no output, test results

[akwodkiewicz]

I created a question about the API in the vscode discussions, let's see if anybody has an answer.

microsoft/vscode-discussions#2876

[connectdotz]

@akwodkiewicz the extension currently works by parsing the JSON results that jest generates for each test — including status, error lines, and messages — and then piping jest’s output directly to vscode’s TestResults and terminal.

This means the extension doesn’t have access to each test’s full console output without either further parsing jest’s raw output or reconstructing it through jest’s reporter API — both approaches are fairly involved.

vscode does provide an API to attach output to individual test items, but the extension currently doesn’t use that API — it only forwards the overall jest output from the test run.

While it’s technically possible to implement per-test output (and we already have an internal reporter that could be extended), doing so would add significant complexity and maintenance burden. At this point, it’s not clear to us whether the overhead would justify the benefit, given that the full jest output is already available in the TestResults and Terminal.

[akwodkiewicz]

Thank you for the reply, @connectdotz. I understand your concerns. I, personally, see the benefit, because with bigger test suites and several tests broken, one has to scroll through the whole output to find the exact part related to the test they need to fix.

Even if ultimately it wouldn't end up in the main branch, implementing this would be an interesting experiment for me to try dipping my toes in vscode API. Could I ask you to help me by pointing to the right vscode API, please?

Is this the internal reporter you mentioned?

vscode-jest/src/reporter.ts

Lines 22 to 32 in 77d55ba

	// report any test or exec errors
	onTestFileResult(
	_test: Test,
	testResult: TestResult,
	_aggregatedResult: AggregatedResult
	): Promise<void> | void {
	if (testResult.numFailingTests > 0 || testResult.testExecError) {
	const msg = `onTestFileResult: encountered errors`;
	process.stderr.write(`${msg}\r\n`);
	}
	}

[nmspatox]

I'd love to see this implemented, in other projects we use vitest VSCode extension that has this and is really useful when working on tests.